sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Missing syntax highlighting for PHP `if-else` alternate syntax
Labels: bug,php,confirmation-pending


Type: <b>Bug</b>

While using the alternate syntax for the `if` statement in PHP, the `else` keyword is not being highlighted the same as `if` keyword.

![Image](https://github.com/user-attachments/assets/ff2898a7-a22f-41a8-864b-6ac00af9c523)



VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:

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

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) Ultra 5 125H (18 x 2995)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.61GB (5.37GB free)|
|Process Argv|--crash-reporter-id 42ce4d94-f018-448f-be6f-b9071de35767|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (22)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-intelephense-client|bme|1.12.6
simple-react-snippets|bur|1.2.8
vscode-eslint|dba|3.0.10
intelli-php-vscode|DEV|0.12.15062
phptools-vscode|DEV|1.53.16379
profiler-php-vscode|DEV|1.53.16379
es7-react-js-snippets|dsz|4.4.3
prettier-vscode|esb|11.0.0
code-runner|for|0.12.2
copilot|Git|1.246.0
copilot-chat|Git|0.22.4
path-autocomplete|ion|1.25.0
remote-wsl|ms-|0.88.5
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.11
cpptools-extension-pack|ms-|1.3.0
ts-file-path-support|ms-|1.0.0
vscode-react-native|msj|1.13.0
es7-react-js-snippets|rod|1.9.3
vscode-icons|vsc|12.9.0
vscode-wakatime|Wak|24.9.1
five-server|yan|0.3.1

(2 theme extensions excluded)

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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31185842
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

```

</details>

<!-- generated by issue reporter -->
Repository: kubernetes
Issue: Kubelet takes more than 10 minutes to pull up the pod
Labels: kind/bug,sig/node,triage/needs-information,needs-triage

### What happened?

Kubelet takes more than 10 minutes to pull up the pod，After adding logs for localization, it was found that it was `dswp.podManager.GetPods()` in  `findAndAddNewPods()`  method did not obtain the corresponding pod, suspecting that there is a problem with obtaining the lock. Causing waitForVolumeAttach (volumeToMount cache. VolumeToMount) to start slowly
`pkg/kubelet/volumemanager/populator/desired_state_of_world_populator.go   findAndAddNewPods() `

### What did you expect to happen?

After the pod is scheduled, operationExecutor.VerifyControlerAttachedVolume can start normally

### How can we reproduce it (as minimally and precisely as possible)?

Resolve the issue where GetPods() cannot access all pods

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```
v1.28.1
</details>


### Cloud provider

<details>
na
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: ui
Issue: [bug]: Confusing error message
Labels: bug

### Describe the bug

I did this

