sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: proposal: net: `fd` and `fdgram` networks for `net.Dial` to connect to file descriptor numbers
Labels: Proposal

### Proposal Details

I would like to use Dial like so:

`net.Dial("fd", "3")`

or ListenPacket like so:

`net.ListenPacket("fdgram", "3")`

to create a `FilePacketConn` from a file descriptor number. I would also like to use Listen like so:

`net.Listen("fd", "0")`

to create a `FileListener` from a file descriptor number. This is useful because many go programs read a network and address from some form of configuration, and then pass these values to `net.Dial` or `net.Listen` to connect or bind to the given address. It is desirable for these programs to be able to inherit file descriptors from a parent process for these connections and listeners, without making any changes made to their implementation, for at least two use cases:

- programs can be run in a containerized environment with networking completely disabled but still use `net` for I/O
- socket managers can terminate and respawn child servers that inherit listeners, without clients seeing an ECONNREFUSED

both of these use cases can already be implemented with NewFile, FileListener, and FilePacketConn, but adding support for them directly to Dial and Listen abstracts their implementation down to the level of configuration, which most programs using `net` implement already. For consistency, separate funcs with typed parameters similar to the other Dial* and Listen* funcs, can also be added:

- `func DialFd(network string, lfd, rfd uintptr) (FilePacketConn, error)`
- `func ListenFd(network string, lfd uintptr) (FileListener, error)`
- `func ListenFdgram(network string, lfd uintptr) (FilePacketConn, error)`

all of these funcs can be implemented as simple compositions of NewFile with FileListener or FilePacketConn. I can add all of these features to `net` if there is support for them.
Repository: go
Issue: os: investigate dropping support for pre-long-path Windows
Labels: OS-Windows,NeedsInvestigation

On Windows, the os package includes some trickery to enable support for long paths on older versions of Windows. The fixLongPath function rewrites longer paths to contain a `\\?\` prefix, which "tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system." (https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#win32-file-namespaces)

The `\\?\` prefix can have effects other than just making a longer path work. For example, ```Mkdir(`\\?\c:\foo `)``` will create a directory `"foo "` with a trailing space, while ```Mkdir(`c:\foo `)``` will strip the space and create `"foo"`.

Newer versions of Windows optionally support long paths directly. On Windows 10.0 with a build ID of 15063 and higher, we skip the `\\?\` workaround: https://go.googlesource.com/go/+/refs/tags/go1.23.0/src/runtime/os_windows.go#450

Interestingly, the Windows documentation indicates that long paths should be supported on 10.0.1607 and higher
(https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later), and 1607 is build id 14393 (https://learn.microsoft.com/en-us/windows/release-health/release-information).

I don't know why we're checking for a build ID of 15063 instead of 14393.

https://go.dev/wiki/MinimumRequirements#windowswindows says that the supported Windows versions are Windows 10 and higher or Windows Server 2016 and higher.

I don't know what versions of Windows Server 2016 support long paths.

Do we still support any versions of Windows that don't have long path support? Can we just drop the `\\?\` workaround entirely?

/cc @qmuntal
Repository: godot
Issue: Android Export Crashes on Startup with .NET 9
Labels: bug,platform:android,needs testing,topic:dotnet,topic:export

### Tested versions

- v4.3.stable.mono

### System information

Built on Windows 11
Tested on Google Pixel 8 (Android 14)

### Issue description

Although the editor appears to successfully export the Android `apk` using `.NET 9`, when launched, it crashes on startup. Using the Logcat I'm able to retrieve this error:
```
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xb40000706385f85 in tid 11785 (VkThread), pid 11745 (m.example.test1)
Cmdline: com.example.test1
pid: 11745, tid: 11785, name: VkThread  >>> com.example.test1 <<<
NOTE: Function names and BuildId information is missing for some frames due
NOTE: to unreadable libraries. For unwinds of apps, only shared libraries
NOTE: found under the lib/ directory are readable.
NOTE: Unreadable libraries:
NOTE:   /data/data/com.example.test1/cache/data_Setup Project_android_arm64/libcoreclr.so
NOTE:   /data/data/com.example.test1/cache/data_Setup Project_android_arm64/libhostfxr.so
NOTE:   /data/data/com.example.test1/cache/data_Setup Project_android_arm64/libhostpolicy.so
...
```
It appears that those are native libraries that are not being loaded. Looks similar to #65863 which points in the direction that `.NET` is not actually being included in the export. Seems to work fine in the editor and when exported to Windows. Also doesn't work on iOS which might be the same issue.

### Steps to reproduce

1. Create project and set target framework to `.NET 9`.
2. Export to Android.
3. Launch the application.

### Minimal reproduction project (MRP)
[android_export_crash.zip](https://github.com/user-attachments/files/17351151/android_export_crash.zip)
Repository: rust
Issue: precondition_check functions can survive MonoReachable
Labels: A-codegen,T-compiler,C-bug

The motivating example is this: https://rust.godbolt.org/z/dGe6EMrEz, the IR of the function at the top which is `IndexRange as SliceIndex<[T]>>::get_unchecked_mut` contains a precondition check. The fact that the call is in a block without any predecessors does not make this unimportant, https://github.com/rust-lang/rust/pull/121421 is not working here.

The MIR for the function in question looks like this:
```
bb0: {   
    _3 = UbChecks();
    switchInt(copy _3) -> [0: bb3, otherwise: bb1];
}

