sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: `NavigationBar` should allow fixed size centered destinations in landscape mode
Labels: c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design

### Use case

In landscape mode on taller devices having 3 to 4 destinations present a bad UI by expanding all destinations to take the full width. Without having a fixed width option, we are forced to use `BottomNavigationBar` which might be deprecated in the future as per this [issue](https://github.com/flutter/flutter/issues/124885)

### Proposal

`NavigationBar` should allow fixed size centered destinations in landscape mode, which also complies with [M3 specs](https://m3.material.io/components/navigation-bar/guidelines#76819d14-8cba-4fd8-96dd-1ef5dca268d4)

> In landscape-oriented mobile screens, navigation bar destinations can retain the same spacing used in portrait mode, or be equally distributed across the container.

In older `BottomNavigationBar` we used to have `BottomNavigationBarLandscapeLayout.centered` to serve the same purpose, which seems was not ported to `NavigationBar` during M3 migration
Repository: vscode
Issue: Remote Tunnel VSCode Server install fails if WSL default shell is not Bash
Labels: bug,info-needed,remote-tunnel

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: N/A

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 
- OS Version: 

Steps to Reproduce:

1. Set WSL2 default shell (Ubuntu 24.04.1 LTS) to something other than Bash. [I primarily use non-POSIX shells like Fish, Nushell, and Elvish.]
2. Enable Remote Tunnel with Microsoft account on Windows 11 with WSL2.
3. Sign in to Microsoft account on vscode.dev, connect to Remote Tunnel, see that you can open folders and edit files from the Windows filesystem as expected.
4. Select Connect to WSL from the Command Palette, watch VSCode attempt to install/start the remote code server instance.
5. Watch the crashloop begin: ![Image](https://github.com/user-attachments/assets/6e799b77-e8ac-4a77-9250-df8be4ac91dc)

The error in the attached screenshot is effectively fatal, reloading the window over and over.
6. Close the tab.
7. Change the default shell for WSL2 to Bash (or possibly some other POSIX-compliant shell).
8. Reopen vscode.dev, connect to Remote Tunnel, Connect to WSL, watch the remote server installation succeed, then verify that you can open directories and edit files as expected.

I'm not sure what's going on behind the scenes with that code server install, but since launching `code` from WSL2 in any of the non-POSIX shells I use works just fine (i.e., delete `~/.vscode-server`, launch `code`, watch the magic happen), it suggests an assumption that the default shell will be Bash (or at least something POSIX-compliant) for the installation and connection via Remote Tunnel.
Repository: ui
Issue: [feat]: sidebar color option
Labels: area: request

### Feature description

The 'themes' page does not include a color option. Therefore, it does not follow the custom color theme. I think it needs options like these:

```
--sidebar-background: 222.2 84% 4.9%;
--sidebar-accent: 217.2 32.6% 17.5%;
```

https://ui.shadcn.com/themes

### Affected component/components

SideBar

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: kubernetes
Issue: Add QueueingHint for VolumeAttachment deletion events in CSI volume limits plugin
Labels: sig/scheduling,sig/storage,kind/feature,needs-triage

### What would you like to be added?

In #128337, we added `VolumeAttachment` deletion event to CSI volume limits plugin's `EventsToRegister`.

We should add a corresponding `QueueingHintFn` to make requeueing more efficient by allowing the plugin to filter out useless events.

/sig scheduling

### Why is this needed?

This is part of the effort to add `QueueingHints` to all scheduler plugins (#118893) to improve scheduling performance by preventing unnecessary retries.
Repository: next.js
Issue: Next.js 15 import alias not working with turbopack
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/aelassas/next-turbopack

### To Reproduce

Create a Next.js 15 project with an internal package `package1`:
```
| - my-app/
| - packages/package1/
```
Add the alias in tsconfig.json:
```js
{
  "compilerOptions": {
   ...
    "baseUrl": "./",
    "paths": {
      "@/*": ["./src/*"],
      ":package1": ["../packages/package1"],
    },
  }
}
```

Import `:package1` in a page or component:
```js
import * as package1 from ':package1'
...
```

Run the dev server with turbopack.

### Current vs. Expected behavior

When I run the dev server without turbopack, it works fine. But when I try with turbopack I always get this error:
```
Module not found: Can't resolve ':package1'
Import map: aliased to relative "../packages/package1" inside of [project]/
```

### Provide environment information

```bash
Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32593
  Available CPU cores: 12
Binaries:
  Node: 20.17.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.2-canary.7 // Latest available version is detected (15.0.2-canary.7).
  eslint-config-next: N/A
  react: 19.0.0-rc-1631855f-20241023
  react-dom: 19.0.0-rc-1631855f-20241023
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Turbopack

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

next dev (local)

### Additional context

_No response_
Repository: pytorch
Issue: What version or package name will be used in aarch64 release for 2.6 on pypi?
Labels: high priority,oncall: releng,triaged,module: regression

### 🐛 Describe the bug

An +cpu suffix is added to aarch64 (cpu) nightly package. https://github.com/pytorch/pytorch/pull/138588

Before
```
# https://download.pytorch.org/whl/nightly/cpu/torch-2.6.0.dev20241022-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
>>> torch.__version__
'2.6.0.dev20241022'
```
After
```
# https://download.pytorch.org/whl/nightly/cpu/torch-2.6.0.dev20241023%2Bcpu-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
>>> torch.__version__
'2.6.0.dev20241023+cpu'
```

For the name of aarch64 (cpu) package does not contain +cpu suffix on pypi in previous version, what version or package name will be used in aarch64 release for 2.6 on pypi?

### Versions

PyTorch version: 2.6.0.dev20241023+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: CentOS Linux 7 (AltArch) (aarch64)
GCC version: (GCC) 10.2.1 20210130 (Red Hat 10.2.1-11)
Clang version: Could not collect
CMake version: version 3.30.1
Libc version: glibc-2.17

Python version: 3.11.9 (main, Jul 15 2024, 06:10:42) [GCC 10.2.1 20210130 (Red Hat 10.2.1-11)] (64-bit runtime)
Python platform: Linux-4.18.0-80.7.2.el7.aarch64-aarch64-with-glibc2.17
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:          aarch64
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    1
Core(s) per socket:    16
Socket(s):             2
NUMA node(s):          2
Model:                 0
CPU max MHz:           2600.0000
CPU min MHz:           2600.0000
BogoMIPS:              200.00
L1d cache:             64K
L1i cache:             64K
L2 cache:              512K
L3 cache:              32768K
NUMA node0 CPU(s):     0-15
NUMA node1 CPU(s):     16-31
Flags:                 fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfhm

Versions of relevant libraries:
[pip3] numpy==1.24.4
[pip3] torch==2.6.0.dev20241023+cpu
[conda] Could not collect

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim
Repository: node
Issue: When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.
Labels: vm

### Version

v22.9.0

### Platform

```text
ubuntu 22.04
```


### Subsystem

_No response_

### What steps will reproduce the bug?

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.
![image](https://github.com/user-attachments/assets/5c3a4eec-b4b6-4ba4-b217-4fd2adf018f1)
mod is vm.script, I didn't set the execution timeout, if I use await here, he will be stuck here all the time

### How often does it reproduce? Is there a required condition?

every time

### What is the expected behavior? Why is that the expected behavior?

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.

### What do you see instead?

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.

### Additional information

When using microtaskMode: 'afterEvaluate', the program gets stuck in the vm and cannot return to the main program.
Repository: neovim
Issue: Insertion after expansion of snippet starts at wrong place
Labels: bug,snippet

### Problem

Original issue: https://github.com/Saghen/blink.cmp/issues/94

Many Lsp's auto import module before starting the completion, but doing so results in the starting of insertion at the wrong place, tested with clangd and gopls

https://github.com/user-attachments/assets/08c26e7c-a8de-4736-860b-feb7ea43cc42



### Steps to reproduce

1. nvim --clean random.txt
2. paste this into the file:
```lua
vim.snippet.expand('test(${1:ing})')
vim.lsp.util.apply_text_edits({
  {
    range = { start = { line = 0, character = 0 }, ['end'] = { line = 0, character = 0 } },
    newText = 'hello world\n',
  },
}, vim.api.nvim_get_current_buf(), 'utf-16')
``` 
3. press `o` on the last line
4. then do `luafile %`

### Expected behavior

the snippet expansion should start from the correct place

### Nvim version (nvim -v)

NVIM v0.11.0-dev-1043+ge4a74e986

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

dont think vim has snippet expansion

### Operating system/version

Arch Linux

### Terminal name/version

Ghostty

### $TERM environment variable

xterm-ghostty

### Installation

bob
Repository: next.js
Issue: Module '"next" has no exported member "X" (eg, 'Image', 'NextConfig').
Labels: bug,Module Resolution

### Link to the code that reproduces this issue

https://github.com/nextui-org/next-app-template

### To Reproduce

1. Upgrade to `v15` from `v14`
2. Enable turbopack
3. start dev server
*using typescript

### Current vs. Expected behavior

## Expected behevior
- Import stuff (like Image, Metadata) from `next` package
## Currently
- you can't

## Though you can: (**Fix**)
1. Disable turbopack
2. start dev server


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 ZEN SMP PREEMPT_DYNAMIC Tue, 22 Oct 2024 18:31:33 +0000
Binaries:
  Node: 20.18.0
  npm: N/A
  Yarn: N/A
  pnpm: 9.12.2
Relevant Packages:
  next: 15.0.1
  eslint-config-next: 15.0.1
  react: 19.0.0-rc-cae764ce-20241025
  react-dom: 19.0.0-rc-cae764ce-20241025
  typescript: 5.6.3
```


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

Module Resolution

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

next dev (local)

### Additional context

_No response_
Repository: vscode
Issue: Uninstall Copilot leaves the sidebar entirely empty without notice
Labels: bug,layout,workbench-auxsidebar

Steps to Reproduce:

1. install copilot
2. secondary sidebar shows
3. uninstall

=> 🐛 secondary sidebar is empty without notice to drop a view

![Image](https://github.com/user-attachments/assets/afc8aed8-558c-48d8-9a0b-72c6709dd660)
Repository: godot
Issue: Being able to access a non-existing member in another class during the static analysis of GDScript
Labels: discussion,topic:gdscript,documentation

### Tested versions

-Reproducible in 4.3 and 4.4dev
-Perhaps reproducible in previous versions

### System information

Windows 11

### Issue description

```GDScript
class D:
	var q = 1

class E:
	var d = D.new()

class F:
	var e = E.new()
	
	func _init() -> void:
		e.d._q = 5
```
In this example, q is the member of D. However, no matter what you input after `e.d.`, the error will never be triggered.

### Steps to reproduce

Copy the example code and paste it in a random script.

### Minimal reproduction project (MRP)

[inner-class-bug.zip](https://github.com/user-attachments/files/17529261/inner-class-bug.zip)
Repository: deno
Issue: Will Deno support node_api_basic_finalize?
Labels: suggestion,node compat,node native extension

It is still experimental in node, but I think it is a fantastic feature to simplify ffi modules.

https://github.com/nodejs/node/blob/0668e64cea127d8d4fa35d1b49bf11093ecc728f/doc/api/n-api.md?plain=1#L614

It allows finalisers to run outside the js context and so executed immediately as soon as the object is gc'ed, no need to wait for js to yield.
Repository: tensorflow
Issue: `data_flow_ops.Barrier` aborts with "Check failed: i >= 0 (0 vs. -100)" 
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.18

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf-nightly  2.19.0-dev20241025

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04.3 LTS

### 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?

I have confirmed that below code would crash on `tf-nightly 2.19.0-dev20241025` (nightly-build)

Please find the [gist](https://colab.research.google.com/drive/1OOOIvZ7brRDjRqshv36CA_55BlPbgI4e?usp=sharing) to reproduce the issue.

### Standalone code to reproduce the issue

```shell
from tensorflow.python.framework import dtypes
from tensorflow.python.ops import data_flow_ops
from tensorflow.python.eager import context
import tensorflow as tf

with context.graph_mode():
    sess = tf.compat.v1.Session()
    with sess.as_default():
        b = data_flow_ops.Barrier((dtypes.float32, dtypes.float32), shapes=((), ()), name='B')
        keys = [b'a', b'b', b'c', b'd']
        values_0 = [10.0, 20.0, 30.0, 40.0]
        values_1 = [100.0, 200.0, 300.0, 400.0]
        insert_1_1_op = b.insert_many(-100, keys[0:2], values_1[0:2]) 
        insert_1_1_op.run()
```


### Relevant log output

```shell
F tensorflow/core/kernels/barrier_ops.cc:286] Check failed: i >= 0 (0 vs. -100)
Aborted (core dumped)
```
Repository: tensorflow
Issue: `gen_list_ops.tensor_list_concat_v2` aborts with "Check failed: size >= 0 (0 vs. -1)"
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.18

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf-nightly  2.19.0-dev20241025

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04.3 LTS

### Mobile device

Linux Ubuntu 20.04.3 LTS

### Python version

3.10.14

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I have confirmed that below code would crash on `tf-nightly 2.19.0-dev20241025` (nightly-build)

Please find the [[gist](https://colab.research.google.com/drive/1Y-ZQk0KgIGfzCMfLVdemJ2UqXLeQWKUd?usp=sharing)](https://colab.research.google.com/drive/1Y-ZQk0KgIGfzCMfLVdemJ2UqXLeQWKUd?usp=sharing) to reproduce the issue.

### Standalone code to reproduce the issue

```shell
from tensorflow.python.framework import dtypes
from tensorflow.python.ops import gen_list_ops
from tensorflow.python.ops import list_ops

l = list_ops.tensor_list_reserve(element_dtype=dtypes.float32, element_shape=None, num_elements=3)
t = gen_list_ops.tensor_list_concat_v2(l, element_dtype=dtypes.float32, element_shape=list_ops._build_element_shape((None, 3)), leading_dims=[-1, 3, 5])
```


### Relevant log output

```shell
F tensorflow/core/framework/tensor_shape.cc:587] Check failed: size >= 0 (0 vs. -1)
Aborted (core dumped)
```
Repository: tensorflow
Issue: `lookup_ops.StaticVocabularyTable` and `lookup_ops.StaticVocabularyTableV1`  can cause a crash
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.18

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf-nightly  2.19.0-dev20241025

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04.3 LTS

### 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?

I encountered an `segmentation fault issue` in TensorFlow when I used API `lookup_ops.StaticVocabularyTable` or `lookup_ops.StaticVocabularyTableV1` . I have confirmed that below code would crash on `tf-nightly 2.19.0-dev20241025` (nightly-build).
Please find the [gist](https://colab.research.google.com/drive/1NGnFQqFl6Jy_Xt7wBL3ynmSVs9AiFw_l?usp=sharing) to reproduce the issue.

### Standalone code to reproduce the issue

```shell
import os
from tensorflow.python.ops import lookup_ops

def _createVocabFile(basename, values=('brain', 'salad', 'surgery')):
    vocabulary_file = os.path.join("/tmp", basename)
    with open(vocabulary_file, 'w') as f:
        f.write('\n'.join(values) + '\n')
    return vocabulary_file

vocab_file = _createVocabFile('feat_to_id_1.txt')
vocab_size = 9223372036854775807
oov_buckets = 1
table = lookup_ops.StaticVocabularyTable(lookup_ops.TextFileIdTableInitializer(vocab_file, vocab_size=vocab_size), oov_buckets, experimental_is_anonymous=True)
#lookup_ops.StaticVocabularyTableV1(lookup_ops.TextFileIdTableInitializer(vocab_file, vocab_size=vocab_size), oov_buckets, experimental_is_anonymous=True)
```


### Relevant log output

```shell
Segmentation fault (core dumped)
```
Repository: godot
Issue: Restrictive permissions on asset folder shows up as "invalid file" errors and creates import loops
Labels: bug,topic:editor,topic:import

### Tested versions

- Reproducible in: v4.3.stable.mono.official [77dcf97d8]

### System information

macOS - Sonoma 14.6.1 (23G93)

### Issue description

I moved an [asset pack](https://quaternius.com/packs/stylizednaturemegakit.html) into my project folder. For some reason, the pack comes with permission 555 on the directories.

When I returned to Godot, the import entered an infinite loop. It kept triggering the import process and failing with hundreds of errors like:

```
  Cannot open file from path 'res://assets/models/StylizedNatureMegaKit/Textures/Bark_DeadTree_Normal.png.import'.
  editor/editor_node.cpp:1278 - Condition "!res.is_valid()" is true. Returning: ERR_CANT_OPEN
  Cannot open file from path 'res://assets/models/StylizedNatureMegaKit/Textures/Leaves_GiantPine_C.png.import'.
  Cannot open file from path 'res://assets/models/StylizedNatureMegaKit/Textures/Leaves_TwistedTree_C.png.import'.
  Cannot open file from path 'res://assets/models/StylizedNatureMegaKit/Textures/Leaves_TwistedTree.png.import'.
  Cannot open file from path 'res://assets/models/StylizedNatureMegaKit/Textures/Leaves_NormalTree_C.png.import'.
  No loader found for resource: res://assets/models/StylizedNatureMegaKit/glTF/Leaves_TwistedTree_C.png (expected type: )
  modules/gltf/gltf_document.cpp:3534 - Condition "err != OK" is true.
  modules/gltf/gltf_document.cpp:3777 - Index image = 1 is out of bounds (p_state->images.size() = 0).
  modules/gltf/gltf_document.cpp:3777 - Index image = 0 is out of bounds (p_state->images.size() = 0).
  modules/gltf/gltf_document.cpp:3777 - Index image = 2 is out of bounds (p_state->images.size() = 0).
  Cannot open file from path 'res://assets/models/StylizedNatureMegaKit/glTF/TwistedTree_4.gltf.import'.
```

The assets show up with a red cross in the filesystem explorer,
you get `editor/editor_node.cpp:1278 - Condition "!res.is_valid()" is true. Returning: ERR_CANT_OPEN` when you try to double-click the file.

The feedback suggests an issue with the assets, as if the files are corrupted or invalid. The first search results discuss [invalid formats](https://www.reddit.com/r/godot/comments/vgilxn/error_failed_to_open_png/).

The solution is "just" to chmod 755 the directories.

Expected:
- The import process doesn't infinite loop,
- The import process shows clear feedback like `"Permission error when creating the res://some-file.import"`.


### Steps to reproduce

`cd assets; chmod 555 ./; touch ./some-file.jpg` go back to godot.

Using the free tier of the asset pack above gives the infinite loop for some reason.

### Minimal reproduction project (MRP)

[bug-report-permissions.zip](https://github.com/user-attachments/files/17529458/bug-report-permissions.zip)