![image](https://github.com/user-attachments/assets/70ac90b2-5a80-40f8-8a9f-013f1c6b4602)


Which gave this error message:

![image](https://github.com/user-attachments/assets/894027cd-4883-4f12-a168-71f9a5107fea)


But I didn't use DialogTitle, so I spent a long time figuring out what's going on. It should say:

> Error: `SheetTitle` must be used within `Dialog` or `Sheet`

### Affected component/components

Sheet

### How to reproduce

1. Use `<SheetTitle>` without a `<Sheet>` parent

### Codesandbox/StackBlitz link

it's pretty easy to trigger this bug

### Logs

_No response_

### System Info

```bash
none, it's straightforward.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ant-design
Issue: 固定列有children时，无法固定在右侧
Labels: 🐛 Bug,help wanted,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/biao-tou-fen-zu-antd-5-22-2-forked-jx3y3f)

### Steps to reproduce

打开demo，滑到右侧，发现无法固定有children的列

### What is expected?

期望能整体固定

### What is actually happening?

无法固定

| Environment | Info |
| --- | --- |
| antd | 5.22.2 |
| React | 18 |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ollama
Issue: Installation not working on Fedora 41 Linux
Labels: bug

### What is the issue?

```
curl -fsSL https://ollama.com/install.sh | sh
> Installing ollama to /usr/local
> [sudo] password for bns: 
> >>> Downloading Linux amd64 bundle
> ######################################################################## 100.0%
> >>> Creating ollama user...
> >>> Adding ollama user to render group...
> >>> Adding ollama user to video group...
> >>> Adding current user to ollama group...
> >>> Creating ollama systemd service...
> >>> Enabling and starting ollama service...
> Created symlink '/etc/systemd/system/default.target.wants/ollama.service' → '/etc/systemd/system/ollama.service'.
> >>> Installing NVIDIA repository...
> Unknown argument "--add-repo" for command "config-manager". Add "--help" for more information about the arguments.
```

### OS

Linux

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: vscode
Issue: Don't import XYZ.contribution-files from non contribution/entry-files
Labels: debt,engineering

We discussed the side-effects that contribution files have and that "normal" files inherit these side effects as soon as they import them. The couple of take aways

* contribution files shouldn't export anything
* contribution files shouldn't be imported by normal files

Let's look into lint rules for this
Repository: flutter
Issue: [flutter_markdown] Allow specifying a custom image error builder
Labels: c: new feature,a: images,package,c: proposal,team-ecosystem,P2,p: flutter_markdown,triaged-ecosystem

### Use case

Developers that want to customize the layout of the error builder for images in markdown content.

### Proposal

In https://github.com/flutter/flutter/issues/158428 two problems were reported:
1) Invalid image urls caused crashes
2) there was no way to customize the error builder for the `Image` widget that resulted from parsing the markdown which had malformed image links (or errors during the loading of the image, per the functionality in Image.network's errorBuilder)

PR https://github.com/flutter/packages/pull/8058 addressed point 1, but point 2 was not yet implemented.

I propose we add an `imageErrorBuilder`, of type `ImageErrorWidgetBuilder?` next to https://github.com/flutter/packages/blob/main/packages/flutter_markdown/lib/src/widget.dart#L223
to fix the remaining work item. This error builder can be used in place of the default `kDefaultImageErrorWidgetBuilder`, when provided.

We probably also want to wire the image error builder up to https://github.com/flutter/packages/blob/main/packages/flutter_markdown/lib/src/builder.dart#L590
and https://github.com/flutter/packages/blob/main/packages/flutter_markdown/lib/src/builder.dart#L607
Repository: vscode
Issue: Git - Command `git.openFile` does not do the same thing as the "Open File" icon button on a file that has been committed in diff view
Labels: bug,git

<!-- ⚠️⚠️ 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?: Yes

<!-- 🪓 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: 1.96.0-insider
- OS Version: Ubuntu 24.04.1 LTS (6.8.0-49-generic)

Steps to Reproduce:

1. Setup a keybinding for the `git.openFile` command (in this case, it is `ctrl+alt+a`).
   ```json5
   // keybindings.json
   [
     // ...
     {
       "key": "ctrl+alt+a",
       "command": "git.openFile"
     }
   ]
   ```
2. Open a project with a git repository.
3. Make changes on a file (or a new file).
4. Stage the file.
5. Select the staged file to show the diff view. This should be readonly.
6. Commit the changes.
7. Then, click on the "Open File" icon button.
   - This should open the file (writable).
   - The tooltip also shows the keybinding for this action (`ctrl+alt+a` as expected).
8. Going back to the previous tab (the diff view), use the keybinding to open the file.
   - Unexpectedly, this opens a readonly editor even though "Open File" must be related to this keybinding because of the tooltip.
   - Using the keybinding on this readonly editor doesn't seem to do anything.

Additionally, the "Git: Open File" command is not available in the Command Palette (`ctrl+shift+p`) for both the diff view and the readonly editor, which I assume is `git.openFile`.

https://github.com/user-attachments/assets/d2a8a67e-c204-43d1-9520-9931fad16614

As reference, the [GitLens](https://github.com/gitkraken/vscode-gitlens) extension has a `gitlens.openWorkingFile` command that opens writable file from this diff view, similar to the "Open File" icon button.
Repository: node
Issue: fs.rmSync('速') crash without throw
Labels: confirmed-bug,fs,windows,good first issue

### Version

23.3.0

### Platform

```text
Windows 10
```


### Subsystem

_No response_

### What steps will reproduce the bug?

When `fs.rmSync('速')` files with name containing “速”, node 23.3.0 will crash without throw.


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

Everytime

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

Delete the file normally.

### What do you see instead?

The program just crashed.

### Additional information

There are other special characters that can cause similar problems, such as “請”. This problem did not occur in previous versions.
Repository: electron
Issue: [Bug]: On MacOS, desktopCapturer make window with resizeable:false resizeable
Labels: platform/macOS,bug :beetle:,status/confirmed,has-repro-gist,component/desktopcapturer,33-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

33.2.1

### What operating system(s) are you using?

macOS

### Operating System Version

Sequoia 15.1.1

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

The window should be not resizeable


### Actual Behavior

After 10 second, `desktopCapturer.getSources({ types: ['screen'] })` is called, and the window become resizeable


### Testcase Gist URL

https://gist.github.com/peernohell/301b616884c0ff02a77dda56b59aa8bd

### Additional Information

You can use the Electron Fiddle to reproduce the issue and use the latest Electron version.
Repository: bitcoin
Issue: ARM Windows build and release
Labels: Windows,Build system,Upstream

This was brought up recently:

* https://bitcointalk.org/index.php?topic=5517601.0
* https://groups.google.com/d/msgid/bitcoindev/e5b06aaa-1fe9-4c8f-a0ea-db10f8a7e48cn%40googlegroups.com
Repository: pytorch
Issue: Replace Miniconda with minforge as option
Labels: module: ci,triaged,enhancement,better-engineering

Subtask of  #138696: [CI/CD] Deprecating PyTorch’s official Anaconda channel.

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: flutter
Issue: Codelab word puzzle section 6 code sample does not have any import statements
Labels: team-codelabs,P1,triaged-codelabs

The code for [lib/widgets/crossword_info_widget.dart](https://github.com/flutter/codelabs/blob/main/generate_crossword/step_07/lib/widgets/crossword_info_widget.dart)

is missing the required imports (in the web page that describes what to do) and does not compile - however having copy / pasted the name of the file and checked the source I see that the source is OK, so it's a display issue of some sort for the web page).

I added these imports locally to make it work:

```
import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';

import '../providers.dart';
import '../utils.dart';
import './ticker_builder.dart';
```
Repository: TypeScript
Issue: Enable Type Checking for Custom File Extensions
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

"xsjs", "xsjslib", "hana", "file extensions"

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Enhance TypeScript's tsconfig.json to support type checking for files with unsupported extensions, such as "**/*.xsjs" and "**/*.xsjslib", when specified explicitly in the "include" config option

### 📃 Motivating Example

Support for SAP HANA server-side javascript and other javascript-based languages using custom file extensions

### 💻 Use Cases

We are using TypeScript to check our SAP HANA server-side javascript files (.xsjs) and library files(xsjslib).
To do so, we currently need to add at least two top-comments in each file:
```javascript
///<reference path"./pathto/config.xsjs" />
//@ts-check
```
In the config.xsjs we store all other triple-slash directives (like lib=es2016) to configure the typescript project.

It is really great that there's a way to enable type-checking on non-standard file extensions (at least in VSCode), but it would be great if you'd be able to configure an entire project which includes non-standard file extensions.
Repository: godot
Issue: Resizing button is lagging in theme preview
Labels: bug,topic:editor,needs testing,topic:gui,performance

### Tested versions

Happens since 4.3 dev3, 4.4 dev7

### System information

Godot v4.4.dev5 - Windows 10.0.19045 - Multi-window, 1 monitor - OpenGL 3 (Compatibility) - Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 threads)

### Issue description

In the theme preview the buttons change size when you hover over mouse.
The button size changes only if there is StyleBoxFlat in normal, the button size change seems to be delayed and late

https://github.com/user-attachments/assets/f61f31b2-f598-42a2-bc0c-2b3542ec7e55

### Steps to reproduce

1. Open MRP, create new Theme
2. Add StyleBoxFlat to normal
3. Hover over button in theme preview
4. Button is late

### Minimal reproduction project (MRP)

[gui.zip](https://github.com/user-attachments/files/17947487/gui.zip)
Repository: deno
Issue: deno init --npm vite doesn't exit after "Done" until you press Enter
Labels: bug,node compat

Very minor bug: After running `deno init --npm vite`, the Vite scaffolding finishes and says Done, but Deno doesn't exit until you press Enter. I waited a fair bit until I thought "What if I press a key?" and happened to pick Enter. (Just Space or something doesn't work.) May be related to #26403? `npm create vite` exits normally. (Thanks for all the Node compat stuff in Deno! Can't be easy.)

```
$ deno init --log-level=debug --npm vite
⚠️ Do you fully trust npm:create-vite package? Deno will invoke code from it with all permissions. Do you want to continue? [y/n]
> y
DEBUG RS - deno::args:587 - .npmrc found at: '/home/tjc/.npmrc'
DEBUG RS - deno::args:931 - Finished config loading.
DEBUG RS - deno::cache::cache_db:170 - Opening cache /home/tjc/.cache/deno/dep_analysis_cache_v2...
DEBUG RS - deno::cache::cache_db:170 - Opening cache /home/tjc/.cache/deno/node_analysis_cache_v2...
DEBUG RS - deno::npm::managed::resolution:282 - Running npm resolution.
DEBUG RS - deno_npm::resolution::graph:932 - <package-req> - Resolved create-vite@* to create-vite@6.0.1
DEBUG RS - deno::npm::managed:351 - Resolved package folder of create-vite@6.0.1 to /home/tjc/.cache/deno/npm/registry.npmjs.org/create-vite/6.0.1
DEBUG RS - deno::js:10 - Deno isolate init with snapshots.
DEBUG RS - deno::worker:198 - main_module file:///home/tjc/.cache/deno/npm/registry.npmjs.org/create-vite/6.0.1/index.js
? Project name: › vite-projectDEBUG RS - deno_runtime::worker:743 - received module evaluate Ok(
    (),
)
✔ Project name: … deno-vite
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /home/tjc/temp/deno-vite...

Done. Now run:

  cd deno-vite
  deno install
  deno run dev
```

*(Ignore the fact you see "Project name:" twice, that's only caused by `--log-level=debug`.)*

deno 2.1.1 (stable, release, x86_64-unknown-linux-gnu)
v8 13.0.245.12-rusty
typescript 5.6.2
Repository: electron
Issue: [Bug]On MacOS, small size transparent windows become opaque white on 4K external monitor
Labels: platform/macOS,bug :beetle:,has-repro-gist

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

33.2.1

### What operating system(s) are you using?

macOS

### Operating System Version

MacOS 13.5.1

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

window should be transparent
like this

![Image](https://github.com/user-attachments/assets/bbd706cb-2866-4345-b181-1cf7f585ea58)






### Actual Behavior

actually ， window become white background instead of transparent background
![Image](https://github.com/user-attachments/assets/7fbcb124-3de7-4cb6-98a3-49d1cf90e693)




### Testcase Gist URL

https://gist.github.com/e7611eda7db2ae9e7592ac1083486a22

### Additional Information

After testing, I found that the bug can be reproduced when the window width is less than 162px on my 4K screen. 
Larger windows do not reproduce the issue.

![Image](https://github.com/user-attachments/assets/81791ba7-aef1-44f9-aec9-d0c01fd0bc5a)
Repository: next.js
Issue: Next.js 15: Same-Path Redirect in Server Action Temporarily Breaks page.tsx Display
Labels: Navigation,linear: next

### Link to the code that reproduces this issue

https://github.com/y-hsgw/reproduction-next-app

### To Reproduce

1. `next dev`
2. Click the "go home" button

### Current vs. Expected behavior

As shown in the attached video, redirecting ( [redirect function](https://nextjs.org/docs/app/api-reference/functions/redirect) ) to the same path in Next.js 15 temporarily hides the content of page.tsx. This issue did not occur in Next.js 14. (You can confirm this by changing the version of Next.js in the attached repository to 14.2.18.)

https://github.com/user-attachments/assets/edf65b80-752d-4902-8471-73b1a4e62b77

I expect it to not temporarily disappear.

While I might be misunderstanding or missing something, I would appreciate it if you could look into this matter.



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:05:14 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8103
  Available memory (MB): 8192
  Available CPU cores: 8
Binaries:
  Node: 22.10.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 8.2.0
Relevant Packages:
  next: 15.0.4-canary.30 // Latest available version is detected (15.0.4-canary.30).
  eslint-config-next: N/A
  react: 19.0.0-rc-b01722d5-20241114
  react-dom: 19.0.0-rc-b01722d5-20241114
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_