bb1: {   
    <snip>
    _4 = <IndexRange as SliceIndex<[T]>>::get_unchecked_mut::precondition_check(move _5, move _6) -> [return: bb2, unwind unreachable];
}

bb2: {   
    <snip>
    goto -> bb4; 
}

bb3: {   
    <snip>
    switchInt(copy _3) -> [0: bb5, otherwise: bb4];
}

bb4: {   
    _10 = num::<impl usize>::unchecked_sub::precondition_check(copy _9, copy _7) -> [return: bb5, unwind unreachable];
}

bb5: {
    <snip>
    return;
}
```
The MIR optimization pipeline has helpfully hoisted the assignment of `UbChecks()` to a local then consulted that twice. But mono-reachable traversal onlky understands that the very specific pattern in `bb0`, and does not figure out that `bb3` is also a switch on a constant that it could handle.

Post-mono GVN is really the way out of this. We'd love to have `switchInt(const true)` or `switchInt(const false)` in the MIR. Codegen could figure that out easily. I'm going to see what it takes to paper another hack over this instead, on the off-chance that it is highly effective and easy to do.
Repository: flutter
Issue: [Android] disable software rendering support for Android platform.
Labels: P3,team-engine,triaged-engine

Today software forces a Skia fallback, which we don't intend to keep forever. The only usages of software should be for testing, we can verify it isn't being used in google3 and remove.
Repository: deno
Issue: Deno compile crash when try chdir
Labels: bug,compile

Version: Deno 2.0.0

I've tried to compile a nextjs standalone compiled project and got this error when try to execute the compiled denojs version of this project:

```
error: Uncaught (in promise) NotSupported: The operation is not supported
    at Process.chdir (ext:deno_fs/30_fs.js:155:3)
```

Minimal repro:
```ts
import { fileURLToPath } from 'node:url'
import process from 'node:process'

const __dirname = fileURLToPath(new URL('.', import.meta.url))

process.chdir(__dirname)
```

`deno compile -A main.js`
`./main`
Repository: deno
Issue: Allow specifying `--allow-imports` permissions via environment variables
Labels: cli,permissions,suggestion

if i want abc.com and xyz.com always in allow-imports, maybe config it in env would be a solution
Repository: ollama
Issue: rhymes-ai/Aria
Labels: model request

This multimodal model outperforms both LLaMA 3.2 (11B Vision) and PixTral 12B. According to the Hugging Face page, it has 25.3 billion parameters and can be loaded onto a single A100 (80GB) GPU with bfloat16 precision. In my tests, it got the result of an image right, where LLaMA 3.2 (72B) failed.
Repository: tauri
Issue: [bug] In linux `appWindow.isFocused` is always `false`.
Labels: type: bug,status: needs triage

### Describe the bug

Hey👋, `appWindow.isFocused` is always `false` in linux, but it's fine in macOS and Windows! How can this problem be solved?

```ts
const appWindow = getCurrentWebviewWindow();

const focused = await appWindow.isFocused();
```

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Ubuntu 22.4.0 aarch64 (X64)
    ✔ webkit2gtk-4.1: 2.44.3
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-unknown-linux-gnu (default)
    - node: 20.18.0
    - pnpm: 9.12.1
    - npm: 10.8.2

[-] Packages
    - tauri 🦀: 2.0.2
    - tauri-build 🦀: 2.0.1
    - wry 🦀: 0.44.1
    - tao 🦀: 0.30.3
    - @tauri-apps/api : 2.0.2
    - @tauri-apps/cli : 2.0.2

[-] Plugins
    - tauri-plugin-single-instance 🦀: 2.0.1
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-os 🦀: 2.0.1
    - @tauri-apps/plugin-os : 2.0.0
    - tauri-plugin-global-shortcut 🦀: 2.0.1
    - @tauri-apps/plugin-global-shortcut : 2.0.0
    - tauri-plugin-log 🦀: 2.0.1
    - @tauri-apps/plugin-log : 2.0.0
    - tauri-plugin-process 🦀: 2.0.1
    - @tauri-apps/plugin-process : 2.0.0
    - tauri-plugin-fs 🦀: 2.0.1
    - @tauri-apps/plugin-fs : 2.0.0
    - tauri-plugin-autostart 🦀: 2.0.1
    - @tauri-apps/plugin-autostart : 2.0.0
    - tauri-plugin-window-state 🦀: 2.0.1
    - @tauri-apps/plugin-window-state : not installed!
    - tauri-plugin-dialog 🦀: 2.0.1
    - @tauri-apps/plugin-dialog : 2.0.0
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : 2.0.0
    - tauri-plugin-shell 🦀: 2.0.1
    - @tauri-apps/plugin-shell : 2.0.0
    - tauri-plugin-sql 🦀: 2.0.1
    - @tauri-apps/plugin-sql : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ollama
Issue: ollama --version to show build options
Labels: feature request

Can you please add a bit more information to `ollama --version` describing how ollama is built. Such as if it's built with CUDA, or ROCm, or CPU-only. This will be useful to know with a simple version request.
Repository: deno
Issue: deno fmt `<dir>` & `--ignore=<file in that dir>` non-deterministic precedence?
Labels: deno fmt,needs investigation

Version: Deno deno 2.0.0 (stable, release, x86_64-pc-windows-msvc)

I'm not entirely sure what's happening here, but these two deno invocations illustrate the issue.

In the first, I am checking formatting for the `scripts`, `src`, and `test` directories, but excluding one of the files within the `test` directory.  Deno does not exclude the file.  (9 files total)

In the second invocation, I tweak the command to specify `test` directory *twice*, keeping all other flags the same.  This time, `deno fmt` correctly excludes the excluded file.  (8 files total)

Is deno applying include and exclude rules in a non-deterministic order, so sometimes the file is included, and sometimes not?  Or is deno using caching that does not include all flags in the key, so I'm occasionally hitting corrupt cache, and occasionally not?

```
> deno fmt --check scripts src test --ignore=test/fixture/webpack-project/main.js
Error checking: G:\dev\@cspotcode\outdent\test\fixture\webpack-project\main.js
  Unexpected eof at file:///G:/dev/@cspotcode/outdent/test/fixture/webpack-project/main.js:7:1

    /*!************************************!*\
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    ~
error: Found 1 not formatted file in 9 files
> deno fmt --check test scripts src test --ignore=test/fixture/webpack-project/main.js
Checked 8 files
```
Repository: godot
Issue: Godot Android editor: Heavy projects occasionally crashing when playing since 4.4
Labels: bug,platform:android,topic:editor,needs testing,regression

### Tested versions

I'm trying out the mobile version of Godot Engine, but I'm facing some issues involving 3D and possibly 2D: When I start the project, the engine for some reason restarts by itself as if some failure had occurred. Obs: There is no error, not even in the scripts, but the engine still insists on restarting, This only happens when I start the project, mysterious crashes also occur, as the project is too small to make the device crash. I use a Moto G9 play.

Moto G9 play:
Qualcomm Snapdragon 665
Adreno 610
64GB and 4GB RAM
Android 10 (Updated to Android 11)

Godot Engine 4.4 dev3


### System information

Godot v4.4.dev3 - Android - Single-window, 1 monitor - Vulkan (Mobile) - integrated Adreno (TM) 610 -  (8 threads)

### Issue description

The Engine is restarting itself every time I start the project to test, even if it opens and loads correctly, the unwanted restart happens.

### Steps to reproduce

Engine problems, I haven't found any problems with GDscript so far.

### Minimal reproduction project (MRP)

No problem in settings
Repository: PowerToys
Issue: FancyZones - Maximize Window with [ctrl+win+up] on W11.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

Add functionality to maximize a window pressing [ctrl+win+up].

This feature is available on W10,
but it seems not available on W11.

Scenario when this would be used?
I have the same setttings file used on a W11 machine, coming from a W10 machine.

Override Windows Snap is active.
Move windows based on > Relative position.

I've posted this issue a small year ago
https://github.com/microsoft/PowerToys/issues/31098

### ✔️ Expected Behavior

Maximize Window with [ctrl+win+up] on W11

### ❌ Actual Behavior

[ctrl+win+up] on W11 does nothing

### Other Software

_No response_
Repository: ollama
Issue: The output dimension of the embedding model in Ollama is incorrect.
Labels: bug

### What is the issue?

I have a question. I noticed that when using Ollama for inference with certain models, such as conna-embedding v1, the output goes through embedding first, then pooling, and finally a dense layer that transforms a vector of shape 1024 into 1792. However, in Ollama's conna-embedding v1, the output dimension is only 1024 after inference, missing the operation of the dense layer. How can I solve this?

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.12
Repository: terminal
Issue: [Bug] "Open in Terminal" focuses on last session instead of selected folder
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-Windowing

### Windows Terminal version

7.4.5

### Windows build number

22631.4317

### Other Software

Using Terminal in combination with File Explorer has a certain risk. When you have closed Terminal with open sessions, it will focus on the last session NO MATTER how you have started Terminal again. Literally focusing on a session open in folder A, even though Terminal was started by the user telling it to open a new session in folder X. When you don't know this and start typing your commands right away without checking you might end up destroying your data depending on the operations you do. I happened to me in a hurry. It destroys your workflow. It opens two Terminal windows, one with the old sessions and a new window with the new session you've openend via the Explorer, but for some stupid reason the former gets the focus. 

### Steps to reproduce

- Open a few sessions in folders A, B, C.
- Close Terminal
- Use File Explorer to "Open in Terminal" folder X
- There a now two Terminal windows, and focus is on the one with the old sessions instead of the session you have started Terminal again for

### Expected Behavior

Open one Terminal window, add the new session to it, and give it focus. Or open two Terimal windows, the old session and in addition a new window with the new session that you actually want to work in, but focus on the latter.

### Actual Behavior

Old session steals the focus, you have to manually switch to the session you have just started with "Open in Terminal".
Repository: godot
Issue: SubViewport (with Size2D override stretch on) in collapsed split container causes affine_invert det==0 error
Labels: bug,topic:gui

### Tested versions

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

### System information

Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 32.0.101.6077) - 12th Gen Intel(R) Core(TM) i5-12500H (16 Threads)

### Issue description

I put a subviewport in a VSplitContainer with Size2D override stretch on.

When collapsed it keeps throwing 

```
E 0:00:01:0230   affine_invert: Condition "det == 0" is true.
  <C++ Source>   core/math/transform_2d.cpp:51 @ affine_invert()
```

The error is gone if I turn off Size2D override stretch.

Or disable subviewport updating before collapsing (try uncommenting the code in the script).

### Steps to reproduce

In editor:

Check collapsed on `VSplitContainer`

Or run the game and click toggle collapsed

### Minimal reproduction project (MRP)

[subviewportissue.zip](https://github.com/user-attachments/files/17349170/subviewportissue.zip)
Repository: rust
Issue: Remove `std.dll` from dist archives on Windows
Labels: A-testsuite,O-windows,T-compiler,A-incr-comp

Thanks to https://github.com/rust-lang/rust/pull/122362, `librustc_driver.so` no longer dynamically links to the standard library (`libstd.so`). And since https://github.com/rust-lang/rust/pull/131188, we no longer ship the dynamic libstd file on non-Windows platforms. This reduces the size of the dist rustup components that we ship.

However, we still ship `std.dll` on Windows, because removing it was causing incremental tests to fail in the post-optimization testing done by the `opt-dist` tool. More information can be found [here](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Failing.20incr.20tests.20on.20Windows.20when.20std.2Edll.20is.20missing).
Repository: rust
Issue: No documentation for minimal and maximal LLVM versions supported
Labels: A-docs

### Location

Nowhere

### Summary

When I build rustc with the local llvm, I want to know with what external LLVM versions will rustc work.

https://github.com/rust-lang/rust/pull/122649 upgrades in March the minimum external LLVM version to 17.
https://github.com/rust-lang/rust/pull/127513 updates in July LLVM to version 19.

But the above links do not touch the user-visible documentation.  For me it is unclear, if I want to compile rust 1.82 later, if I can use LLVM 18, or I must use LLVM 19. I find no place, where this is documented.

* Document the minimal and maximal versions for external LLVM supported by rustc.
Repository: flutter
Issue: [Flutter GPU] Add buffer->texture blit.
Labels: engine,P2,team-engine,triaged-engine,flutter-gpu

Add a DeviceBuffer->Texture blit command to CommandBuffer, which allows specifying the source buffer view (offset), destination rectangle, and destination mip level.

It's common for PBR renderers to perform expensive generation of radiance maps offline. As roughness increases, the radiance map should become more blurry in appearance. And so mipmaps are a very convenient and efficient way to sample radiance.
Repository: TypeScript
Issue: Capitalize and Uncapitalized are implemented multiple times
Labels: Infrastructure

### Acknowledgement

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

### Comment

The intrinsic type implementation for `Capitalize` and `Uncapitalize` are implemented multiple times in the `checker.ts`. They should be moved into a reusable function.

https://github.com/microsoft/TypeScript/issues/60206
Repository: vscode
Issue: [BUG] [1.94 Regression] VS Code uses the wrong, deprecated file/folder picker on Gnome.
Labels: linux,electron,upstream-issue-linked,native-file-dialog

Does this issue occur when all extensions are disabled?: Yes
- VS Code Version/OS version: 
```
Version: 1.94.2
Release: 24284
Commit: ea88724571c2cd4044155127c5ba85681e5cdcfe
Date: 2024-10-10T18:23:57.145Z
Electron: 30.5.1
ElectronBuildId: undefined
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Linux x64 6.11.2-zen1-1-zen
Desktop Environment: Gnome 47
```

Steps to Reproduce:

1. Open a new VS Code window
2. Click on "Open folder" from the primary sidebar.

Expected: 

VS Code opens the default Nautilus file explorer that it *used* to show priot to 1.94 update (see screenshot).
![Image](https://github.com/user-attachments/assets/ab6a2810-6416-4b9c-87a3-4dbacf2b1bc3)

Actual observation:
VS Code opens the GTK file explorer that is deprecated on Gnome in favor of the native file chooser
![Image](https://github.com/user-attachments/assets/2de65dbb-5a6d-4490-8ab4-7c61120437a3)

Additional information:
Prior to Gnome 47, the difference between the GTK file chooser and the nautilus file chooser was minimal. But since 47, the Gnome team has made massive improvements to the default file chooser which used to open perfectly correctly before the September 1.94 update.
Repository: next.js
Issue: `next/link` Link component creates a stackoverflow when navigating to a server component with a `redirect` logic
Labels: bug

### Link to the code that reproduces this issue

https://github.com/bwilytsch/redirect-nextjs-repro

### To Reproduce

1. Setup a new NextJS app using the app router
2. Create two nested routes e.g. `/dashboard` and `/dashboard/getting-started`
3. Add a `layout.tsx` server component to `/dashboard` with a redirect to `/dashboard/getting-started` when a condition is met.
4. In your root `page.tsx` use the `next/link` Link component to navigate to `/dashboard`

### Current vs. Expected behavior

# Current
`next/link` component creates a stackoverflow by getting stuck in an infinite react hook loop.

# Expected
To not do the above.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1-NixOS SMP PREEMPT_DYNAMIC Sun Sep 15 14:57:56 UTC 2024
  Available memory (MB): 31400
  Available CPU cores: 16
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 9.10.0
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: 14.2.15
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

Not sure

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

next dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

Not sure if this is a unique case, but we have to fetch some data for our redirect logic, which is why we can't do it via e.g. `middleware.ts`.

Also our example is a bit more complex than the on in the reproduction and affects child components as well, which is why it's currently in the `layout.tsx` component.

Appreciate any help on a potential fix. Thank you!