id
int64 393k
2.82B
| repo
stringclasses 68
values | title
stringlengths 1
936
| body
stringlengths 0
256k
⌀ | labels
stringlengths 2
508
| priority
stringclasses 3
values | severity
stringclasses 3
values |
|---|---|---|---|---|---|---|
2,810,811,500 | PowerToys | Fancy Zones is so slow | ### Description of the new feature / enhancement
There's a delay between key-down of the shift key and the zone rectangles appearing. There's a delay between the mouse-up and the window fitting into the zone. These delays drop you out of your flow and make you wonder if Fancy Zones is working... it is... but losing your train of thought is frustrating, especially for something as trivial as moving windows.
### Scenario when this would be used?
All the time.
### Supporting information
_No response_ | Needs-Triage | low | Major |
2,810,812,744 | flutter | Blur not working as expected with impeller on Samsung galaxy s22 and some other devices | ### Steps to reproduce
1. create new flutter project with flutter create
2. paste code from code sample to your main.dart file
3. run this app on Samsung Galaxy s22 (i know this issue persist across some other devices but don't know exactly on which)
### Expected results
This is how blur expected to work video recorded on android emulator
https://github.com/user-attachments/assets/75e0f379-99ee-45c6-af2f-9ec324f2e7eb
### Actual results
This video recorded on Samsung Galaxy s22 and it is not working properly
https://github.com/user-attachments/assets/1a36c260-1452-4a44-a856-c0221510b128
It works well If i add this meta-data in AndroidManifest.xml
<meta-data
android:name="io.flutter.embedding.android.EnableImpeller"
android:value="false" />
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'dart:ui';
import 'package:flutter/material.dart';
void main() {
runApp(const App());
}
class App extends StatelessWidget {
const App({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
brightness: Brightness.dark,
useMaterial3: true,
),
darkTheme: ThemeData(brightness: Brightness.dark),
themeMode: ThemeMode.dark,
debugShowCheckedModeBanner: false,
debugShowMaterialGrid: false,
home: const HomePage(),
);
}
}
class HomePage extends StatelessWidget {
const HomePage({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: const Text('Home Page'),
),
body: ListView.builder(
itemBuilder: (context, index) {
return SizedBox(
height: 320,
child: ListView.separated(
padding: const EdgeInsets.symmetric(horizontal: 16),
itemCount: 10,
clipBehavior: Clip.none,
scrollDirection: Axis.horizontal,
itemBuilder: (context, index) {
return ClipRRect(
borderRadius: BorderRadius.circular(8),
child: Image.network(
'https://picsum.photos/200/300',
width: 200,
height: 300,
),
);
},
separatorBuilder: (context, index) => SizedBox(width: 8),
),
);
},
),
extendBody: true,
bottomNavigationBar: RepaintBoundary(
child: ClipRect(
child: BackdropFilter(
filter: ImageFilter.blur(sigmaX: 10, sigmaY: 10),
child: Material(
elevation: 10,
color: Colors.black.withValues(alpha: 0.5),
child: Padding(
padding: EdgeInsets.fromLTRB(
30.0,
0,
30.0,
0,
),
child: SizedBox(
height: 52,
width: double.infinity,
child: Row(
mainAxisAlignment: MainAxisAlignment.spaceBetween,
children: [],
),
),
),
),
),
),
),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.27.3, on macOS 15.2 24C101 darwin-arm64, locale
ru-TM)
• Flutter version 3.27.3 on channel stable at
/Users/serdar/Documents/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (4 дня назад), 2025-01-21 10:32:23 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version
35.0.0-rc3)
• Android SDK at /Users/serdar/Library/Android/sdk
• Platform android-35, build-tools 35.0.0-rc3
• Java binary at: /Applications/Android
Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build
17.0.9+0-17.0.9b1087.7-11185874)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16C5032a
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2023.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
17.0.9+0-17.0.9b1087.7-11185874)
[✓] VS Code (version 1.96.4)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (4 available)
• sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64 •
Android 14 (API 34) (emulator)
• macOS (desktop) • macos • darwin-arm64 •
macOS 15.2 24C101 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin •
macOS 15.2 24C101 darwin-arm64
• Chrome (web) • chrome • web-javascript •
Google Chrome 132.0.6834.110
! Error: Browsing on the local area network for iPhone. Ensure the device is
unlocked and attached with a cable or associated with the same local area
network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code
-27)
! Error: Browsing on the local area network for ayna. Ensure the device is
unlocked and attached with a cable or associated with the same local area
network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code
-27)
[✓] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| waiting for customer response,in triage | low | Critical |
2,810,812,951 | ollama | Context caching in RAM | I have been thinking about the possibility of caching computed context into RAM. Let me explain, how it could be helpful on cheaper HW, that many of us are running.
The challenges:
1) you have limited VRAM. You have to split it between model and context cache (context length). As you are using the server alone (or with a few friends), you do not really need concurency, so you allow only one context to be stored. That means more VRAM for model and 1 context.
2) you sometimes want to chat about different things in different chats (especially when using WebUI), seems like kind of a natural workflow.
3) you sometimes want some inference at roughly the same time as your friend (pretty similar from the ollama standpoint)
4) whenever you send a prompt, it gets ingested and you get the response. When you send response to that, the context is already cached = immediate inference.
5) when you switch chats or a friend starts their own conversation, the pre-computed context is gone.
6) especially for longer conversations (e.g. coding or deep philosophical discussions idk) it takes long for the whole conversation to be ingested again, so that next response could be inferenced.
Here comes the idea of the context caching to RAM to the rescue. RAM is relatively cheap and CPU/RAM inference is usually slow compared to GPU/VRAM (most of us do not have Genoas with lot of memory bandwidth). My proposal:
1) allow to allocate memory in RAM specifically for a specified number of context caches.
2) the "normal" number of contexts would still be allocated in VRAM, it needs to be accessible with high bandwidth.
3) keep sort of a FIFO in RAM (if you choose to allocate more space for context cache in RAM), so that the oldest contexts are discarded first
4) when you detect that there is a continuation of previous conversation, first check if the pre computed context is cached, if so, load it into VRAM basically instantly (versus computing it again for longer contexts..)
What do you think? Is it doable? Is it a silly idea? Are there limitations I do not see? Is it "too much my usecase"? I do not really know! :)
Last but not least, thank you all for your wonderful work! <3 | feature request | low | Major |
2,810,820,809 | ant-design | input inside dropdown of form item of select will inherit error status of select | ### Reproduction link
[](https://codesandbox.io/p/sandbox/wvk5xh)
### Steps to reproduce
submit to make select got error status then click select to see input status
<img width="472" alt="Image" src="https://github.com/user-attachments/assets/14b4920d-048a-4180-908d-586b90121994" />
### What is expected?
input inside dropdown should not inherit error status of parent select
### What is actually happening?
input inside dropdown inherit error status of parent select
| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18.3.1 |
| System | macOS 15.1.1 |
| Browser | Chrome |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | 🤔 Need Reproduce | low | Critical |
2,810,824,589 | rust | `#[thread_local]`s are pessimized in `#[no_mangle]` functions | ```rust
#![feature(thread_local)]
use std::cell::Cell;
#[thread_local]
static THREAD_LOCAL: Cell<bool> = const { Cell::new(false) };
pub fn pub_mentions_thread_local() {
let _ = THREAD_LOCAL;
}
#[no_mangle]
fn no_mangle_uses_thread_local() {
let r = &THREAD_LOCAL;
if !r.get() {
r.set(true);
}
}
```
compiles to:
```asm
no_mangle_uses_thread_local:
push rax
data16
lea rdi, [rip + example::THREAD_LOCAL::h5a1be4459c52c6f4@TLSGD]
data16
data16
rex64
call __tls_get_addr@PLT
cmp byte ptr [rax], 0
jne .LBB0_2
data16
lea rdi, [rip + example::THREAD_LOCAL::h5a1be4459c52c6f4@TLSGD]
data16
data16
rex64
call __tls_get_addr@PLT
mov byte ptr [rax], 1
.LBB0_2:
pop rax
ret
example::THREAD_LOCAL::h5a1be4459c52c6f4:
.zero 1
```
(https://godbolt.org/z/K69s4fzzz)
i.e. two accesses under the `global-dynamic` TLS model. I have two questions here:
1. Why is the TLS resolved twice? It's sound to resolve it only once; in fact, the source code takes `&THREAD_LOCAL` just once. This might be an LLVM problem.
2. Why is `global-dynamic` used instead of `local-dynamic`? Removing `pub` from `pub_mentions_thread_local`, deleting `pub_mentions_thread_local` altogether, or adding `#[no_mangle]` to it fixes this, even though that function literally has an empty MIR. This makes me suspect this is not an LLVM bug.
[Here's another example.](https://godbolt.org/z/4fbnzcMGd)
I'm not positive that `#[no_mangle]` is to blame here, but that's the closest I have to a non-generic title.
`std::thread_local!` is unaffected.
@rustbot label +A-codegen +A-thread-locals +C-optimization +F-thread_local +T-compiler | A-codegen,T-compiler,A-thread-locals,F-thread_local,C-optimization | low | Critical |
2,810,839,707 | vscode | Hot Exit bug | <!-- ⚠️⚠️ 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/No
<!-- 🪓 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:
There is a bug with hot exit disabled. It cannot really be disabled, and that's very frustrating to people who never want all this autosave nonsense.
Steps to Reproduce:
1. Set `files.hotExit` to `Off`
2. Type "Should Not Be Saved" on a Jupyter notebook.
3. Close the Jupyter notebook without saving it.
4. Reopen the Jupyter notebook.
5. That "Should Not Be Saved" text is still on the notebook, even though it wasn't saved.
This behavior is very frustrating, as it makes it impossible to keep track of which edits were discarded and which were saved and what was really the last saved state of a document. To be really safe, one has to immediately close and relaunch VS Code every time a file is closed without saving it. | info-needed | low | Critical |
2,810,844,033 | PowerToys | If PowerToys run shortcut is set to win+space, it also activates Click To Do in Windows. | ### Microsoft PowerToys version
0.87.1
### Installation method
WinGet
### Running as admin
No
### Area(s) with issue?
PowerToys Run
### Steps to reproduce
Use Windows Insider Dev with Click To Do on Copilot+ PC
Set shortcut for activating PowerToys Run to Win+Space
Activate PowerToys Run with Win+Space
*Notes*
Win + Space only activates click to do when it's set as a PowerToys Run shortcut. If PowerToys Run is set to a different shortcut, Win+Space no longer activates Click To Do.
I've also reported this to the black hole that is the Windows Feedback Hub (https://aka.ms/AAu38pk)) because it could be a bug in either piece of software, but it will likely never be found there.
### ✔️ Expected Behavior
Only PowerToys Run activates, as normal
### ❌ Actual Behavior
PowerToys Run activates, and Windows Click To Do starts, which makes interaction with the system difficult.
### Other Software
Windows on Copilot+ PC with Click To Do (Win version 26120.3000+) | Issue-Bug,Needs-Triage | low | Critical |
2,810,846,746 | vscode | Sluggish after Nvidia 570 driver upgrade |
Type: <b>Bug</b>
I upgraded my desktop from 560 to 570 using the open kernel module driver. After restarting my system, user input to VSCode has become very laggy.
Things I've tried with no change in behaviour:
> code --disable-gpu
> disabling all extensions and restarting
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Linux x64 6.8.0-51-generic snap
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 9 5950X 16-Core Processor (32 x 4203)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: disabled_off<br>webnn: unavailable_software|
|Load (avg)|6, 3, 2|
|Memory (System)|62.71GB (50.70GB free)|
|Process Argv|--no-sandbox --disable-gpu --crash-reporter-id 614587e4-7906-4b53-9257-22b30aabc6b8|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu-wayland|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu-wayland|
|XDG_SESSION_TYPE|wayland|
</details><details><summary>Extensions (72)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-django|bat|1.15.0
pythoncpp-debug|ben|0.3.0
cmake-format|che|0.6.11
doxdocgen|csc|1.4.0
python-environment-manager|don|1.2.7
python-extension-pack|don|1.7.0
gitlens|eam|16.2.1
scalene|Eme|0.0.10
shell-format|fox|7.2.5
matlab|Gim|3.0.2
copilot|Git|1.259.0
copilot-chat|Git|0.23.2
vscode-github-actions|git|0.27.0
go|gol|0.44.0
gc-excelviewer|Gra|4.2.62
huggingface-vscode|Hug|0.2.2
better-cpp-syntax|jef|1.27.1
cmake-language-support-vscode|jos|0.0.9
vsc-python-indent|Kev|1.19.0
restructuredtext|lex|190.4.5
restructuredtext-pack|lex|1.0.3
language-matlab|Mat|1.3.1
rainbow-csv|mec|3.15.0
vscode-docker|ms-|1.29.4
vscode-dotnet-runtime|ms-|2.2.5
vscode-kubernetes-tools|ms-|1.3.18
black-formatter|ms-|2024.4.0
debugpy|ms-|2024.14.0
isort|ms-|2023.10.1
pylint|ms-|2024.0.0
python|ms-|2024.23.2025012401
vscode-pylance|ms-|2024.12.1
vscode-python-envs|ms-|0.1.2025012401
datawrangler|ms-|1.16.0
jupyter|ms-|2024.11.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
remote-containers|ms-|0.394.0
remote-ssh|ms-|0.116.1
remote-ssh-edit|ms-|0.87.0
remote-wsl|ms-|0.88.5
vscode-remote-extensionpack|ms-|0.26.0
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.11
cpptools-extension-pack|ms-|1.3.0
makefile-tools|ms-|0.11.13
powershell|ms-|2025.0.0
remote-explorer|ms-|0.4.3
remote-server|ms-|1.5.2
veriloghdl|msh|1.16.0
resourcemonitor|mut|1.0.7
autodocstring|njp|0.6.1
nsight-vscode-edition|nvi|2024.1.34572442
sqlite-viewer|qwt|0.9.6
vscode-yaml|red|1.15.0
esbonio|swy|0.11.0
even-better-toml|tam|0.21.2
qt|the|1.0.2
qt-core|the|1.2.1
qt-cpp|the|1.2.1
qt-qml|the|1.2.1
qt-ui|the|1.2.1
pdf|tom|1.2.2
simple-rst|tro|1.5.4
cmake|twx|0.0.17
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vim|vsc|1.29.0
jinja|who|0.0.8
vscode-proto3|zxh|0.5.5
(1 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730
```
</details>
<!-- generated by issue reporter --> | freeze-slow-crash-leak | low | Critical |
2,810,850,635 | PowerToys | Dedicate some keyboard keys to a specific windows | ### Description of the new feature / enhancement
Imagine you have 2 windows opened, one VLC for playing a teacher and another for Word where you want to write what the teacher is saying.
you want to be able to pause the VLC without moving and clicking to the VLC windows, hence dedicate one key like the space key to the windows of VLC.
It is true that the space key is also useful for writing, but there are other key like for example the arrow key which are not very useful for writing and can add or subtract a 10s to VLC streaming. In that case, it will be very useful
### Scenario when this would be used?
Imagine you have 2 windows opened, one VLC for playing a teacher and another for Word where you want to write what the teacher is saying.
you want to be able to pause the VLC without moving and clicking to the VLC windows, hence dedicate one key like the space key to the windows of VLC.
It is true that the space key is also useful for writing, but there are other key like for example the arrow key which are not very useful for writing and can add or subtract a 10s to VLC streaming. In that case, it will be very useful
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,810,852,568 | transformers | Huggingface/transfomers v3.3.2 is throwing import errors when building on Nextjs 14 | ### System Info
Operating System: MacOS Sequoia 15.2
Hardware: M1 Macbook Pro
### Who can help?
@zucchini-nlp @muellerzr
I get this error when I run`pnpm build` to build my project to production but it kept throwing this error. I've tried downgrading the version of @huggingface/transformers package to v3.0.0 and v3.0.2 but I can't even get the model to run at all.
### Information
- [ ] The official example scripts
- [x] My own modified scripts
### Tasks
- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [x] My own task or dataset (give details below)
### Reproduction
Here are the steps needed to reproduce the error
1. Set up a simple nextjs app
2. pnpm install @huggingface/transformers
3. run `pnpm build`
### Expected behavior
The expected behavior is to be able to successfully build the nextjs application so that I can host it and allow users to use my app | bug | low | Critical |
2,810,878,252 | godot | Fix StatusIndicator tooltip typo in Create New Node menu | ### Tested versions
Reproducable in: 4.3 stable
Testing earlier versions not necessary, this has likely existed since the addition of the node StatusIndicator, or if there was a formatting migration, this would have happened during that.
### System information
Godot v4.3.stable - Linux Mint 22 (Wilma) - X11 - GLES3 (Compatibility) - NVIDIA GeForce GTX 960M (nvidia; 550.120) - Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (4 Threads)
### Issue description
Tooltip in Create New Node menu for StatusIndicator contains the following string: `[b]note:[/b]` which is clearly intended to apply **bold** formatting to the word "note" but fails and displays the formatting code.
I would provide a screenshot, but doing anything that unfocuses the Godot window for even a tiny moment, such as taking a screenshot, causes the tooltip to fade before an image can be captured.
### Steps to reproduce
1. open the "Create New Node" menu by pressing ctrl+A or clicking the plus sign above the node tree
2. Click on the search bar and look for "StatusIndicator"
3. Hover your mouse over the node option named "StatusIndicator" until a tooltip pops up
4. read the tooltip.
### Minimal reproduction project (MRP)
N/A | bug,topic:editor | low | Minor |
2,810,887,304 | angular | extend streaming resource with {status} capability | ### Which @angular/* package(s) are relevant/related to the feature request?
core
### Description
After playing around with the new streaming resource in 19.2.0-next.0 I thought about different usecases where I would like to use this.
First: the resource is only in "Loading" state when a new request is emitted until the promise resolves with the first (signal of) value. Afterwards, when a new value is emitted the resource will just update. This is fine!
But what if the implementation "knows" when it is fetching a value?
Example 1: Polling
Imagine some API which doesn't support streaming, so it has to be polled. The "poller" would then know when it is going to fetch the next value (even on the same request).
Example 2: Retry
Imagine some streaming resource implementation which automatically retries after an error occured. It will then know when it is "Reloading".
### Proposed solution
Extend the type of the signal with
```ts
{ value: T }
| { error: unknown }
| { status: ResourceStatus.Loading | ResourceStatus.Reloading }
```
When the signal of the streaming resource emits a "status" the `Resource<T>` transitions to the given state (I don't think the other `ResourceStatus` values make sense here).
### Alternatives considered
Currently the implementation would have to encode the (re)loading information into its value and that can't be populated to the `Resource<T>`'s status. | area: core,core: reactivity,cross-cutting: signals | low | Critical |
2,810,898,069 | rust | Crash writing PNG from a C++ background thread on macOS Rust 1.84.0 | I'm writing PNG files from a C++ background thread. It used to work on Rust stable 1.83.0, but it crashes on Rust stable 1.84.0 and nightly. I'm using the `png` crate, but it or its dependencies [shouldn't have any code](https://github.com/Frommi/miniz_oxide/issues/160), which would cause the crash.
The crash happens on macOS and Rust 1.84.0 (I tested on arm and intel macs). The program runs without issues on Ubuntu linux Rust 1.84.0. I didn't test Windows. There are no issues writing PNGs from the C++ main thread, but PNG writing crashes on the C++ background thread. If I write the same program in pure Rust without ffi and using Rust threads, then everything works without issues.
Could this be a regression in the Rust standard library? Or is the Rust function called from the C++ background thread in a way that is incompatible with Rust 1.84.0?
### Code
Here's a minimal example project as a zip file so that you can see the code and try it yourself: [test-cthread-png.zip](https://github.com/user-attachments/files/18545493/test-cthread-png.zip)
I expected to see this happen: Two PNG files should be written to the current folder: 'out-png-1.png' and 'out-png-2.png'
Instead, this happened: Only one PNG file is written: 'out-png-1.png' (on the main thread) and then the program crashes:
```
Rust PNG writing to 'out-png-1.png'
Waiting thread to finish..
Rust PNG writing to 'out-png-2.png'
zsh: bus error ./main
```
### Version it worked on
It most recently worked on: Rust 1.83
### Version with regression
`rustc --version --verbose`:
```
rustc 1.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: aarch64-apple-darwin
release: 1.84.0
LLVM version: 19.1.5
```
### LLVM Stack Trace
<details><summary>Stack trace of the example project</summary>
<p>
```
Process 62208 launched: '/Users/temp/rust/test-cthread-png/main' (arm64)
Rust PNG writing to 'out-png-1.png'
Waiting thread to finish..
Rust PNG writing to 'out-png-2.png'
Process 62208 stopped
* thread #2, stop reason = EXC_BAD_ACCESS (code=2, address=0x16fe036b0)
frame #0: 0x000000010005a334 main`alloc::boxed::Box$LT$core..mem..maybe_uninit..MaybeUninit$LT$T$GT$$C$A$GT$::write::hf0470a3673d75fd5(boxed=0x0000000000000000, value=<unavailable>) at boxed.rs:1008
1005 /// ```
1006 #[unstable(feature = "box_uninit_write", issue = "129397")]
1007 #[inline]
-> 1008 pub fn write(mut boxed: Self, value: T) -> Box<T, A> {
1009 unsafe {
1010 (*boxed).write(value);
1011 boxed.assume_init()
Target 0: (main) stopped.
(lldb) thread backtrace
* thread #2, stop reason = EXC_BAD_ACCESS (code=2, address=0x16fe036b0)
* frame #0: 0x000000010005a334 main`alloc::boxed::Box$LT$core..mem..maybe_uninit..MaybeUninit$LT$T$GT$$C$A$GT$::write::hf0470a3673d75fd5(boxed=0x0000000000000000, value=<unavailable>) at boxed.rs:1008
frame #1: 0x000000010005a540 main`_$LT$alloc..boxed..Box$LT$T$GT$$u20$as$u20$core..default..Default$GT$::default::h770abf79bd18dfcf at boxed.rs:1733:9
frame #2: 0x0000000100045818 main`miniz_oxide::deflate::core::DictOxide::new::hf9b523780f33e231(flags=4112) at core.rs:1156:16
frame #3: 0x000000010004116c main`_$LT$miniz_oxide..deflate..core..CompressorOxide$u20$as$u20$core..default..Default$GT$::default::h98fdbfee01692241 at core.rs:436:19
frame #4: 0x000000010003dea8 main`_$LT$alloc..boxed..Box$LT$T$GT$$u20$as$u20$core..default..Default$GT$::default::h89b44e0f0b402adf at boxed.rs:1733:39
frame #5: 0x000000010003ecc8 main`_$LT$flate2..ffi..rust..Deflate$u20$as$u20$flate2..ffi..DeflateBackend$GT$::make::hee247c1da637a407(level=(__0 = 6), zlib_header=true, _window_bits='\x0f') at rust.rs:131:47
frame #6: 0x000000010003fc8c main`flate2::mem::Compress::new::h1c4d10d7643a257f(level=(__0 = 6), zlib_header=true) at mem.rs:197:20
frame #7: 0x000000010002d1dc main`flate2::zlib::write::ZlibEncoder$LT$W$GT$::new::h9b8a7495719a8ece(w=Vec<u8, alloc::alloc::Global> @ 0x000000016fe863a8, level=(__0 = 6)) at write.rs:43:40
frame #8: 0x000000010000c398 main`png::encoder::Writer$LT$W$GT$::write_image_data::h1a6cf982c65de46c(self=0x000000016fe86b98, data=(data_ptr = "", length = 307200)) at encoder.rs:742:32
frame #9: 0x000000010000b99c main`rspng_write(filenumber='\x02') at lib.rs:20:8
frame #10: 0x00000001000022fc main`MyThread::run(this=0x000000016fdff32b) at main.cpp:9:13
frame #11: 0x0000000100002e54 main`decltype(*std::declval<MyThread*>().*std::declval<void (MyThread::*)()>()()) std::__1::__invoke[abi:ne180100]<void (MyThread::*)(), MyThread*, void>(__f=0x0000600002b940c8, __a0=0x0000600002b940d8) at invoke.h:312:25
frame #12: 0x0000000100002d84 main`void std::__1::__thread_execute[abi:ne180100]<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (MyThread::*)(), MyThread*, 2ul>(__t=size=3, (null)=__tuple_indices<2UL> @ 0x000000016fe86f7f) at thread.h:199:3
frame #13: 0x0000000100002680 main`void* std::__1::__thread_proxy[abi:ne180100]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (MyThread::*)(), MyThread*>>(__vp=0x0000600002b940c0) at thread.h:208:3
frame #14: 0x0000000188b272e4 libsystem_pthread.dylib`_pthread_start + 136
(lldb)
```
</p>
</details>
| C-external-bug | low | Critical |
2,810,898,344 | rust | Should generate llvm.threadlocal.address for TLS accesses | See https://llvm.org/docs/LangRef.html#llvm-threadlocal-address-intrinsic. Instead of directly accessing the global, the result of `@llvm.threadlocal.address(ptr @g)` should be accessed.
This is required for correctness when using LLVM coroutines (not relevant for Rust), but it should also improve codegen in some cases because it will allow CSE/LICM of the TLS address calculation. | A-LLVM,T-compiler,A-thread-locals,C-bug | low | Minor |
2,810,901,019 | rust | `DerefPure` impl for `Cow` may be too general | <!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->
One of `unsafe trait DerefPure`'s preconditions is that `Self`'s `Deref` impl is "well-behaved". `std::borrow::Cow` currently always implements `DerefPure`, but `Cow<B>`'s `Deref` impl can call arbitrary user code in `<B::Owned as Borrow<B>>::borrow` that may not be "well-behaved".
I tried this (safe) code:
```rust
#![feature(deref_patterns)]
use std::borrow::{Cow, Borrow};
struct Weird<T: ?Sized = [()]>(bool, T);
struct WeirdOwned {
val: std::cell::Cell<bool>,
}
impl Borrow<Weird> for WeirdOwned {
fn borrow(&self) -> &Weird {
let val = self.val.get();
self.val.set(!val);
if val { &Weird(true, []) } else { &Weird(false, []) }
}
}
impl ToOwned for Weird {
type Owned = WeirdOwned;
fn to_owned(&self) -> WeirdOwned {
WeirdOwned {
val: false.into(),
}
}
}
fn main() {
let x: Cow<Weird> = Cow::Owned(WeirdOwned { val: true.into() });
match x {
deref!(Weird(false, _)) | deref!(Weird(true, _)) => println!("a"),
_ => println!("b"),
}
// prints b
let x: Cow<Weird> = Cow::Owned(WeirdOwned { val: true.into() });
match x {
deref!(Weird(false, _) | Weird(true, _)) => println!("a"),
_ => println!("b"),
}
// prints a
}
```
I expected to see this happen: Either this shouldn't compile (because `Cow<Weird>`'s `Deref` impl is not "well-behaved"), or the first match should also print "a".
Instead, this happened: Having two separate `deref!` patterns joined by an or-pattern behaves differently than an or-pattern in a `deref!` pattern. IIUC currently there is no soundness issue because deref patterns do not interact with exhaustiveness checking, but if the first match didn't require the blanket `_` arm and considered `deref!(Weird(false, _)) | deref!(Weird(true, _))` exhaustive, then the exhibited behavior would be a soundness issue.
-----
One possible resolution might be to restrict `Cow`'s `DerefPure` impls to just `Cow<T: Sized>`, `Cow<str>`, `Cow<[T]>`, and other types that the stdlib fully controls the `ToOwned`/`Borrow`/`Deref` impls of.
```diff
-unsafe impl<B: ?Sized + ToOwned> DerefPure for Cow<'_, B> where B::Owned: Borrow<B> {}
+unsafe impl<T: Clone> DerefPure for Cow<'_, T>{}
+unsafe impl DerefPure for Cow<'_, str>{}
+unsafe impl<T: Clone> DerefPure for Cow<'_, [T]>{}
```
<details> <summary> incorrect suggestion </summary>
Moved this into a hidden block because this would **not** work with `Cow<T: Sized>`, since `T::Owned = T`, which probably doesn't implement `Deref<Target = T> + DerefPure`.
> One possible resolution might be to add "`Borrow<Self::Target>`/`BorrowMut<Self::Target>` are well-behaved if implemented" to `DerefPure`'s preconditions, and then change `Cow`'s impl as follows:
>
> ```diff
> -unsafe impl<B: ?Sized + ToOwned> DerefPure for Cow<'_, B> where B::Owned: Borrow<B> {}
> +unsafe impl<B: ?Sized + ToOwned> DerefPure for Cow<'_, B> where B::Owned: Borrow<B> + Deref<Target = B> + DerefPure {}
> ```
>
> Then, `Cow<Weird>` would not implement `DerefPure`, because `WeirdOwned` does not implement `DerefPure`. This would still allow `Cow<str>`, and `Cow<[T]>` (since `String` and `Vec<T>` implement `DerefPure`), but this would **not** work with `Cow<T: Sized>`, since `T::Owned = T`, which might not implement `DerefPure`, and probably doesn't implement `Deref<Target = T>`.
>
> Note that *just* adding `B::Owned: DerefPure` is not sufficient, since you could have `Weird::Owned = Box<WeirdOwned>`, and `Box: DerefPure`.
</details>
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
`rustc --version --verbose`:
```
rustc 1.86.0-nightly (649b995a9 2025-01-22)
binary: rustc
commit-hash: 649b995a9febd658b2570160703dff6fdc038ab2
commit-date: 2025-01-22
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
```
@rustbot label +F-deref-patterns +requires-nightly | T-lang,T-libs-api,C-bug,requires-nightly,F-deref_patterns | low | Critical |
2,810,906,438 | godot | Rotation gizmo is visible while previewing a Camera3D after restarting the editor with a camera previewed | ### Tested versions
- Reproducible in: 4.0.stable, 4.3.stable, 4.4.beta1
### System information
Godot v4.4.dev (24d74510e) - Fedora Linux 41 (KDE Plasma) on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 565.77) - 13th Gen Intel(R) Core(TM) i9-13900K (32 threads)
### Issue description
If you preview a camera, save a scene and restart the editor, when the editor restarts, you end up with the rotation gizmo being visible despite previewing a camera:
Interacting with the gizmo will have no effect. Normally, the rotation gizmo is hidden while previewing a camera.
I noticed this while making comparison screenshots for https://github.com/godotengine/godot/pull/101961#issuecomment-2613904399.
### Steps to reproduce
- Add a Node3D with a Camera3D child.
- Select Camera3D and click **Preview** in the top-left corner of the 3D editor viewport.
- Save the scene and use **Project > Reload Current Project** while still previewing the camera.
- When the editor reopens, the camera is still previewed but the rotation gizmo is now visible in the top-right corner of the 3D editor viewport.
### Minimal reproduction project (MRP)
N/A | bug,topic:editor,topic:3d | low | Minor |
2,810,912,364 | rust | 2024 edition migration of `ref` in patterns suboptimal: fixed up by clippy --fix | <!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->
The 2024 edition migration changed this:
```rust
impl TryFrom<&Selector> for konfigkoll_utils::line_edit::Selector {
type Error = eyre::Error;
fn try_from(value: &Selector) -> Result<Self, Self::Error> {
match value {
Selector::All => Ok(Self::All),
Selector::Eof => Ok(Self::Eof),
Selector::Line(n) => Ok(Self::Line(*n)),
Selector::Range(a, b) => Ok(Self::Range(*a, *b)),
Selector::Regex(r) => Ok(Self::Regex(Regex::new(r).wrap_err("invalid regex")?)),
Selector::Function(ref f) => {
let f = f.clone();
Ok(Self::Function(Rc::new(move |lineno, s| {
let guard = f.borrow_mut().expect("Failed to borrow function object");
match guard.call::<_, bool>((lineno, s)) {
VmResult::Ok(v) => v,
VmResult::Err(e) => {
tracing::error!(
"Error in custom selector function {:?}: {:?}",
*guard,
e
);
false
}
}
})))
}
}
}
}
```
into this:
```rust
impl TryFrom<&Selector> for konfigkoll_utils::line_edit::Selector {
type Error = eyre::Error;
fn try_from(value: &Selector) -> Result<Self, Self::Error> {
match value {
Selector::All => Ok(Self::All),
Selector::Eof => Ok(Self::Eof),
Selector::Line(n) => Ok(Self::Line(*n)),
Selector::Range(a, b) => Ok(Self::Range(*a, *b)),
Selector::Regex(r) => Ok(Self::Regex(Regex::new(r).wrap_err("invalid regex")?)),
&Selector::Function(ref f) => {
let f = f.clone();
Ok(Self::Function(Rc::new(move |lineno, s| {
let guard = f.borrow_mut().expect("Failed to borrow function object");
match guard.call::<_, bool>((lineno, s)) {
VmResult::Ok(v) => v,
VmResult::Err(e) => {
tracing::error!(
"Error in custom selector function {:?}: {:?}",
*guard,
e
);
false
}
}
})))
}
}
}
}
```
Then running `cargo +beta clippy --fix` changed it ~~right back~~ to `Selector::Function(f)`.
When runing without `--fix` this is the clippy message:
```
warning: dereferencing a tuple pattern where every element takes a reference
--> crates/konfigkoll_script/src/plugins/patch.rs:105:13
|
105 | &Selector::Function(ref f) => {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrowed_reference
= note: `#[warn(clippy::needless_borrowed_reference)]` on by default
help: try removing the `&` and `ref` parts
|
105 - &Selector::Function(ref f) => {
105 + Selector::Function(f) => {
|
warning: dereferencing a tuple pattern where every element takes a reference
--> crates/konfigkoll_script/src/plugins/patch.rs:208:13
|
208 | &Action::Function(ref f) => {
| ^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrowed_reference
help: try removing the `&` and `ref` parts
|
208 - &Action::Function(ref f) => {
208 + Action::Function(f) => {
|
```
I expected to see this happen: ~~A coherrent decision on what way is the proper way to write this. Rustc and clippy shouldn't fight each other.~~ The edition migration shouldn't be sloppy and need to be fixed up by clippy.
Instead, this happened: Clippy has to clean up after rustc.
I have also pushed this to a branch in my repo, in case you need more context for investigating this: https://github.com/VorpalBlade/paketkoll/tree/feature/edition-2024 (the migration and the reversion are each in a separate commit). There seemed to be a few more instances of the same needless_borrowed_reference in other files too, but I think they are the same underlying cause.
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
`rustc --version --verbose`:
```console
$ rustc +beta --version --verbose
rustc 1.85.0-beta.5 (441650704 2025-01-20)
binary: rustc
commit-hash: 44165070434aab38db1115448621880a35da00ff
commit-date: 2025-01-20
host: x86_64-unknown-linux-gnu
release: 1.85.0-beta.5
LLVM version: 19.1.7
```
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>
```
Not relevant? Didn't crash after all...
```
</p>
</details>
<!-- TRIAGEBOT_START -->
<!-- TRIAGEBOT_ASSIGN_START -->
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"dianne"}$$TRIAGEBOT_ASSIGN_DATA_END -->
<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END --> | T-compiler,C-bug,A-suggestion-diagnostics,A-clippy,A-edition-2024,I-edition-triaged | low | Critical |
2,810,922,207 | godot | Godot script crash | ### Tested versions
4.3.stable
See belows
### System information
MacOS - See below
### Issue description
See dump
[godot_crash.txt](https://github.com/user-attachments/files/18545725/godot_crash.txt)
### Steps to reproduce
Running Godot script from Godot - when FPS goes to a spesific location it always crashes badly. (MacOs - havent tried other envs)
### Minimal reproduction project (MRP)
Cannot do tha | needs work,needs testing,crash | low | Critical |
2,810,922,931 | vscode | Issues with allowed extensions Group Policy | <!-- ⚠️⚠️ 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/No
<!-- 🪓 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.4
- OS Version: Windows 11 pro 24H2
Hello VSCode Team,
I have noticed some issues with the group policy setting for allowed extensions.
- The field for entering it is too small and as such doesn't allow long strings
- It's unintuitive to edit the entries since the JSON should be a single line without any new lines and also has a length limitation
- Please consider an alternative UI for the group policy so that it's easier to add the entries.
The other issues have been documented below. Please let me know if you need further details.
Steps to Reproduce:
1. Install remote ssh extension and other extensions from microsoft or github publisher
2. Add the following entry to the group policy for allowed extensions `{ "github": true, "microsoft": true }`
3. Now the remote ssh editing icon disappears from the side bar, see image below, basically the publisher field is not working as expected
4. Add the extensions with the correct extension id to the group policy, then apply with `gpupdate` , the extensions are enabled again
5. Use a a very long list of allowed extensions like in the example below, the group policy field cuts off after a specific length and the resulting entry is invalid and as such is ignored by the group policy
```json
{
"ASF.apache-netbeans-java": true,
"asciidoctor.asciidoctor-vscode": true,
"baincd.copy-path-unixstyle": true,
"charliermarsh.ruff": true,
"eamodio.gitlens": true,
"github": true,
"microsoft": true,
"ms-azuretools.vscode-docker": true,
"ms-python.debugpy": true,
"ms-python.python": true,
"ms-python.vscode-pylance": true,
"ms-toolsai.datawrangler": true,
"ms-toolsai.jupyter": true,
"ms-toolsai.jupyter-keymap": true,
"ms-toolsai.jupyter-renderers": true,
"ms-toolsai.vscode-jupyter-cell-tags": true,
"ms-toolsai.vscode-jupyter-slideshow": true,
"ms-vscode-remote.remote-ssh": true,
"ms-vscode-remote.remote-ssh-edit": true,
"ms-vscode.hexeditor": true,
"ms-vscode.live-server": true,
"ms-vscode.powershell": true,
"ms-vscode.remote-explorer": true,
"redhat": "stable",
"redhat.ansible": true,
"redhat.java": true,
"redhat.vscode-yaml": true,
"visualstudioexptteam.intellicode-api-usage-examples": true,
"visualstudioexptteam.vscodeintellicode": true,
"vscjava.vscode-gradle": true,
"vscjava.vscode-java-debug": true,
"vscjava.vscode-java-dependency": true,
"vscjava.vscode-java-pack": true,
"vscjava.vscode-java-test": true,
"vscjava.vscode-maven": true
}
```
| info-needed | low | Critical |
2,810,923,700 | langchain | TavilySearchResults is not getting images even with include_images=True? | ### Checked other resources
- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).
### Example Code
Not able to get the images for the webpages return by tavily results.
Like [end of cold war](https://coldwar.unc.edu/theme/end-of-the-cold-war/) this page has images but i did not recieve it.
This is inspite keeping include_images=True in parameters.
Environment : Google colab
### Following is the minimal reproducible code
```python
%pip install -qU "langchain-community>=0.2.11" tavily-python
import getpass
import os
if not os.environ.get("TAVILY_API_KEY"):
os.environ["TAVILY_API_KEY"] = getpass.getpass("Tavily API key:\n")
from langchain_community.tools import TavilySearchResults
tool = TavilySearchResults(
max_results=5,
search_depth="advanced",
include_answer=True,
include_raw_content=True,
include_images=True,
)
tool_results = tool.invoke({"query": "What happened at end of cold war?"})
tool_results
```
### Error Message and Stack Trace (if applicable)
_No response_
### Description
- I am trying to use langchain integration with tavily seach using from langchain_community.tools import TavilySearchResults
- Expected to return the images present in the webpage along with text.
- Instead I just get some text present in the webpage and no images are found.
### System Info
### The output
```
[{'url': 'https://en.wikipedia.org/wiki/Cold_War_(1985–1991)',
'content': "The time period of around 1985–1991 marked the final period of the Cold War. It was characterized by systemic reform within the Soviet Union, the easing of geopolitical tensions between the Soviet-led bloc and the United States-led bloc, the collapse of the Soviet Union's influence in Eastern Europe, and the dissolution of the Soviet Union in 1991. While the exact end date of the Cold War is debated among historians, it is generally agreed upon that the implementation of nuclear and conventional arms control agreements, the withdrawal of Soviet military forces from Afghanistan and Eastern Europe, and the collapse of the Soviet Union marked the end of the Cold War."},
{'url': 'https://alphahistory.com/coldwar/end-of-the-cold-war/',
'content': 'Reunification after 45 years of division was a cause for celebration in Germany. Three events heralded the end of the Cold War: the fall of the Berlin Wall, the reunification of Germany and the dissolution of the Soviet Union.All came in the last years of the tumultuous 1980s when ordinary but defiant people challenged the viability of socialism and socialist governments.'},
{'url': 'https://coldwar.unc.edu/theme/end-of-the-cold-war/',
'content': 'End of the Cold War | A Visual Guide to the Cold War Toggle navigation A Visual Guide to the Cold War Origins of the Cold War Renewed Cold War End of the Cold War Home / Theme / End of the Cold War End of the Cold War The late Cold War is characterized by a thaw in relations between the US and Soviet Union in the late 1980s, and mostly associated with the figure of Mikhail Gorbachev and his perestroika reforms in the Soviet Union. At the Malta summit in December 1989, Gorbachev and US President George H.W. Bush declared the end of the Cold War. The next year, the Soviet Union consented to the reunification of Germany. AFTER THE COLD WAR'},
{'url': 'https://americanhistory.si.edu/subs/history/timeline/end/',
'content': 'During 1989 and 1990, the Berlin Wall came down, borders opened, and free elections ousted Communist regimes everywhere in eastern Europe. In late 1991 the Soviet Union itself dissolved into its component republics. With stunning speed, the Iron Curtain was lifted and the Cold War came to an end.'},
{'url': 'https://www.historyonthenet.com/the-cold-war-timeline-2',
'content': 'This post is a comprehensive timeline of the Cold War, from the origins of the Russian-American conflict following World War Two to the final dissolution of the Soviet Union and the fall of the Berlin Wall at the end of the 20th century. Scroll down to learn more. Alternatively, watch this nine-minute explainer video for an overview of the Cold'}]
``` | 🤖:bug | low | Critical |
2,810,928,626 | godot | Godot random crashes in Windows when starting project manager or running project | ### Tested versions
Verified in 4.3, 4.4 dev and 4.4 beta. Once loaded, the editor works, but running a project also crashes several times. Exported projects also crash with same error.
### System information
Windows 10-AMD RX 6600, and Windows 11, Nvidia RTX 4060
### Issue description
Since 4.3 I have experienced weird crashes in different Windows PCs. The engine crashes on start (the project manager doesnt loads) several times in a row with this error:
```
Godot Engine v4.4.beta1.official.d33da79d3 - https://godotengine.org
================================================================
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.4.beta1.official (d33da79d3f8fe84be2521d25b9ba8e440cf25a88)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
```
Here is the memory dump:
https://drive.google.com/file/d/1ty2ys5YB5FEOBOhbLqqdx7e5MWmBfZ7M/view?usp=sharing
### Steps to reproduce
Run the engine/create a project/run a project. Any of those actions can trigger the crash.
### Minimal reproduction project (MRP)
Not specifically project related | bug,needs testing,crash | low | Critical |
2,810,930,712 | godot | Engine crash when disabling `own_world_3d` with nested viewports | ### Tested versions
v4.3.stable.mono.custom_build [77dcf97d8]
v4.2.2.stable.mono.official [15073afe3]
### System information
Windows 10
### Issue description
The engine (game and editor) crashes if you turn off `own_world_3d` for `SubViewport` with child `SubViewport`s.
### Steps to reproduce
* Create a scene with nested `SubViewport`s
* Activate `own_world_3d` for the first viewport
* The following child viewports do not update the World3D automatically, so:
* - Save and reload the project/scene
* - Or turn on and off `own_world_3d` for nested viewports.
* Disable `own_world_3d` for the first viewport
https://github.com/user-attachments/assets/4d9229ff-0362-4fc9-9d18-c57a03d8a32a
### Minimal reproduction project (MRP)
[test.zip](https://github.com/user-attachments/files/18545670/test.zip) | bug,needs testing,crash,topic:3d | low | Critical |
2,810,930,718 | ollama | llama.cpp server API compatibility | This seems like an obvious thing but I could not find an existing issue for that. It would be nice if Ollama API had a compatibility layer with [llama.cpp server API](https://github.com/ggerganov/llama.cpp/blob/master/examples/server/README.md#api-endpoints).
I wanted to try out the new [llama.vscode](https://github.com/ggml-org/llama.vscode) extension and could figure out how to make it work with ollama-served models. I would like to avoid having a zoo of model servers and would prefer to just rely on ollama. | feature request | low | Minor |
2,810,941,430 | TypeScript | Property 'X' has no initializer and is not definitely assigned in the constructor | ### 🔎 Search Terms
Property 'X' has no initializer and is not definitely assigned in the constructor
### 🕗 Version & Regression Information
- This changed between versions ______ and _______
- This changed in commit or PR _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because _______
### ⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.8.0-dev.20250125#code/IYIwzgLgTsDGEAJYBthjAgkgEwOIFMA7fGCAeygH0BGBAbwCgFmEAHKASwDdgJ8FIvDrASpIOAFwJCAVwC2IEggC8CAAwBuJi3bde-DtimyFJDQgD0FhAFEoUCg23NYZQpCgz4FABQBKemcWZggACw4wADowfAgCYlJ8bBx-LWCAXydg3R4+AVj4kn1k7H9A4OCcQtIKGkixCBwAaia0ipDwqMMVLDwiIvIqanq0Ruw25kyg1hkQZGEEAHNYlL9jeUUocvaEKFiZKEIEMIjIwwmETKnQDzhEFDQMKv6aqgAmbeYc-QEIIREGpJpBslKpNNNOLkDEZgaYoOYrAgAHJkWz2RxBVzuaBeQZlRg7XrVXi1N4jcTYFoXYInLrYHrPBIk97ksYXKbZWbzETLMb+dZwz4VPYQA5HWlncZBK5AA
### 💻 Code
I encountered an inconsistency in the TypeScript compiler when using static properties in abstract classes
The following code produces an error in `IdGenerator_1` but not in `IdGenerator_2`
```ts
abstract class IdGenerator_1 {
private static lastId: number = 0;
private id: number; // Error
constructor() {
this.setGeneratedId();
}
private setGeneratedId() {
IdGenerator_1.lastId++;
this.id = IdGenerator_1.lastId;
}
public getId(): number {
return this.id;
}
}
abstract class IdGenerator_2 {
private static lastId: number = 0;
private id: number; // No Error
constructor() {
IdGenerator_2.lastId++;
this.id = IdGenerator_2.lastId;
}
public getId(): number {
return this.id;
}
}
```
### 🙁 Actual behavior
The compiler produces an error for `IdGenerator_1` but not for `IdGenerator_2`
### 🙂 Expected behavior
Both `IdGenerator_1` and `IdGenerator_2` should compile without errors, as they are functionally identical
### Additional information about the issue
_No response_ | Duplicate | low | Critical |
2,810,949,660 | flutter | FadeInImage with BlendMode.color abruptly shows the specified color as a background | ### Steps to reproduce
1. Add `transparent_image: ^2.0.1` dependency on a new Flutter project
2. Paste the code sample below to `main.dart`
3. Run the app on any platform
### Expected results
Specified color to only affect the image as a filter and not mess with the background before the image fades in.
### Actual results
Specified color suddenly appears as a background color when the image loads, then the image fades in.
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
import 'package:transparent_image/transparent_image.dart';
void main() => runApp(const App());
class App extends StatelessWidget {
const App({super.key});
@override
Widget build(BuildContext context) {
return const MaterialApp(
home: DemoPage(),
);
}
}
class DemoPage extends StatelessWidget {
const DemoPage({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: const Text('Example'),
),
body: Center(
child: FadeInImage.memoryNetwork(
color: Colors.blue,
colorBlendMode: BlendMode.color,
fadeInDuration: const Duration(seconds: 2),
placeholder: kTransparentImage,
image: 'https://picsum.photos/600',
),
),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
https://github.com/user-attachments/assets/e2b747ce-851c-4290-9e20-068ab6aa7438
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.27.3, on macOS 15.2 24C101 darwin-arm64, locale en-TR)
• Flutter version 3.27.3 on channel stable at /Users/rasitayaz/Library/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (4 days ago), 2025-01-21 10:32:23 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/rasitayaz/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16C5032a
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2022.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
[✓] VS Code (version 1.96.3)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (5 available)
• Raşit’s iPhone (mobile) • 00008120-001A35E63E83C01E • ios • iOS 18.2.1 22C161
• iPhone 16 Pro (mobile) • A446A6A9-3396-488A-8586-D0C36D89B118 • ios • com.apple.CoreSimulator.SimRuntime.iOS-18-2
(simulator)
• macOS (desktop) • macos • darwin-arm64 • macOS 15.2 24C101 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 15.2 24C101 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.265
[✓] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| framework,a: images,has reproducible steps,team-framework,found in release: 3.27,found in release: 3.29 | low | Minor |
2,810,970,465 | flutter | make EditableText.onTapUpOutside default logic configurable | ### Use case
Just like with `EditableText.onTapOutside`, there should be a way to set the default logic of `EditableText.onTapUpOutside` .
### Proposal
A few months ago, a pull request (https://github.com/flutter/flutter/pull/150125) was merged that added a `EditableTextTapOutsideIntent` to allow setting a default action for `EditableText.onTapOutside`.
A few days later, another pull request (https://github.com/flutter/flutter/pull/156110) adding an `onTapUpOutside` to `EditableText` was merged. I authored that pull request, but I unfortunately missed the newly created `Intent`, and didn't create a matching `Intent` for the new `onTapUpOutside` parameter.
A `EditableTextTapUpOutsideIntent` should be created to fix this. | a: text input,c: new feature,framework,c: proposal,team-text-input | low | Minor |
2,810,970,844 | TypeScript | Add AnyFunction as a new helper Type | ### ⚙ Compilation target
ESNext
### ⚙ Library
ESNext
### Missing / Incorrect Definition
I would suggest to add a new type for "any type of functions" called AnyFunction.
When we check for the code `(...args: any) => any` or `(...args: any[]) => any` in github, we finde over 90k files which have this code.
So it would be helpful to have a type for this instead in typescript.
Also this type can be used in utility-types like `Parameters` and `ReturnType`.
As there is already a `VoidFunction` in the DOM-lib this would be a great addition.
This also makes code much better readable. For example this:
```typescript
// From
const wrappedAnyFn: () => (...args: any) => any = () => () => console.log('hello');
// To:
const wrappedAnyFn: () => AnyFunction = () => () => console.log('hello');
```
This makes it much clearer what the type of our variable is.
### Sample Code
```TypeScript
// From
const wrappedAnyFn: () => (...args: any) => any = () => () => console.log('hello');
// To:
const wrappedAnyFn: () => AnyFunction = () => () => console.log('hello');
```
### Documentation Link
_No response_ | Suggestion,Declined | low | Minor |
2,810,973,543 | excalidraw | Eraser is slow. | https://github.com/user-attachments/assets/2df60fcc-c6e7-4ea5-9df8-ca4305891142 | bug,performance ⚡️,Eraser tool | low | Major |
2,810,973,613 | vscode | Extreme cpu and memory usage. | <!-- ⚠️⚠️ 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.4
- OS Version: WIN 11 23H2 (22631.4751)
```
Version: 1.96.4 (user setup)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
```
Last weeks (cannot say exact) i have problem with VS Code. After i open project, cpu usage spikes almost to the maximum and memory usage being slowly rising. After some time vscode took 3 gb ram on my machine and i guess this wasnt a limit...
Also after a few minutes disk space starts slowly to be consumed too, but I'm not sure if this is related to this problem or if this realted to the SWAP file somehow.
Of the points I noticed: the extension icon shows loading forever.
Tried to clean settings.json and launch without extensions, but looks like nothing helps.
the issue isnt present in insiders build.
Steps to Reproduce:
1. Open any project as usual, can be empty folder too.
2. Done
 | info-needed,shared-process | low | Critical |
2,810,975,017 | godot | Error when calling exisiting function using JavaClassWrapper | ### Tested versions
- Tested in 4.4-beta1 and dev7
### System information
Godot v4.4.beta1 - Windows 11 (build 22631) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Laptop GPU (NVIDIA; 32.0.15.6636) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 threads)
### Issue description
Issue:
When using the new JavaClassWrapper and calling some functions from the JavaClass it sometimes crashes the Application and returns "Attempt to call function 'xyz' in base 'JavaClass' on a null instance."
This is weird, as in my example I even return all the Java Methods and therefore the JavaClass can't be a null instance
How do I expect it to work:
Proper Error Handling and / or not crashing the whole app :D
### Steps to reproduce
For the MRP:
- Open the Project in the latest Version (4.4-beta1)
- Install Export Templates
- Remote Deploy to Android Device
### Minimal reproduction project (MRP)
[orientation_and_gps.zip](https://github.com/user-attachments/files/18546234/orientation_and_gps.zip) | bug,platform:android,topic:export | low | Critical |
2,810,978,339 | flutter | [Engine/Android] Inconsistent system navigation bar between SystemUiMode.manual and others due to inconsistent usage of SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION | ### Steps to reproduce
Switching between different SystemUiMode, for example
```dart
// Step 1: show all the bars
SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge)
// Step 2: show only navigation bar
SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual,
overlays: [SystemUiOverlay.bottom]);
// Step 3: bring back all the bars
SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge)
```
The problem is caused by this line in engine code:
https://github.com/flutter/flutter/blob/586a59211df425b8a1f9b6be1b02662bf88ddc0b/engine/src/flutter/shell/platform/android/io/flutter/plugin/platform/PlatformPlugin.java#L377
I think it should not remove `SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION` flag when showing navigaiton bar as all the other modes have this flag. If we remove it, it will resize the whole app! Check the code for non-manual modes:
https://github.com/flutter/flutter/blob/586a59211df425b8a1f9b6be1b02662bf88ddc0b/engine/src/flutter/shell/platform/android/io/flutter/plugin/platform/PlatformPlugin.java#L266
### Expected results
Should not change the layout in the whole process.
### Actual results
The layout is changed. When going from step1 to step2, the app height is getting smaller, and from step2 to step3, the app height is getting bigger again, and a flashing black area under navigation bar is spotted.
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
class SystemBarPage extends StatelessWidget {
const SystemBarPage({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
ElevatedButton(
onPressed: () {
SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge);
},
child: const Text('Edge to Edge'),
),
ElevatedButton(
onPressed: () {
SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual,
overlays: [SystemUiOverlay.top, SystemUiOverlay.bottom]);
},
child: const Text('Top and Bottom'),
),
ElevatedButton(
onPressed: () {
SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual,
overlays: [SystemUiOverlay.bottom]);
},
child: const Text('Only Bottom'),
),
],
),
),
);
}
}
```
</details>
### Screenshots or Video
_No response_
### Logs
_No response_
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[√] Flutter (Channel stable, 3.27.1, on Microsoft Windows [版本 10.0.22631.4602], locale zh-CN)
• Flutter version 3.27.1 on channel stable at G:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 17025dd882 (6 weeks ago), 2024-12-17 03:23:09 +0900
• Engine revision cb4b5fff73
• Dart version 3.6.0
• DevTools version 2.40.2
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
• Android SDK at E:\Android\SDK
• Platform android-35, build-tools 35.0.0
• ANDROID_HOME = E:\Android\SDK
• Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
• Java version OpenJDK Runtime Environment (build 17.0.10+0--11609105)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.10.3)
• Visual Studio at D:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.10.35013.160
• Windows 10 SDK version 10.0.22621.0
[√] Android Studio (version 2024.1)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.10+0--11609105)
[√] IntelliJ IDEA Ultimate Edition (version 2023.1)
• IntelliJ at D:\Program Files\JetBrains\IntelliJ IDEA 2023.1.2
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
[√] VS Code (version 1.96.4)
• VS Code at C:\Users\lai\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.102.0
[√] Connected device (4 available)
• Redmi Note 8 (mobile) • 43ab0033 • android-arm64 • Android 11 (API 30)
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [版本 10.0.22631.4602]
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.267
• Edge (web) • edge • web-javascript • Microsoft Edge 128.0.2739.42
[√] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| in triage | low | Major |
2,810,987,233 | ollama | FHS Violation | ### What is the issue?
The Linux FHS has this to say about /usr/
```
/usr is shareable, read-only data. That means that /usr should
be shareable between various FHS-compliant hosts and must not be written to.
Any information that is host-specific or varies with time is stored elsewhere.
```
However, Lama puts the service 'home' directory under /usr, and stores model file there, but /usr could be mounted read-only during normal operations. The FHS would require /var/ for the mode files, etc., that normally go in the service home directory.
### OS
Linux
### GPU
_No response_
### CPU
_No response_
### Ollama version
0.5.7 | bug | low | Minor |
2,810,988,850 | angular | Cannot read properties of undefined (reading 'index') Zone.js | ### Which @angular/* package(s) are the source of the bug?
zone.js
### Is this a regression?
Yes
### Description
### Please provide a link to a minimal reproduction of the bug
https://github.com/mohamedchibani/TasksServiceToken-for-dependency-injection
### Please provide the exception or error you saw
```true
```
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular 18.0.0
"@angular-devkit/build-angular": "^18.0.0",
"@angular/cli": "^18.0.0",
"@angular/compiler-cli": "^18.0.0"
```
### Anything else?
_No response_ | needs reproduction,area: zones | low | Critical |
2,811,010,920 | transformers | Request to add Doge | ### Model description
Doge is an architecture that combines the advantages of state-space and self-attention. It solves the problem of self-attention getting lost in long sequences by computing **dynamic mask** from cached value states using zeroth-order holding. It can also use `wsd_scheduler` on top of dense weight checkpoints to **additionally train** a sparsely activated feedforward network expansion layer.
paper: https://arxiv.org/abs/2412.11834
### Open source status
- [x] The model implementation is available
- [x] The model weights are available
### Provide useful links for the implementation
Repository: https://github.com/LoserCheems/WonderfulMatrices
Weights: https://huggingface.co/collections/JingzeShi/doge-slm-677fd879f8c4fd0f43e05458 | New model | low | Minor |
2,811,012,332 | flutter | FloatingActionButton is out of frame when trying to place it in CupertinoSheetRoute | ### Steps to reproduce
I wanted to try out [PR](https://github.com/flutter/flutter/pull/157568#issuecomment-2590955571)'s recently implemented CupertinoSheetRoute, so I ran [sheet.dart](https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/cupertino/sheet.dart) and examples' [cupertino_sheet.0.dart](https://github.com/MitchellGoodwin/flutter/blob/1546d7c8d3c86cbb41a482a131dbef552130b106/examples/api/lib/cupertino/sheet/cupertino_sheet.0.dart).
This works fine.
Next, I wanted to add a FloatingActionButton to this code.
CupertinoPageScaffold does not have a floatingActionButton property, so I changed it to Scaffold and placed a floatingActionButton.
However, this code places the floatingActionButton partially outside the frame.
### Expected results
FloatingActionButton should be displayed in the frame in the Sheet.
### Actual results
FloatingActionButton is displayed out of frame in Sheet
### Code sample
<details open><summary>Code sample</summary>
```dart
// Copyright 2014 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';
import 'package:flutter_engineer_codecheck/sheet.dart';
/// Flutter code sample for [CupertinoSheetRoute].
void main() {
runApp(const CupertinoSheetApp());
}
class CupertinoSheetApp extends StatelessWidget {
const CupertinoSheetApp({super.key});
@override
Widget build(BuildContext context) {
return const CupertinoApp(title: 'Cupertino Sheet', home: HomePage());
}
}
class HomePage extends StatelessWidget {
const HomePage({super.key});
@override
Widget build(BuildContext context) {
return CupertinoPageScaffold(
navigationBar: const CupertinoNavigationBar(
middle: Text('Sheet Example'),
automaticBackgroundVisibility: false,
),
child: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
CupertinoButton.filled(
onPressed: () {
Navigator.of(context).push(
CupertinoSheetRoute<void>(
builder: (BuildContext context) => const _SheetScaffold(),
),
);
},
child: const Text('Open Bottom Sheet'),
),
],
),
),
);
}
}
class _SheetScaffold extends StatelessWidget {
const _SheetScaffold();
@override
Widget build(BuildContext context) {
return Scaffold(
floatingActionButton: FloatingActionButton(
onPressed: () {},
child: Icon(Icons.add),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
const Text('CupertinoSheetRoute'),
CupertinoButton.filled(
onPressed: () {
Navigator.of(context).maybePop();
},
child: const Text('Go Back'),
),
const Text('You can also close this sheet by dragging downwards'),
CupertinoButton.filled(
onPressed: () {
Navigator.of(context).push(
CupertinoSheetRoute<void>(
builder: (BuildContext context) => const _SheetScaffold(),
),
);
},
child: const Text('Push Another Sheet'),
),
],
),
),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
| iOS | Android |
|----------|----------|
| <img src="https://github.com/user-attachments/assets/4b99e743-3c9c-42fa-acff-969e404a03f3" width="70%" /> | <img src="https://github.com/user-attachments/assets/61cb69d0-68fc-4a71-945f-699f26a4cd8b" /> |
</details>
### Logs
_No response_
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
$ flutter doctor -v
[✓] Flutter (Channel stable, 3.27.1, on macOS 13.5.2 22G91 darwin-arm64, locale ja-JP)
• Flutter version 3.27.1 on channel stable at /Users/yamamotohiroto/fvm/versions/3.27.1
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 17025dd882 (6 weeks ago), 2024-12-17 03:23:09 +0900
• Engine revision cb4b5fff73
• Dart version 3.6.0
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
• Android SDK at /Users/yamamotohiroto/Library/Android/sdk
• Platform android-35, build-tools 35.0.0
• ANDROID_HOME = /Users/yamamotohiroto/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15C500b
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
[✓] VS Code (version 1.93.1)
• VS Code at /Users/yamamotohiroto/Downloads/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (5 available)
• iPhone (mobile) • 00008120-000A5D180E01A01E • ios • iOS 17.6.1 21G93
• iPhone 15 (mobile) • B02EDDD3-93FB-489F-93B1-A8BFA65FD1C3 • ios • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
• macOS (desktop) • macos • darwin-arm64 • macOS 13.5.2 22G91 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 13.5.2 22G91 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.267
[✓] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| f: material design,f: cupertino,has reproducible steps,team-design,found in release: 3.29 | low | Minor |
2,811,012,573 | kubernetes | pull-kubernetes-e2e-kind-evented-pleg is failing with error: "gauge:{value:NNNN}} was collected before with the same name and label values" #128229 | ### Which jobs are failing?
pull-kubernetes-e2e-kind-evented-pleg
### Which tests are failing?
SynchronizedBeforeSuite
detail link: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/129355/pull-kubernetes-e2e-kind-evented-pleg/1883113368735191040
### Since when has it been failing?
Today (or may have begun failing earlier, but we only started running it today).
### Testgrid link
None, We have not added Testgrid for it.
### Reason for failure (if possible)
```
{
ErrStatus:
code: 500
details:
causes:
- message: |-
An error has occurred while serving metrics:
10 error(s) occurred:
* collected metric "kubelet_container_log_filesystem_used_bytes" { label:{name:"container" value:"local-path-provisioner"} label:{name:"namespace" value:"local-path-storage"} label:{name:"pod" value:"local-path-provisioner-58cc7856b6-kkzh7"} label:{name:"uid" value:"3c66de01-612c-4e67-9b68-d17db5e6018c"} gauge:{value:12288}} was collected before with the same name and label values
* collected metric "kubelet_container_log_filesystem_used_bytes" { label:{name:"container" value:"local-path-provisioner"} label:{name:"namespace" value:"local-path-storage"} label:{name:"pod" value:"local-path-provisioner-58cc7856b6-kkzh7"} label:{name:"uid" value:"3c66de01-612c-4e67-9b68-d17db5e6018c"} gauge:{value:12288}} was collected before with the same name and label values
* collected metric "kubelet_container_log_filesystem_used_bytes" { label:{name:"container" value:"kindnet-cni"} label:{name:"namespace" value:"kube-system"} label:{name:"pod" value:"kindnet-jb2l7"} label:{name:"uid" value:"5b560c1f-3223-4fda-acf5-a44a8eb20d6b"} gauge:{value:90112}} was collected before with the same name and label values
* collected metric "kubelet_container_log_filesystem_used_bytes" { label:{name:"container" value:"kindnet-cni"} label:{name:"namespace" value:"kube-system"} label:{name:"pod" value:"kindnet-jb2l7"} label:{name:"uid" value:"5b560c1f-3223-4fda-acf5-a44a8eb20d6b"} gauge:{value:90112}} was collected before with the same name and label values
* collected metric "kubelet_container_log_filesystem_used_bytes" { label:{name:"container" value:"coredns"} label:{name:"namespace" value:"kube-system"} label:{name:"pod" value:"coredns-674b8bbfcf-tgjsw"} label:{name:"uid" value:"74e1a7b8-b716-439d-8a2c-97d1bd6e3f5c"} gauge:{value:12288}} was collected before with the same name and label values
* collected metric "kubelet_container_log_filesystem_used_bytes" { label:{name:"container" value:"coredns"} label:{name:"namespace" value:"kube-system"} label:{name:"pod" value:"coredns
reason: UnexpectedServerResponse
kind: nodes
name: kind-control-plane:10250
message: an error on the server ("An error has occurred while serving metrics:\n\n10
error(s) occurred:\n* collected metric \"kubelet_container_log_filesystem_used_bytes\"
{ label:{name:\"container\" value:\"local-path-provisioner\"} label:{name:\"namespace\"
value:\"local-path-storage\"} label:{name:\"pod\" value:\"local-path-provisioner-58cc7856b6-kkzh7\"}
label:{name:\"uid\" value:\"3c66de01-612c-4e67-9b68-d17db5e6018c\"} gauge:{value:12288}}
was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\"
{ label:{name:\"container\" value:\"local-path-provisioner\"} label:{name:\"namespace\"
value:\"local-path-storage\"} label:{name:\"pod\" value:\"local-path-provisioner-58cc7856b6-kkzh7\"}
label:{name:\"uid\" value:\"3c66de01-612c-4e67-9b68-d17db5e6018c\"} gauge:{value:12288}}
was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\"
{ label:{name:\"container\" value:\"kindnet-cni\"} label:{name:\"namespace\" value:\"kube-system\"}
label:{name:\"pod\" value:\"kindnet-jb2l7\"} label:{name:\"uid\" value:\"5b560c1f-3223-4fda-acf5-a44a8eb20d6b\"}
gauge:{value:[901](https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/128239/pull-kubernetes-e2e-kind-evented-pleg/1883150391969845248#1:build-log.txt%3A901)12}} was collected before with the same name and label values\n*
collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\"
value:\"kindnet-cni\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\"
value:\"kindnet-jb2l7\"} label:{name:\"uid\" value:\"5b560c1f-3223-4fda-acf5-a44a8eb20d6b\"}
gauge:{value:90112}} was collected before with the same name and label values\n*
collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\"
value:\"coredns\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\"
value:\"coredns-674b8bbfcf-tgjsw\"} label:{name:\"uid\" value:\"74e1a7b8-b716-439d-8a2c-97d1bd6e3f5c\"}
gauge:{value:12288}} was collected before with the same name and label values\n*
collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\"
value:\"coredns\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\"
value:\"coredns") has prevented the request from succeeding (get nodes kind-control-plane:10250)
metadata: {}
reason: InternalError
status: Failure,
}
[FAILED] in [SynchronizedBeforeSuite] - k8s.io/kubernetes/test/e2e/framework/debug/dump.go:139 @ 01/25/25 14:11:46.528
<< Timeline
[FAILED] an error on the server ("An error has occurred while serving metrics:\n\n10 error(s) occurred:\n* collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\" value:\"local-path-provisioner\"} label:{name:\"namespace\" value:\"local-path-storage\"} label:{name:\"pod\" value:\"local-path-provisioner-58cc7856b6-kkzh7\"} label:{name:\"uid\" value:\"3c66de01-612c-4e67-9b68-d17db5e6018c\"} gauge:{value:12288}} was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\" value:\"local-path-provisioner\"} label:{name:\"namespace\" value:\"local-path-storage\"} label:{name:\"pod\" value:\"local-path-provisioner-58cc7856b6-kkzh7\"} label:{name:\"uid\" value:\"3c66de01-612c-4e67-9b68-d17db5e6018c\"} gauge:{value:12288}} was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\" value:\"kindnet-cni\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\" value:\"kindnet-jb2l7\"} label:{name:\"uid\" value:\"5b560c1f-3223-4fda-acf5-a44a8eb20d6b\"} gauge:{value:90112}} was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\" value:\"kindnet-cni\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\" value:\"kindnet-jb2l7\"} label:{name:\"uid\" value:\"5b560c1f-3223-4fda-acf5-a44a8eb20d6b\"} gauge:{value:90112}} was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\" value:\"coredns\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\" value:\"coredns-674b8bbfcf-tgjsw\"} label:{name:\"uid\" value:\"74e1a7b8-b716-439d-8a2c-97d1bd6e3f5c\"} gauge:{value:12288}} was collected before with the same name and label values\n* collected metric \"kubelet_container_log_filesystem_used_bytes\" { label:{name:\"container\" value:\"coredns\"} label:{name:\"namespace\" value:\"kube-system\"} label:{name:\"pod\" value:\"coredns") has prevented the request from succeeding (get nodes kind-control-plane:10250)
In [SynchronizedBeforeSuite] at: k8s.io/kubernetes/test/e2e/framework/debug/dump.go:139 @ 01/25/25 14:11:46.528
```
### Anything else we need to know?
The test failure is unrelated to the PR modifying evented PLEG. Even when running this test job in any PR (where changes do not involve PLEG), it fails consistently.
### Relevant SIG(s)
/sig node | sig/node,kind/failing-test,lifecycle/active,triage/accepted | low | Critical |
2,811,013,859 | neovim | `nvim_win_call()` can affect global current directory in presence of window-local current directory | ### Problem
Executing `nvim_win_call()` does not play well with window-local current directory. Even more so if inside its callback new window splits are created.
### Steps to reproduce
1. Create the following 'init.lua':
```lua
-- Create separate window with the current (global) current directory
vim.cmd('belowright vsplit')
local win_id = vim.api.nvim_get_current_win()
vim.cmd('wincmd h')
-- Make current (left, non-target) window have window-local current directory
vim.cmd('lcd ' .. vim.fn.fnamemodify('local', ':p'))
-- Define functions to perform `nvim_win_call` and split
_G.log = {}
local log_pwd = function() table.insert(_G.log, vim.api.nvim_exec2('verbose pwd', { output = true }).output) end
_G.do_win_call = function()
log_pwd()
vim.api.nvim_win_call(win_id, function()
log_pwd()
vim.cmd('belowright split')
log_pwd()
end)
log_pwd()
end
```
2. For more clarity, create a directory named 'global' and its subdirectory 'local'.
3. Start `nvim --clean -u path/to/init.lua` from inside 'global' directory.
4. There are two vertically split windows. The left is current and executing `:verbose pwd` inside it shows expected `[window] .../global/local`. Navigating to the right window and doing the same shows expected `[global] .../global`.
5. With left window being current, execute `:lua do_win_call()`. It should create a horizontal split below right window. Inspect the log with `:log`. It shows the following entries:
- `[window] .../global/local` - as expected in the context of left window.
- `[global] .../global/local` - **not expected**, as it should be `[global] .../global` as it is in the context of the right window.
- `[global] .../global` - as expected, as it should copy current directory data from the right window.
- `[window] .../global/local` - as expected.
On top of the single unexpected change of global current directory, the values of current directory now have changed for both right windows. Executing `:verbose pwd` in **both of them** shows `[global] .../global/local` which was never assigned as global current directory. The `[global] .../global` output is expected in both windows.
Notes:
- Same behavior can be observed with `vim.fn.win_execute(win_id, 'belowright split')` instead of `nvim_win_call()`.
- Possibly related: #16314, #28213 (cc @zeertzjq).
### Expected behavior
Calling `nvim_win_call()` respects window-local current directory.
Performing split inside `nvim_win_call()` correctly preserves current directory and never alters global current directory.
### Nvim version (nvim -v)
NVIM v0.11.0-dev-1633+g851137f679
### Vim (not Nvim) behaves the same?
Kind of, if replicated with `win_execute()`
### Operating system/version
EndeavourOS Linux x86_64, 6.12.10-arch1-1
### Terminal name/version
Ghostty 1.0.1-arch
### $TERM environment variable
xterm-ghostty
### Installation
appimage | bug-vim | low | Minor |
2,811,032,709 | material-ui | React 19 for mui-joy | ### Summary
Hi I know you have paused the development of mui-joy.
But could you give the possibility to use it with react 19?
### Examples
_No response_
### Motivation
_No response_
**Search keywords**: react 19 mui-joy | support: question,status: waiting for author | low | Minor |
2,811,038,872 | godot | After hiding a node on GPUParticles2D finished signal and then showing again, without restarting, the particles always show again for a frame at the last position. | ### Tested versions
4.3 + mono, 4.4 beta 1 (Forward+)
### System information
Win 11 - intel i5 - 13600KF - Nvidia RTX 4070
### Issue description
Video from the MRP: https://youtu.be/CINibauy7sU
Video from my project: https://youtu.be/TkcZ82gIO0E
I'll describe what to watch for in the video, please watch it after reading this.
Watch the blue arrows moving to the red tile, at the end they create a black circle. The black circle is a particle system with 1 particle emitted (through emitting = true, I also tried restart()). The particle system has a scale curve set to go from 0 -> 1.
Right now everything is correct and as expected.
I connect to the Finished signal of the particles and hide the projectile, structure is like this:
Then I redo the whole action and send new projectiles at the enemy, these are the same projectiles as the first one I just change their position and use show() to display them so I'm not creating another set of projectiles. And here's the issue, observe that when they spawn the black circle for a moment appears at the last know position.
I don't understand why.
If I await 0.1 second (timer) in the finish before hiding the projectile then this issue doesn't happen. This makes me wonder, are particles really finished on Finish? Why are the particles showing only for one frame and at a wrong position?
I tried removing the particles from the tree which naturally stops the issue. But if I remove them from the tree and immediatelly add them back the issue is the same.
I tried hiding them, repositioning the projectile and unhiding them but the same problem occurs.
The only definite way is to not hide the projectile on finish which is naturally a problem in itself or give it some extra time for the engine to finish handling the particles in some way.
### Steps to reproduce
Run the MRP, wait until couple arrows explode then wait couple seconds until they respawn and you should see at the moment of the respawn the black explosions at the last position they reached on the first run.
You can replace the gradient texture with the godot icon, it's not important I just tested it a moment ago.
### Minimal reproduction project (MRP)
[TestParticles2d - gd + csharp.zip](https://github.com/user-attachments/files/18547711/TestParticles2d.-.gd.%2B.csharp.zip)
**EDIT: Added MRP both gdscript and csharp and a video from the MRP.**
EDIT2: You can call `Hide()` on the particle node in the finished callback and `Show()` just before setting `Emitting = true;` this way the issue doesn't happen, it seems to only happen for a frame or so just after the projectile is displayed again and moved (though the issue is there on the frame you set the position so you need to show it sometime later as suggested above for example just before the particles need to emit.
Another option is as describbed earlier, don't kill the tween or set a timer inside Finished signal and hide the projectile after 0.1f or so of a delay that gives particles time to do what it needs to I guess - unless this is my code error obviously ;)?) | bug,needs testing,topic:2d,topic:particles | low | Critical |
2,811,044,829 | rust | Reborrowing (`&mut *x`) is not suggested as a potential solution for `&mut T` being moved | ### Code
```Rust
fn do_something<T>(_a: &mut T, _b: &mut T) {}
fn foo<T: Default>(r: &mut T) {
let mut a = T::default();
let b = r;
do_something(&mut a, b);
*r = a;
}
```
### Current output
```Shell
error[E0382]: use of moved value: `r`
--> src/lib.rs:7:5
|
3 | fn foo<T: Default>(r: &mut T) {
| - move occurs because `r` has type `&mut T`, which does not implement the `Copy` trait
4 | let mut a = T::default();
5 | let b = r;
| - value moved here
6 | do_something(&mut a, b);
7 | *r = a;
| ^^ value used here after move
For more information about this error, try `rustc --explain E0382`.
error: could not compile `moved` (lib) due to 1 previous error
```
### Desired output
```Shell
help: try reborrowing: `let b = &mut *r;`
++++++
```
### Rationale and extra context
A rather trivial fix, but not very easy to recall it even exists, because in most places compiler does this for you automatically (iinm). For example, I think Rust always inserts `&mut *` when a `&mut T` is passed as an argument to a call.
### Other cases
Similar to #81059 & #82453, but those also involve pattern matching.
Similar to #129694, but example there is more complex, with some type inference involved.
Similar to #81772, but that issue seems to be about expecting the compiler to automatically insert `&mut *` and not about the diagnostic quality. The diagnostics there actually does suggest to add a reborrow (as of nightly 2025-01-24).
Same thing with #85161: it is not about diagnostics but about compiler not reborrowing automatically. The diagnostic there does suggest reborrowing too.
More or less a duplicate of #74706? Feel free to close either one if you think these are indeed duplicates.
### Rust Version
```Shell
$ rustc --version --verbose
rustc 1.86.0-nightly (1e9b0177d 2025-01-24)
binary: rustc
commit-hash: 1e9b0177da38e3f421a3b9b1942f1777d166e06a
commit-date: 2025-01-24
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
```
### Anything else?
If not for [the Boats's post on pinned places](https://without.boats/blog/pinned-places/), I don't think I would even realize I can do `&mut *` to fix the error I got, despite several years of actively using Rust under my belt. | A-diagnostics,T-compiler | low | Critical |
2,811,048,848 | vscode | "c" key is not typing in vs code |
Type: <b>Bug</b>
Hello Team VS Code,
In my VS Code , when I try to type "c" it didn't type but when is type "C" with shift key i typed . Only letter "c" is not typing.
Please this problem as-soon-as possible .
Thanks.
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i3-3240 CPU @ 3.40GHz (4 x 3392)|
|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)|7.97GB (3.35GB free)|
|Process Argv|--crash-reporter-id 1bbbfc40-021b-4ec7-a154-787e0d10147f|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (3)</summary>
Extension|Author (truncated)|Version
---|---|---
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
9064b325:31222308
copilot_t_ci:31222730
```
</details>
<!-- generated by issue reporter --> | info-needed,triage-needed | low | Critical |
2,811,053,112 | ollama | ollama version is 0.5.7-0-ga420a45-dirty | ### What is the issue?
Can we talk about how to fix this?
### OS
Linux
### GPU
Nvidia
### CPU
Intel
### Ollama version
0.5.7 | bug | low | Minor |
2,811,060,097 | ui | [bug]: Unused Variable Error for actionTypes in TypeScript with ESLint in use-toast.ts | ### Describe the bug
When using the use-toast.ts file from the shadcn template in a Next.js project, running npm run lint results in the following ESLint error:
<img width="1167" alt="Image" src="https://github.com/user-attachments/assets/2f7caac0-74a7-49e6-8cd8-8927a1e49f0c" />
### Affected component/components
Toast
### How to reproduce
Run the following commands to reproduce the issue
```bash
npx create-next-app@latest test-nextjs
pnpm dlx shadcn@latest init -d
pnpm dlx shadcn@latest add toast
npm run lint
```
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
./src/hooks/use-toast.ts
21:7 Error: 'actionTypes' is assigned a value but only used as a type. @typescript-eslint/no-unused-vars
```
### System Info
```bash
OS: macOS
node: v22.13.0
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,811,061,376 | next.js | Deprecation warning of "punycode" module in freshly created next js app in Windows 11 | ### Link to the code that reproduces this issue
https://github.com/vickvey/next-imdb/
### To Reproduce
1. Create a fresh next app with `npm create-next-app@latest` in windows 11 from powershell terminal.
2. Run the developement server using `npm run dev`.
3. You will see the warning there about some punycode module is expired.
PS: I dont't know but I think its just dont feels right that, although I have just created a new fresh next app using "npx create-next-app@latest" and nothing else but yet I get this punycode deprecation warning, this means that the create-next-app@latest has some flaws which needs to fixed maybe there is need to update the dependecies.
### Current vs. Expected behavior
See here the `punycode` deprecation warning in freshly created next app using `npm create-next-app@latest`.
Please resolve this issue, as I have OCD of using deprecated software.
### Provide environment information
```bash
Operating system:
Windows 11
Architecture:
x64
```
### Which area(s) are affected? (Select all that apply)
create-next-app
### Which stage(s) are affected? (Select all that apply)
next dev (local)
### Additional context
Nothing, Please fix this. The biggest reason for me creating this issue is I mean i just used the latest version of next-js to create a fresh next app but still got a deprecation warning of some punycode module. Please resolve this. | create-next-app,linear: next | low | Minor |
2,811,062,722 | ollama | Deepseek R1 throwing weird generation DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD | ### What is the issue?
I tried to use the full deepseek model 4-bit quantized one with `ollama run deepseek-r1:671b`
but it somehow gives `DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD` as the output
### OS
Linux
### GPU
AMD
### CPU
_No response_
### Ollama version
0.5.7 | bug | low | Major |
2,811,079,711 | youtube-dl | How can you use a list of proxies? | The question is, how can I use a whole list of proxies, I added 10 proxies to the list and upload it, but before that my script checks which ones work, which ones don't and generates a file with working proxies, I upload it.
How does the proxy list work, each connection to the parsing site comes from a different proxy ip address? I understand correctly.
The point was that if each connection to the parsing site comes not from one of the ip addresses of the proxy, but from different ones, then it makes sense, so that, say, YouTube does not complain that you need to use cookies, etc.
**Added proxy loading from the list**
` with open("/home/shortsvideo/working_proxies.txt", "r") as f:
working_proxies = f.read().splitlines()`
**Options like this, and connecting a list of proxies**
` ydl_opts = {
'http_user_agent': self.ua.random,
'cookiefile': self.get_cookies_path(),
'format': 'mp4',
'outtmpl': f'{self.download_path}/%(id)s.mp4',
'proxy': ', '.join(working_proxies),
'force_ipv6': True,
'age_limit': 45,
}`
Am I doing everything right to use the whole list with proxies, so that each connection to the site where the video should be parsed comes from a different proxy from the list.
I get this error, for some reason it shows a list with proxies.
 | question | low | Critical |
2,811,080,443 | rust | Tracking issue for release notes of #134090: Stabilize target_feature_11 |
This issue tracks the release notes text for #134090.
### Steps
- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.
### Release notes text
The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).
````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Stabilize target_feature_11](https://github.com/rust-lang/rust/pull/134090)
````
> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*
### Release blog section
If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*
````markdown
````
cc @veluca93, @tmandry -- origin issue/PR authors and assignees for starting to draft text
| T-lang,relnotes,needs-triage,relnotes-tracking-issue | low | Minor |
2,811,083,017 | rust | type level debuginfo is duplicated across codegen units | <!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->
I tried this code:
```rust
// inner.rs
/// Byte order that is selectable at runtime.
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]
pub enum RunTimeEndian {
/// Little endian byte order.
Little,
/// Big endian byte order.
Big,
}
// main.rs
use inner::RunTimeEndian;
fn main() {
use RunTimeEndian::*;
println!("{:?}{:?}{:?}{:?}{:?}", Little, Big, Little, Big, Little);
}
```
I expected to see this happen: `RunTimeEndian` only appears once in the debuginfo.
Instead, this happened: `RunTimeEndian` appears twice:
```
; dwarfdump -a /home/jyn/.local/lib/cargo/target/debug/example | rg '\sRunTimeEndian$' -B5
< 1><0x00000329> DW_TAG_namespace
DW_AT_name inner
< 2><0x0000032e> DW_TAG_enumeration_type
DW_AT_type <0x00000322>
DW_AT_enum_class yes(1)
DW_AT_name RunTimeEndian
--
< 1><0x0000002a> DW_TAG_namespace
DW_AT_name inner
< 2><0x0000002f> DW_TAG_enumeration_type
DW_AT_type <0x00000088>
DW_AT_enum_class yes(1)
DW_AT_name RunTimeEndian
```
Note that the original (non-minimized) example was much worse; the `correctness` integration test for `addr2line` has this duplicated 59 times.
cc https://github.com/rust-lang/rust/issues/129722, https://github.com/rust-lang/rust/issues/115455. this is not the same as either of those because it only appears across codegen units (AFAICT).
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
`rustc --version --verbose`:
```
rustc 1.86.0-nightly (049355708 2025-01-18)
binary: rustc
commit-hash: 049355708383ab1b9a1046559b9d4230bdb3a5bc
commit-date: 2025-01-18
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
``` | A-debuginfo,T-compiler,C-bug,I-heavy | low | Critical |
2,811,092,270 | rust | Dropped non-Send incorrectly reported as living, resulting in non-Send Future | This:
```rust
struct NonSend(*const ());
impl NonSend {
fn noop(&self) {}
}
fn main() {
assert_send(async {
let x = NonSend(core::ptr::null());
x.noop();
drop(x);
async {}.await;
});
}
fn assert_send(_: impl Send) {}
```
[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=660c2df413763c4e2fd007962e3dfae8)
Errors with:
```
error: future cannot be sent between threads safely
--> src/main.rs:8:2
|
8 | / assert_send(async {
9 | | let x = NonSend(core::ptr::null());
10 | | x.noop();
11 | | drop(x);
12 | | async {}.await;
13 | | });
| |______^ future created by async block is not `Send`
|
= help: within `{async block@src/main.rs:8:14: 8:19}`, the trait `Send` is not implemented for `*const ()`
note: future is not `Send` as this value is used across an await
--> src/main.rs:12:12
|
9 | let x = NonSend(core::ptr::null());
| - has type `NonSend` which is not `Send`
...
12 | async {}.await;
| ^^^^^ await occurs here, with `x` maybe used later
note: required by a bound in `assert_send`
--> src/main.rs:16:24
|
16 | fn assert_send(_: impl Send) {}
| ^^^^ required by this bound in `assert_send`
error: could not compile `playground` (bin "playground") due to 1 previous error
```
It states that the non-Send `x` might be used across the await; however, this is not possible, as it has been dropped. | C-bug,needs-triage | low | Critical |
2,811,092,603 | puppeteer | [Feature]: Reducing dependencies | ### Feature description
In the `@puppeteer/browsers` package, there are some dependencies for unpacking archive files: `extract-zip` for `.zip`, `tar-fs` for `.tar`, and `unbzip2-stream` for `.bz2`.
https://github.com/puppeteer/puppeteer/blob/bbf75db85352e245bfc1ee59b5ef06b1eb3cf18b/packages/browsers/src/fileUtil.ts#L70-L71
However, when uncompressing a '.xz' file, it seems to call the OS's native command instead of relying on node_modules dependencies.
If so, wouldn't it be possible to do the same in other formats?
I have a concern about the licensing of the `unbzip2-stream` package. https://github.com/regular/unbzip2-stream/issues/41
And from the perspective of someone who only uses `puppeteer-core` to manipulate Chrome that is already installed, the dependencies on unpacking is useless, so the fewer dependencies the better.
| feature | low | Minor |
2,811,100,075 | ant-design | Menu component in dark mode makes selected parent item background the same color as its text | ### Reproduction link
[https://ant.design/~demos/menu-demo-horizontal-dark](https://ant.design/~demos/menu-demo-horizontal-dark)
### Steps to reproduce
Select a sub-item from the menu. See that the selected parent item background is the same as the text color.
### What is expected?
Text color should be contrasting in dark-mode
### What is actually happening?
Text color is the same as background, making it unreadable.
| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18.3.1 |
| System | macOS Ventura 13.2.1 |
| Browser | Chrome 131.0.6778.265 |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | 🐛 Bug | low | Minor |
2,811,102,120 | godot | MeshTexture does not render correctly on GPUparticles2D, CPUparticles2D or Polygon2D | ### Tested versions
- Reproducible in the 4.4 beta.
- Reproducible in 4.1.1 stable.
Honestly i doubt it ever worked given its relatively niche so its feasible it was never brought up ( seems to be the case from an issue search)
### System information
Godot v4.4.beta.mono (d004aed08) - Pop!_OS 22.04 LTS on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU - 12th Gen Intel(R) Core(TM) i7-12650H (16 threads) (this is the branch from this PR : https://github.com/godotengine/godot/pull/102028 but the issues are present on other versions too
### Issue description
The MeshTexture 2D doesn't display on most the aforementioned nodes. There may be good reasons for this internally but if so it shouldn't show up in the dropdowns imo, or at least throw some sort of error upon attempted assignment
### Steps to reproduce
Create a one of the aforementioned nodes, add a MeshTexture to it with it's corresponding mesh and texture. You will be greeted by a blank canvas,
I highly recommend anyone testing this issue test it on https://github.com/godotengine/godot/pull/102028 since meshtexture has a plethora of other bugs previous to that that will harm evaluation of this one potentially
### Minimal reproduction project (MRP)
[MeshParticlesPolygonTest.zip](https://github.com/user-attachments/files/18547252/MeshParticlesPolygonTest.zip) | enhancement,discussion,topic:2d | low | Critical |
2,811,103,718 | vscode | Run code button is missing |
Type: <b>Feature Request</b>
Run code button is missing from top right
VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.22621
Modes:
<!-- generated by issue reporter --> | info-needed | low | Minor |
2,811,107,513 | flutter | FormatException: Invalid UTF-8 byte (at offset 59) when checking USB connection | ### Steps to reproduce
Flutter crash report.
Please report a bug at https://github.com/flutter/flutter/issues.
## command
flutter daemon
## exception
FormatException: FormatException: Invalid UTF-8 byte (at offset 59)
```
#0 _Utf8Decoder.convertChunked (dart:convert-patch/convert_patch.dart:1950:7)
#1 _Utf8ConversionSink.addSlice (dart:convert/string_conversion.dart:304:28)
#2 _Utf8ConversionSink.add (dart:convert/string_conversion.dart:300:5)
#3 _ConverterStreamEventSink.add (dart:convert/chunked_conversion.dart:69:18)
#4 _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:111:24)
#5 _rootRunUnary (dart:async/zone.dart:1422:47)
#6 _CustomZone.runUnary (dart:async/zone.dart:1324:19)
#7 _CustomZone.runUnaryGuarded (dart:async/zone.dart:1233:7)
#8 _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:366:11)
#9 _BufferingStreamSubscription._add (dart:async/stream_impl.dart:297:7)
#10 _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:777:19)
#11 _StreamController._add (dart:async/stream_controller.dart:651:7)
#12 _StreamController.add (dart:async/stream_controller.dart:606:5)
#13 _Socket._onData (dart:io-patch/socket_patch.dart:2455:41)
#14 _rootRunUnary (dart:async/zone.dart:1430:13)
#15 _CustomZone.runUnary (dart:async/zone.dart:1324:19)
#16 _CustomZone.runUnaryGuarded (dart:async/zone.dart:1233:7)
#17 _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:366:11)
#18 _BufferingStreamSubscription._add (dart:async/stream_impl.dart:297:7)
#19 _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:777:19)
#20 _StreamController._add (dart:async/stream_controller.dart:651:7)
#21 _StreamController.add (dart:async/stream_controller.dart:606:5)
#22 new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1942:33)
#23 _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1385:14)
#24 _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#25 _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#26 _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#27 _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:185:5)
```
## flutter doctor
```
[!] Flutter (Channel stable, 3.27.2, on Debian GNU/Linux 12 (bookworm) 6.6.62+rpt-rpi-2712, locale en_GB.UTF-8)
• Flutter version 3.27.2 on channel stable at /home/<Ja>/Tvorba/flutter
! The flutter binary is not on your path. Consider adding /home/<Ja>/Tvorba/flutter/bin to your path.
! The dart binary is not on your path. Consider adding /home/<Ja>/Tvorba/flutter/bin to your path.
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 68415ad1d9 (12 days ago), 2025-01-13 10:22:03 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
• If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.1)
• Android SDK at /usr/lib/android-sdk
• Platform android-35, build-tools 35.0.1
• Java binary at: /opt/android-studio/jbr/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.13+11-Debian-2deb12u1)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at google-chrome
[✓] Linux toolchain - develop for Linux desktop
• Debian clang version 14.0.6
• cmake version 3.25.1
• ninja version 1.11.1
• pkg-config version 1.8.1
[✓] Android Studio (version 2024.2)
• Android Studio at /opt/android-studio
• Flutter plugin version 83.0.3
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.13+11-Debian-2deb12u1)
[✓] VS Code (version 1.96.4)
• VS Code at /usr/share/code
• Flutter extension version 3.102.0
[☠] Connected device (the doctor check crashed)
✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
✗ FormatException: Invalid UTF-8 byte (at offset 59)
• #0 _Utf8Decoder.convertChunked (dart:convert-patch/convert_patch.dart:1950:7)
#1 _Utf8ConversionSink.addSlice (dart:convert/string_conversion.dart:304:28)
#2 _Utf8ConversionSink.add (dart:convert/string_conversion.dart:300:5)
#3 _ConverterStreamEventSink.add (dart:convert/chunked_conversion.dart:69:18)
#4 _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:111:24)
#5 _rootRunUnary (dart:async/zone.dart:1422:47)
#6 _CustomZone.runUnary (dart:async/zone.dart:1324:19)
#7 _CustomZone.runUnaryGuarded (dart:async/zone.dart:1233:7)
#8 _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:366:11)
#9 _BufferingStreamSubscription._add (dart:async/stream_impl.dart:297:7)
#10 _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:777:19)
#11 _StreamController._add (dart:async/stream_controller.dart:651:7)
#12 _StreamController.add (dart:async/stream_controller.dart:606:5)
#13 _Socket._onData (dart:io-patch/socket_patch.dart:2455:41)
#14 _rootRunUnary (dart:async/zone.dart:1430:13)
#15 _CustomZone.runUnary (dart:async/zone.dart:1324:19)
#16 _CustomZone.runUnaryGuarded (dart:async/zone.dart:1233:7)
#17 _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:366:11)
#18 _BufferingStreamSubscription._add (dart:async/stream_impl.dart:297:7)
#19 _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:777:19)
#20 _StreamController._add (dart:async/stream_controller.dart:651:7)
#21 _StreamController.add (dart:async/stream_controller.dart:606:5)
#22 new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1942:33)
#23 _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1385:14)
#24 _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#25 _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#26 _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#27 _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:185:5)
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 2 categories.
```
In visual studio flutter is hit and miss sometimes crashing when attempting to chose or add target with same output and sometime crashing on load (again with similar log).
I have multiple locales on this computer including SK, CS, RU, UA but all with utf-8
In regards to less important issue:
Contrary to flutter checks occasional claim, (most cases it does not claim its address missing in PATH, flutter is run and works from any location without specifying path to it and echo $PATH includes the correct path.
### Expected results
Flutter continues runnning enables chosing target at without having to restart after adding new targets
### Actual results
have to restart Visual studio code sometimes several times each time adding target Linux. even clicking on chice crashes the flutter with output above
### Code sample
Tutorials first code
### Screenshots or Video
_No response_
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
flutter doctor -v
```
[✓] Flutter (Channel stable, 3.27.2, on Debian GNU/Linux 12 (bookworm)
6.6.62+rpt-rpi-2712, locale en_GB.UTF-8)
• Flutter version 3.27.2 on channel stable at /home/<Ja>/Tvorba/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 68415ad1d9 (12 days ago), 2025-01-13 10:22:03 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version
35.0.1)
• Android SDK at /usr/lib/android-sdk
• Platform android-35, build-tools 35.0.1
• Java binary at: /opt/android-studio/jbr/bin/java
• Java version OpenJDK Runtime Environment (build
17.0.13+11-Debian-2deb12u1)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• CHROME_EXECUTABLE = chromium
[✓] Linux toolchain - develop for Linux desktop
• Debian clang version 14.0.6
• cmake version 3.25.1
• ninja version 1.11.1
• pkg-config version 1.8.1
[✓] Android Studio (version 2024.2)
• Android Studio at /opt/android-studio
• Flutter plugin version 83.0.3
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
17.0.13+11-Debian-2deb12u1)
[✓] VS Code (version 1.96.4)
• VS Code at /usr/share/code
• Flutter extension version 3.102.0
[☠] Connected device (the doctor check crashed)
✗ Due to an error, the doctor check did not complete. If the error
message below is not helpful, please let us know about this issue at
https://github.com/flutter/flutter/issues.
✗ FormatException: Invalid UTF-8 byte (at offset 59)
• #0 _Utf8Decoder.convertChunked
(dart:convert-patch/convert_patch.dart:1950:7)
#1 _Utf8ConversionSink.addSlice
(dart:convert/string_conversion.dart:304:28)
#2 _Utf8ConversionSink.add
(dart:convert/string_conversion.dart:300:5)
#3 _ConverterStreamEventSink.add
(dart:convert/chunked_conversion.dart:69:18)
#4 _SinkTransformerStreamSubscription._handleData
(dart:async/stream_transformers.dart:111:24)
#5 _rootRunUnary (dart:async/zone.dart:1422:47)
#6 _CustomZone.runUnary (dart:async/zone.dart:1324:19)
#7 _CustomZone.runUnaryGuarded (dart:async/zone.dart:1233:7)
#8 _BufferingStreamSubscription._sendData
(dart:async/stream_impl.dart:366:11)
#9 _BufferingStreamSubscription._add
(dart:async/stream_impl.dart:297:7)
#10 _SyncStreamControllerDispatch._sendData
(dart:async/stream_controller.dart:777:19)
#11 _StreamController._add
(dart:async/stream_controller.dart:651:7)
#12 _StreamController.add
(dart:async/stream_controller.dart:606:5)
#13 _Socket._onData (dart:io-patch/socket_patch.dart:2455:41)
#14 _rootRunUnary (dart:async/zone.dart:1430:13)
#15 _CustomZone.runUnary (dart:async/zone.dart:1324:19)
#16 _CustomZone.runUnaryGuarded (dart:async/zone.dart:1233:7)
#17 _BufferingStreamSubscription._sendData
(dart:async/stream_impl.dart:366:11)
#18 _BufferingStreamSubscription._add
(dart:async/stream_impl.dart:297:7)
#19 _SyncStreamControllerDispatch._sendData
(dart:async/stream_controller.dart:777:19)
#20 _StreamController._add
(dart:async/stream_controller.dart:651:7)
#21 _StreamController.add
(dart:async/stream_controller.dart:606:5)
#22 new _RawSocket.<anonymous closure>
(dart:io-patch/socket_patch.dart:1942:33)
#23 _NativeSocket.issueReadEvent.issue
(dart:io-patch/socket_patch.dart:1385:14)
#24 _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#25 _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#26 _runPendingImmediateCallback
(dart:isolate-patch/isolate_patch.dart:118:13)
#27 _RawReceivePort._handleMessage
(dart:isolate-patch/isolate_patch.dart:185:5)
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.
``` | waiting for customer response,in triage | low | Critical |
2,811,108,477 | vscode | paste option is disable |
Type: <b>Bug</b>
i cant able to paste my code
VS Code version: Code - Insiders 1.97.0-insider (f5782f528629d4200a964cc652055a4da43a7eb1, 2025-01-24T05:04:36.365Z)
OS version: Windows_NT x64 10.0.22631
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i5-12450H (12 x 2496)|
|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.63GB (1.98GB free)|
|Process Argv|--crash-reporter-id 97cbdd43-7eb8-488a-ada8-910ba7d28e20|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (35)</summary>
Extension|Author (truncated)|Version
---|---|---
react-hooks-snippets|AlD|1.2.0
vscode-tailwindcss|bra|0.14.1
npm-intellisense|chr|1.4.5
postcss|css|1.0.9
c-cpp-compile-run|dan|1.0.60
vscode-eslint|dba|3.0.10
es7-react-js-snippets|dsz|4.4.3
prettier-vscode|esb|11.0.0
code-runner|for|0.12.2
codespaces|Git|1.17.3
copilot|Git|1.259.1335
copilot-chat|Git|0.24.2025012402
vsc-python-indent|Kev|1.19.0
vscode-docker|ms-|1.29.4
debugpy|ms-|2024.15.2025012301
python|ms-|2024.23.2025012401
vscode-pylance|ms-|2025.1.101
jupyter|ms-|2025.1.2025012301
jupyter-hub|ms-|2024.10.1002831100
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.2025011401
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-powertoys|ms-|0.1.1
vscode-jupyter-slideshow|ms-|0.1.6
cmake-tools|ms-|1.19.52
cpptools|ms-|1.23.4
cpptools-extension-pack|ms-|1.3.0
remote-explorer|ms-|0.4.3
remote-server|ms-|1.5.2
vscode-speech|ms-|0.12.1
postman-for-vscode|Pos|1.6.1
LiveServer|rit|5.7.9
markdown-preview-enhanced|shd|0.8.15
cmake|twx|0.0.17
tailwind-snippets|Zar|1.0.2
(1 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vsc_aacf:30263846
pythonvspyt551:31179976
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
vscrp:30624060
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupyter:31046869
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
c3hdf307:31184662
6074i472:31201624
dwoutputs:31217127
6e63a538:31218797
9064b325:31222308
copilot_t_ci:31222730
ecdi0152:31224757
```
</details>
<!-- generated by issue reporter --> | info-needed | low | Critical |
2,811,112,982 | ollama | Error: "not authorized to push" | ### What is the issue?
Hi,
At first i have pull a model using ollama (ollama pull qwen:0.5b) then i wanted to push this model and using this command ```ollama push qwen:0.5b``` but i got this error:
pushing fad2a06e4cc7... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 394 MB
pushing 41c2cf8c272f... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 7.3 KB
pushing 1da0581fd4ce... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 130 B
pushing f02dd72bb242... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 59 B
pushing ea0a531a015b... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 485 B
pushing manifest
Error: you are not authorized to push to this namespace, create the model under a namespace you own
is there anyone that have encountered with this issue?!
### OS
_No response_
### GPU
_No response_
### CPU
_No response_
### Ollama version
_No response_ | bug | low | Critical |
2,811,114,817 | rust | Confusing error message when returning impl Trait where the concrete type contains itself. | ### Code
```Rust
#[derive(Debug)]
enum MyTreeNode {
Leaf,
VecNode(Vec<Self>),
}
impl MyTreeNode {
pub fn iter(&self) -> impl Iterator<Item = &Self> + '_ {
[self]
.into_iter()
.chain(self.nonrecursive_iter().flat_map(|e| e.iter()))
}
fn nonrecursive_iter(&self) -> Box<dyn Iterator<Item = &Self> + '_> {
match self {
Self::Leaf => Box::new([].into_iter()),
Self::VecNode(v) => Box::new(v.iter()),
}
}
}
fn main() {
let tree = MyTreeNode::VecNode(vec![
MyTreeNode::Leaf,
MyTreeNode::VecNode(vec![MyTreeNode::Leaf, MyTreeNode::Leaf]),
]);
for node in tree.iter() {
dbg!(node);
}
}
```
### Current output
```Shell
Compiling playground v0.0.1 (/playground)
error: concrete type differs from previous defining opaque type use
--> src/main.rs:9:9
|
9 | / [self]
10 | | .into_iter()
11 | | .chain(self.nonrecursive_iter().flat_map(|e| e.iter()))
| | ^
| | |
| |___________________________________________________________________expected `std::iter::Chain<std::array::IntoIter<&MyTreeNode, 1>, FlatMap<Box<dyn Iterator<Item = &MyTreeNode>>, impl Iterator<Item = &MyTreeNode> + '_, {closure@src/main.rs:11:54: 11:57}>>`, got `impl Iterator<Item = &MyTreeNode> + '_`
| this expression supplies two conflicting concrete types for the same opaque type
error: could not compile `playground` (bin "playground") due to 1 previous error
```
### Desired output
```Shell
```
### Rationale and extra context
[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=c84b7cef49f214b39b851231eaf17912)
I believe the issue here is not that the expression returns two different types, but that it returns a single recursive type. Changing the `iter()` function signature to return a boxed iterator makes the code compile. If I'm right, then I think some wording about boxing the output of recursive function calls makes sense (similar to the message you see if you recurse async function calls).
### Other cases
```Rust
```
### Rust Version
```Shell
rustc 1.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: aarch64-apple-darwin
release: 1.84.0
LLVM version: 19.1.5
```
### Anything else?
_No response_ | A-diagnostics,T-compiler | low | Critical |
2,811,119,437 | next.js | Unexpected Rendering Behavior When Using a 'pages' Folder Outside the App Directory in App Router | ### Link to the code that reproduces this issue
https://github.com/eteen12/Isreal
### To Reproduce
## To reproduce
1. Add a pages directory containing components into the project ( in this example a footer )
2. Add the component to the root layout or include it in the page.js` file as the main renderer for the homepage.
```export default function RootLayout({ children }) {
return (
<html lang="en">
<body
className={`${geistSans.variable} ${geistMono.variable} antialiased`}
>
{children}
<Footer />
</body>
</html>
);
}
```
3. Run the project locally using localhost, then navigate to /footer (or the corresponding route for your component).
### Current vs. Expected behavior
## Current behavior
When using the App Router, placing a file or folder named pages in the root of the project causes unexpected behavior. The components inside this pages folder will render when navigating to their corresponding component names, or in this example case /footer.
## Expected behavior
When using the App Router, the Pages Router should be completely removed and should no longer be referenced for rendering. The behavior should be similar to using a components folder for placing components, where the folder cannot render individual pages. The 'pages' folder should not be treated as a route.
### Provide environment information
```bash
Operating System:
Platform: linux
Arch: x64
Version: #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024
Available memory (MB): 15929
Available CPU cores: 12
Binaries:
Node: 22.12.0
npm: 10.9.0
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 15.1.4 // There is a newer version (15.1.6) available, upgrade recommended!
eslint-config-next: 15.1.4
react: 19.0.0
react-dom: 19.0.0
typescript: 5.7.3
Next.js Config:
output: export
```
### Which area(s) are affected? (Select all that apply)
Navigation
### Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), Other (Deployed)
### Additional context
I understand that naming a components folder 'pages' is unconventional, but this was for a micro meme site I made, and I thought I’d report the issue.
It is available locally and in the cloud flare pages environment, when the site was indexed I noticed that so were the pages component routes. | Navigation | low | Minor |
2,811,137,602 | ui | [bug]: Doesn't select dates using calendar component | ### Describe the bug
there is a css property pointer-event:none that's why we could not select any date
### Affected component/components
Doesnot select date
### How to reproduce
remove the pointer-event:none property
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
```
### System Info
```bash
Browser
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,811,146,381 | PowerToys | Add a feature to prevent accidental pointer movement during mouse clicks with adjustable offset for intentional dragging | ### Description of the new feature / enhancement
I have a computer mouse that's very sensitive to movement, and I want to keep that sensitivity. The problem is that when I click the left button, the mouse sometimes slips slightly, resulting in accidental dragging.
I’d like a feature that does something simple: when the left button is pressed, the computer's mouse pointer shouldn’t move, even if I physically move the mouse slightly by mistake (due to slipping).
Since there can be legitimate cases of dragging a file or something similar, I suggest having an offset—if small mouse movements are detected while the button is pressed, they should be ignored, and the pointer won’t move.
However, if a large movement is detected, it’s likely intentional, so it shouldn’t be ignored. This way, the feature would block most cases of accidental pointer slipping while still allowing legitimate actions like dragging a file.
### Scenario when this would be used?
I wrote:
> The problem is that when I click the left button, the mouse sometimes slips slightly, resulting in accidental dragging.
This should handle this issue
### Supporting information
I can develop it myself. I know that it is possible to develop because I am very expert in Win32 API.
But this is not the kind of things that I ever going to spent time myself. | Needs-Triage | low | Minor |
2,811,147,542 | vscode | Display Image Previews in Path Autocomplete | <!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
It would be incredibly helpful if image previews could be displayed alongside their file paths in the autocomplete suggestions when navigating through image paths.
This feature would improve the developer experience by allowing users to visually identify images without needing to open or hover over the files. It would be particularly useful for projects that involve managing many image assets, such as web development, game development, or content-heavy applications.
Thank you for considering this enhancement!
<img width="955" alt="Image" src="https://github.com/user-attachments/assets/3101785a-33e9-401b-9d2f-e9ca9f8482ce" />
<!-- Describe the feature you'd like. -->
| feature-request,javascript | low | Minor |
2,811,148,699 | rust | ICE: fast reject: `kind mismatch: {type error} 3_u8` | <!--
[31mICE[0m: Rustc ./a.rs '-Zcrate-attr=feature(generic_const_exprs) -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' panicked at /rustc/203e6c127c50c499be53731a39fe36d24f544502/compiler/rustc_type_ir/src/fast_reject.rs:254:22: 'kind mismatch: {type error} 3_u8'', 'thread 'rustc' panicked at /rustc/203e6c127c50c499be53731a39fe36d24f544502/compiler/rustc_type_ir/src/fast_reject.rs:254:22: 'kind mismatch: {type error} 3_u8''
File: /tmp/im/a.rs
-->
auto-reduced (treereduce-rust):
````rust
#![feature(generic_const_exprs)]
trait Traitor<const N: u8 = 1, const M: u8 = repeat_36> {}
impl Traitor<2, 3> for bool {}
fn bar<const N: u8>(arg: &dyn Traitor<N>) -> u8 {
arg.owo()
}
fn main() {
bar(&true);
}
````
original:
````rust
trait Trait<const N: u8 = 12> {
fn uwu(&self) -> u8 {
N
}
}
impl Trait<2> for u32 {}
fn foo(arg: &dyn Trait) -> isize {
arg.uwu()
}
trait Traitor<const N: u8 = 1, const M: u8 = repeat_36> {
fn owo(&self) -> u8 {
M
}
}
impl Traitor<2, 3> for bool {}
fn bar<const N: u8>(arg: &dyn Traitor<N>) -> u8 {
arg.owo()
}
fn main() {
foo(&10_u32);
//~^ error: the trait bound `u32: Trait` is not satisfied
bar(&true);
//~^ error: the trait bound `bool: Traitor<_>` is not satisfied
}
````
Version information
````
rustc 1.86.0-nightly (203e6c127 2025-01-25)
binary: rustc
commit-hash: 203e6c127c50c499be53731a39fe36d24f544502
commit-date: 2025-01-25
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
````
Command:
`/home/matthias/.rustup/toolchains/master/bin/rustc -Zcrate-attr=feature(generic_const_exprs)`
<details><summary><strong>Program output</strong></summary>
<p>
```
error[E0425]: cannot find value `repeat_36` in this scope
--> /tmp/icemaker_global_tempdir.WTfAIAh7lsb4/rustc_testrunner_tmpdir_reporting.MvFPhVMEvs6Q/mvce.rs:1:46
|
1 | trait Traitor<const N: u8 = 1, const M: u8 = repeat_36> {}
| ^^^^^^^^^ not found in this scope
warning: the feature `generic_const_exprs` is incomplete and may not be safe to use and/or cause compiler crashes
--> <crate attribute>:1:9
|
1 | feature(generic_const_exprs)
| ^^^^^^^^^^^^^^^^^^^
|
= note: see issue #76560 <https://github.com/rust-lang/rust/issues/76560> for more information
= note: `#[warn(incomplete_features)]` on by default
error[E0393]: the type parameter `M` must be explicitly specified
--> /tmp/icemaker_global_tempdir.WTfAIAh7lsb4/rustc_testrunner_tmpdir_reporting.MvFPhVMEvs6Q/mvce.rs:5:31
|
1 | trait Traitor<const N: u8 = 1, const M: u8 = repeat_36> {}
| ------------------------------------------------------- type parameter `M` must be specified for this
...
5 | fn bar<const N: u8>(arg: &dyn Traitor<N>) -> u8 {
| ^^^^^^^^^^ missing reference to `M`
|
= note: because the parameter default references `Self`, the parameter must be specified on the object type
thread 'rustc' panicked at /rustc/203e6c127c50c499be53731a39fe36d24f544502/compiler/rustc_type_ir/src/fast_reject.rs:254:22:
kind mismatch: {type error} 3_u8
stack backtrace:
0: 0x7b60dde902a0 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hdfdabc38b8669c9f
1: 0x7b60de6150e6 - core::fmt::write::h85841a8a9f23dd59
2: 0x7b60df5594d1 - std::io::Write::write_fmt::hf2e4fe8e168db1b7
3: 0x7b60dde90102 - std::sys::backtrace::BacktraceLock::print::h14149197b7c0de32
4: 0x7b60dde92582 - std::panicking::default_hook::{{closure}}::h9943e5f3f0626409
5: 0x7b60dde9240a - std::panicking::default_hook::hdd3968de3a098232
6: 0x7b60dd0459e9 - std[57730b54ef401f3]::panicking::update_hook::<alloc[f5830c3c5cfb9e11]::boxed::Box<rustc_driver_impl[238e9adc12ab3263]::install_ice_hook::{closure#1}>>::{closure#0}
7: 0x7b60dde93103 - std::panicking::rust_panic_with_hook::h73ef51d9a205dc0a
8: 0x7b60dde92dfa - std::panicking::begin_panic_handler::{{closure}}::hed515db6078dd255
9: 0x7b60dde90789 - std::sys::backtrace::__rust_end_short_backtrace::h8ba760917d95b5b1
10: 0x7b60dde92abd - rust_begin_unwind
11: 0x7b60dab98400 - core::panicking::panic_fmt::h5ecc779537f0304d
12: 0x7b60db43899b - <rustc_trait_selection[4ba0541b438290d2]::traits::select::SelectionContext>::assemble_candidates_from_impls
13: 0x7b60db415705 - <rustc_trait_selection[4ba0541b438290d2]::traits::select::SelectionContext>::candidate_from_obligation::{closure#0}::{closure#0}
14: 0x7b60dae5c32e - <rustc_trait_selection[4ba0541b438290d2]::traits::select::SelectionContext>::poly_select::{closure#0}
15: 0x7b60deee6030 - <rustc_trait_selection[4ba0541b438290d2]::traits::fulfill::FulfillProcessor as rustc_data_structures[b1621f9a8426d32f]::obligation_forest::ObligationProcessor>::process_obligation
16: 0x7b60de610882 - <rustc_data_structures[b1621f9a8426d32f]::obligation_forest::ObligationForest<rustc_trait_selection[4ba0541b438290d2]::traits::fulfill::PendingPredicateObligation>>::process_obligations::<rustc_trait_selection[4ba0541b438290d2]::traits::fulfill::FulfillProcessor>
17: 0x7b60de79f0e4 - <rustc_hir_typeck[f3c634e21e25c7e1]::fn_ctxt::FnCtxt>::confirm_builtin_call
18: 0x7b60df390bc8 - <rustc_hir_typeck[f3c634e21e25c7e1]::fn_ctxt::FnCtxt>::check_expr_with_expectation_and_args
19: 0x7b60df389dcf - <rustc_hir_typeck[f3c634e21e25c7e1]::fn_ctxt::FnCtxt>::check_expr_block
20: 0x7b60df3916d4 - <rustc_hir_typeck[f3c634e21e25c7e1]::fn_ctxt::FnCtxt>::check_expr_with_expectation_and_args
21: 0x7b60dec88780 - rustc_hir_typeck[f3c634e21e25c7e1]::check::check_fn
22: 0x7b60dec9163d - rustc_hir_typeck[f3c634e21e25c7e1]::typeck_with_inspect::{closure#0}
23: 0x7b60dec8f64c - rustc_query_impl[db064f70679e7e57]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[db064f70679e7e57]::query_impl::typeck::dynamic_query::{closure#2}::{closure#0}, rustc_middle[e5994b11539d1088]::query::erase::Erased<[u8; 8usize]>>
24: 0x7b60de981a4e - rustc_query_system[acb98781fee9c8ed]::query::plumbing::try_execute_query::<rustc_query_impl[db064f70679e7e57]::DynamicConfig<rustc_data_structures[b1621f9a8426d32f]::vec_cache::VecCache<rustc_span[573b00108592c307]::def_id::LocalDefId, rustc_middle[e5994b11539d1088]::query::erase::Erased<[u8; 8usize]>, rustc_query_system[acb98781fee9c8ed]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[db064f70679e7e57]::plumbing::QueryCtxt, false>
25: 0x7b60de97ff51 - rustc_query_impl[db064f70679e7e57]::query_impl::typeck::get_query_non_incr::__rust_end_short_backtrace
26: 0x7b60de97fc0b - <rustc_middle[e5994b11539d1088]::hir::map::Map>::par_body_owners::<rustc_hir_analysis[f7ab43cc31358404]::check_crate::{closure#4}>::{closure#0}
27: 0x7b60de97dcbf - rustc_hir_analysis[f7ab43cc31358404]::check_crate
28: 0x7b60de97a2e2 - rustc_interface[a9a02922dc001c32]::passes::run_required_analyses
29: 0x7b60df554bde - rustc_interface[a9a02922dc001c32]::passes::analysis
30: 0x7b60df554baf - rustc_query_impl[db064f70679e7e57]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[db064f70679e7e57]::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle[e5994b11539d1088]::query::erase::Erased<[u8; 0usize]>>
31: 0x7b60df541b55 - rustc_query_system[acb98781fee9c8ed]::query::plumbing::try_execute_query::<rustc_query_impl[db064f70679e7e57]::DynamicConfig<rustc_query_system[acb98781fee9c8ed]::query::caches::SingleCache<rustc_middle[e5994b11539d1088]::query::erase::Erased<[u8; 0usize]>>, false, false, false>, rustc_query_impl[db064f70679e7e57]::plumbing::QueryCtxt, false>
32: 0x7b60df54188e - rustc_query_impl[db064f70679e7e57]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
33: 0x7b60df603969 - rustc_interface[a9a02922dc001c32]::passes::create_and_enter_global_ctxt::<core[bef17dfe197dbeb2]::option::Option<rustc_interface[a9a02922dc001c32]::queries::Linker>, rustc_driver_impl[238e9adc12ab3263]::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
34: 0x7b60df5ad513 - rustc_interface[a9a02922dc001c32]::interface::run_compiler::<(), rustc_driver_impl[238e9adc12ab3263]::run_compiler::{closure#0}>::{closure#1}
35: 0x7b60df4a7235 - std[57730b54ef401f3]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[a9a02922dc001c32]::util::run_in_thread_with_globals<rustc_interface[a9a02922dc001c32]::util::run_in_thread_pool_with_globals<rustc_interface[a9a02922dc001c32]::interface::run_compiler<(), rustc_driver_impl[238e9adc12ab3263]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>
36: 0x7b60df4a6f19 - <<std[57730b54ef401f3]::thread::Builder>::spawn_unchecked_<rustc_interface[a9a02922dc001c32]::util::run_in_thread_with_globals<rustc_interface[a9a02922dc001c32]::util::run_in_thread_pool_with_globals<rustc_interface[a9a02922dc001c32]::interface::run_compiler<(), rustc_driver_impl[238e9adc12ab3263]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core[bef17dfe197dbeb2]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
37: 0x7b60df4a66af - std::sys::pal::unix::thread::Thread::new::thread_start::h58ab2ce80d2171c1
38: 0x7b60d98a339d - <unknown>
39: 0x7b60d992849c - <unknown>
40: 0x0 - <unknown>
error: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: please make sure that you have updated to the latest nightly
note: rustc 1.86.0-nightly (203e6c127 2025-01-25) running on x86_64-unknown-linux-gnu
note: compiler flags: -Z crate-attr=feature(generic_const_exprs) -Z dump-mir-dir=dir
query stack during panic:
#0 [typeck] type-checking `main`
#1 [analysis] running analysis passes on this crate
end of query stack
error: aborting due to 2 previous errors; 1 warning emitted
Some errors have detailed explanations: E0393, E0425.
For more information about an error, try `rustc --explain E0393`.
```
</p>
</details>
<!--
query stack:
#0 [typeck] type-checking `main`
#1 [analysis] running analysis passes on this crate
-->
@rustbot label +F-generic_const_exprs | I-ICE,T-compiler,C-bug,F-generic_const_exprs,A-trait-objects | low | Critical |
2,811,149,509 | flutter | Border dimensions are incorrect when strokeAlign is set to strokeAlignInside or strokeAlignOutside. | ### Steps to reproduce
When setting `stokeAlign` of `Border` to `strokeAlignInside` or `strokeAlignOutside` the `dimensions` are incorrect.
`Border.all(width: 10, strokeAlign: BorderSide.strokeAlignInside).dimensions` returns `EdgeInsets.all(10)` while `EdgeInsets.zero` is expected.
`Border.all(width: 10, strokeAlign: BorderSide.strokeAlignOutside).dimensions` returns `EdgeInsets.zero` while `EdgeInsets.all(10)` is expected.
The samples below show how this affects the size of the `Container` widget.
1. When `Border.strokeAlign` is set to `BorderSide.strokeAlignInside` `Container` adds 10px padding to the child and thus size is 220px instead of 200px.
<img width="363" alt="Image" src="https://github.com/user-attachments/assets/3a92f549-dd17-4d52-91af-67c6d8337129" />
2. When `Border.strokeAlign` is set to `BorderSide.strokeAlignOutside` `Container` doesn't add padding to the child and thus size is 200px instead of 220px.
<img width="363" alt="Image" src="https://github.com/user-attachments/assets/d0255132-fdd0-49c9-82a4-236034be829b" />
### Expected results
`Border.all(width: 10, strokeAlign: BorderSide.strokeAlignInside).dimensions` should return `EdgeInsets.zero` as the border is drawn inside the border path.
`Border.all(width: 10, strokeAlign: BorderSide.strokeAlignOutside).dimensions` should return `EdgeInsets.all(10)` as the border is drawn outside the border path.
### Actual results
`Border.all(width: 10, strokeAlign: BorderSide.strokeAlignInside).dimensions` returns `EdgeInsets.all(10)`
`Border.all(width: 10, strokeAlign: BorderSide.strokeAlignOutside).dimensions` returns `EdgeInsets.zero`
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
void main() {
runApp(const App());
}
class App extends StatelessWidget {
const App({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
body: Center(
child: Container(
decoration: BoxDecoration(
color: Colors.red,
border: Border.all(
width: 10,
strokeAlign: BorderSide.strokeAlignInside,
// strokeAlign: BorderSide.strokeAlignCenter,
// strokeAlign: BorderSide.strokeAlignOutside,
),
),
child: SizedBox.square(dimension: 200),
),
),
),
);
}
}
```
</details>
### Screenshots or Video
<details closed>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details closed><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel master, 3.28.0-2.0.pre.38865, on macOS 15.2 24C101 darwin-arm64, locale en-US) [2.7s]
• Flutter version 3.28.0-2.0.pre.38865 on channel master at /Users/ksokolovskyi/development/flutter_master
• Upstream repository [email protected]:ksokolovskyi/flutter.git
• FLUTTER_GIT_URL = [email protected]:ksokolovskyi/flutter.git
• Framework revision 02e11f95a1 (29 hours ago), 2025-01-24 09:50:38 -0500
• Engine revision 02e11f95a1
• Dart version 3.8.0 (build 3.8.0-24.0.dev)
• DevTools version 2.42.0
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0) [1,779ms]
• Android SDK at /Users/ksokolovskyi/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• ANDROID_HOME = /Users/ksokolovskyi/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
• All Android licenses accepted.
[!] Xcode - develop for iOS and macOS (Xcode 16.2) [931ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16C5032a
! CocoaPods 1.14.3 out of date (1.16.2 is recommended).
CocoaPods is a package manager for iOS or macOS platform code.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/to/platform-plugins
To update CocoaPods, see https://guides.cocoapods.org/using/getting-started.html#updating-cocoapods
[✓] Chrome - develop for the web [10ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.2) [9ms]
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
[✓] VS Code (version 1.96.4) [7ms]
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (4 available) [6.2s]
• iPhone 13 mini (mobile) • FE5BEA00-295F-48CB-9632-96E7F4F8C370 • ios • com.apple.CoreSimulator.SimRuntime.iOS-18-0 (simulator)
• macOS (desktop) • macos • darwin-arm64 • macOS 15.2 24C101 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 125.0.6422.141
[✓] Network resources [1,208ms]
• All expected network resources are available.
```
</details>
| framework,has reproducible steps,team-framework,found in release: 3.27,found in release: 3.29 | low | Minor |
2,811,154,186 | godot | Shader compilation error when defining the MASS property to a Particle ShaderMaterial | ### Tested versions
Reproducible in: 4.3.stable
### System information
Godot v4.3.stable - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6750 XT (RADV NAVI22) - AMD Ryzen 5 2400G with Radeon Vega Graphics (8 Threads)
### Issue description
When writing a ShaderMaterial to a GPUParticles3D a compilation error occurs when defining the MASS built-in variable, either in the start() or process() function.
```
servers/rendering/renderer_rd/storage_rd/particles_storage.cpp:1699 - Condition "!particles_storage->particles_shader.shader.version_is_valid(version)" is true.
servers/rendering/renderer_rd/shader_rd.cpp:293 - Error compiling Compute shader, variant #0 ().
servers/rendering/renderer_rd/shader_rd.cpp:294 - Failed parse:
ERROR: 0:462: 'm_MASS' : undeclared identifier
ERROR: 0:462: '' : compilation terminated
ERROR: 2 compilation errors. No code generated.
servers/rendering/renderer_rd/shader_rd.cpp:297 - code:
1 |
2 | #version 450
3 |
4 |
5 | #define SAMPLERS_BINDING_FIRST_INDEX 3
6 |
7 | #define START_CODE_USED
8 | #define PROCESS_CODE_USED
9 | #define RENDER_DRIVER_VULKAN
10 |
11 | layout(local_size_x = 64, local_size_y = 1, local_size_z = 1) in;
12 |
13 | #define SDF_MAX_LENGTH 16384.0
14 |
15 | /* SET 0: GLOBAL DATA */
16 |
17 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 0) uniform sampler SAMPLER_NEAREST_CLAMP;
18 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 1) uniform sampler SAMPLER_LINEAR_CLAMP;
19 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 2) uniform sampler SAMPLER_NEAREST_WITH_MIPMAPS_CLAMP;
20 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 3) uniform sampler SAMPLER_LINEAR_WITH_MIPMAPS_CLAMP;
21 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 4) uniform sampler SAMPLER_NEAREST_WITH_MIPMAPS_ANISOTROPIC_CLAMP;
22 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 5) uniform sampler SAMPLER_LINEAR_WITH_MIPMAPS_ANISOTROPIC_CLAMP;
23 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 6) uniform sampler SAMPLER_NEAREST_REPEAT;
24 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 7) uniform sampler SAMPLER_LINEAR_REPEAT;
25 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 8) uniform sampler SAMPLER_NEAREST_WITH_MIPMAPS_REPEAT;
26 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 9) uniform sampler SAMPLER_LINEAR_WITH_MIPMAPS_REPEAT;
27 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 10) uniform sampler SAMPLER_NEAREST_WITH_MIPMAPS_ANISOTROPIC_REPEAT;
28 | layout(set = 0, binding = SAMPLERS_BINDING_FIRST_INDEX + 11) uniform sampler SAMPLER_LINEAR_WITH_MIPMAPS_ANISOTROPIC_REPEAT;
29 |
30 | layout(set = 0, binding = 2, std430) restrict readonly buffer GlobalShaderUniformData {
31 | vec4 data[];
32 | }
33 | global_shader_uniforms;
34 |
35 | /* Set 1: FRAME AND PARTICLE DATA */
36 |
37 |
38 |
39 | #define MAX_ATTRACTORS 32
40 |
41 | #define ATTRACTOR_TYPE_SPHERE 0
42 | #define ATTRACTOR_TYPE_BOX 1
43 | #define ATTRACTOR_TYPE_VECTOR_FIELD 2
44 |
45 | struct Attractor {
46 | mat4 transform;
47 | vec3 extents;
48 | uint type;
49 | uint texture_index;
50 | float strength;
51 | float attenuation;
52 | float directionality;
53 | };
54 |
55 | #define MAX_COLLIDERS 32
56 |
57 | #define COLLIDER_TYPE_SPHERE 0
58 | #define COLLIDER_TYPE_BOX 1
59 | #define COLLIDER_TYPE_SDF 2
60 | #define COLLIDER_TYPE_HEIGHT_FIELD 3
61 | #define COLLIDER_TYPE_2D_SDF 4
62 |
63 | struct Collider {
64 | mat4 transform;
65 | vec3 extents;
66 | uint type;
67 |
68 | uint texture_index;
69 | float scale;
70 | uint pad[2];
71 | };
72 |
73 | struct FrameParams {
74 | bool emitting;
75 | float system_phase;
76 | float prev_system_phase;
77 | uint cycle;
78 |
79 | float explosiveness;
80 | float randomness;
81 | float time;
82 | float delta;
83 |
84 | uint frame;
85 | float amount_ratio;
86 | uint pad1;
87 | uint pad2;
88 |
89 | uint random_seed;
90 | uint attractor_count;
91 | uint collider_count;
92 | float particle_size;
93 |
94 | mat4 emission_transform;
95 | vec3 emitter_velocity;
96 | float interp_to_end;
97 |
98 | Attractor attractors[MAX_ATTRACTORS];
99 | Collider colliders[MAX_COLLIDERS];
100 | };
101 |
102 | layout(set = 1, binding = 0, std430) restrict buffer FrameHistory {
103 | FrameParams data[];
104 | }
105 | frame_history;
106 |
107 | #define PARTICLE_FLAG_ACTIVE uint(1)
108 | #define PARTICLE_FLAG_STARTED uint(2)
109 | #define PARTICLE_FLAG_TRAILED uint(4)
110 | #define PARTICLE_FRAME_MASK uint(0xFFFF)
111 | #define PARTICLE_FRAME_SHIFT uint(16)
112 |
113 | struct ParticleData {
114 | mat4 xform;
115 | vec3 velocity;
116 | uint flags;
117 | vec4 color;
118 | vec4 custom;
119 | #ifdef USERDATA1_USED
120 | vec4 userdata1;
121 | #endif
122 | #ifdef USERDATA2_USED
123 | vec4 userdata2;
124 | #endif
125 | #ifdef USERDATA3_USED
126 | vec4 userdata3;
127 | #endif
128 | #ifdef USERDATA4_USED
129 | vec4 userdata4;
130 | #endif
131 | #ifdef USERDATA5_USED
132 | vec4 userdata5;
133 | #endif
134 | #ifdef USERDATA6_USED
135 | vec4 userdata6;
136 | #endif
137 | };
138 |
139 | layout(set = 1, binding = 1, std430) restrict buffer Particles {
140 | ParticleData data[];
141 | }
142 | particles;
143 |
144 | #define EMISSION_FLAG_HAS_POSITION 1
145 | #define EMISSION_FLAG_HAS_ROTATION_SCALE 2
146 | #define EMISSION_FLAG_HAS_VELOCITY 4
147 | #define EMISSION_FLAG_HAS_COLOR 8
148 | #define EMISSION_FLAG_HAS_CUSTOM 16
149 |
150 | struct ParticleEmission {
151 | mat4 xform;
152 | vec3 velocity;
153 | uint flags;
154 | vec4 color;
155 | vec4 custom;
156 | };
157 |
158 | layout(set = 1, binding = 2, std430) restrict buffer SourceEmission {
159 | int particle_count;
160 | uint pad0;
161 | uint pad1;
162 | uint pad2;
163 | ParticleEmission data[];
164 | }
165 | src_particles;
166 |
167 | layout(set = 1, binding = 3, std430) restrict buffer DestEmission {
168 | int particle_count;
169 | int particle_max;
170 | uint pad1;
171 | uint pad2;
172 | ParticleEmission data[];
173 | }
174 | dst_particles;
175 |
176 | /* SET 2: COLLIDER/ATTRACTOR TEXTURES */
177 |
178 | #define MAX_3D_TEXTURES 7
179 |
180 | layout(set = 2, binding = 0) uniform texture3D sdf_vec_textures[MAX_3D_TEXTURES];
181 | layout(set = 2, binding = 1) uniform texture2D height_field_texture;
182 |
183 | /* SET 3: MATERIAL */
184 |
185 | #ifdef MATERIAL_UNIFORMS_USED
186 | layout(set = 3, binding = 0, std140) uniform MaterialUniforms{
187 |
188 |
189 | } material;
190 | #endif
191 |
192 | layout(push_constant, std430) uniform Params {
193 | float lifetime;
194 | bool clear;
195 | uint total_particles;
196 | uint trail_size;
197 | bool use_fractional_delta;
198 | bool sub_emitter_mode;
199 | bool can_emit;
200 | bool trail_pass;
201 | }
202 | params;
203 |
204 | uint hash(uint x) {
205 | x = ((x >> uint(16)) ^ x) * uint(0x45d9f3b);
206 | x = ((x >> uint(16)) ^ x) * uint(0x45d9f3b);
207 | x = (x >> uint(16)) ^ x;
208 | return x;
209 | }
210 |
211 | bool emit_subparticle(mat4 p_xform, vec3 p_velocity, vec4 p_color, vec4 p_custom, uint p_flags) {
212 | if (!params.can_emit) {
213 | return false;
214 | }
215 |
216 | bool valid = false;
217 |
218 | int dst_index = atomicAdd(dst_particles.particle_count, 1);
219 |
220 | if (dst_index >= dst_particles.particle_max) {
221 | atomicAdd(dst_particles.particle_count, -1);
222 | return false;
223 | }
224 |
225 | dst_particles.data[dst_index].xform = p_xform;
226 | dst_particles.data[dst_index].velocity = p_velocity;
227 | dst_particles.data[dst_index].color = p_color;
228 | dst_particles.data[dst_index].custom = p_custom;
229 | dst_particles.data[dst_index].flags = p_flags;
230 |
231 | return true;
232 | }
233 |
234 | vec3 safe_normalize(vec3 direction) {
235 | const float EPSILON = 0.001;
236 | if (length(direction) < EPSILON) {
237 | return vec3(0.0);
238 | }
239 | return normalize(direction);
240 | }
241 |
242 |
243 | void main() {
244 | uint particle = gl_GlobalInvocationID.x;
245 |
246 | if (params.trail_size > 1) {
247 | if (params.trail_pass) {
248 | if (particle >= params.total_particles * (params.trail_size - 1)) {
249 | return;
250 | }
251 | particle += (particle / (params.trail_size - 1)) + 1;
252 | } else {
253 | if (particle >= params.total_particles) {
254 | return;
255 | }
256 | particle *= params.trail_size;
257 | }
258 | }
259 |
260 | if (particle >= params.total_particles * params.trail_size) {
261 | return;
262 | }
263 |
264 | uint index = particle / params.trail_size;
265 | uint frame = (particle % params.trail_size);
266 |
267 | #define FRAME frame_history.data[frame]
268 | #define PARTICLE particles.data[particle]
269 |
270 | bool apply_forces = true;
271 | bool apply_velocity = true;
272 | float local_delta = FRAME.delta;
273 |
274 | float mass = 1.0;
275 |
276 | bool restart = false;
277 |
278 | bool restart_position = false;
279 | bool restart_rotation_scale = false;
280 | bool restart_velocity = false;
281 | bool restart_color = false;
282 | bool restart_custom = false;
283 |
284 | if (params.clear) {
285 | PARTICLE.color = vec4(1.0);
286 | PARTICLE.custom = vec4(0.0);
287 | PARTICLE.velocity = vec3(0.0);
288 | PARTICLE.flags = 0;
289 | PARTICLE.xform = mat4(
290 | vec4(1.0, 0.0, 0.0, 0.0),
291 | vec4(0.0, 1.0, 0.0, 0.0),
292 | vec4(0.0, 0.0, 1.0, 0.0),
293 | vec4(0.0, 0.0, 0.0, 1.0));
294 | }
295 |
296 |
297 |
298 | if (params.trail_pass) {
299 |
300 | uint src_idx = index * params.trail_size;
301 | if (bool(particles.data[src_idx].flags & PARTICLE_FLAG_STARTED)) {
302 |
303 | PARTICLE.color = particles.data[src_idx].color;
304 | PARTICLE.custom = particles.data[src_idx].custom;
305 | PARTICLE.velocity = particles.data[src_idx].velocity;
306 | PARTICLE.flags = PARTICLE_FLAG_TRAILED | ((frame_history.data[0].frame & PARTICLE_FRAME_MASK) << PARTICLE_FRAME_SHIFT);
307 | PARTICLE.xform = particles.data[src_idx].xform;
308 | #ifdef USERDATA1_USED
309 | PARTICLE.userdata1 = particles.data[src_idx].userdata1;
310 | #endif
311 | #ifdef USERDATA2_USED
312 | PARTICLE.userdata2 = particles.data[src_idx].userdata2;
313 | #endif
314 | #ifdef USERDATA3_USED
315 | PARTICLE.userdata3 = particles.data[src_idx].userdata3;
316 | #endif
317 | #ifdef USERDATA4_USED
318 | PARTICLE.userdata4 = particles.data[src_idx].userdata4;
319 | #endif
320 | #ifdef USERDATA5_USED
321 | PARTICLE.userdata5 = particles.data[src_idx].userdata5;
322 | #endif
323 | #ifdef USERDATA6_USED
324 | PARTICLE.userdata6 = particles.data[src_idx].userdata6;
325 | #endif
326 | }
327 | if (!bool(particles.data[src_idx].flags & PARTICLE_FLAG_ACTIVE)) {
328 |
329 | PARTICLE.flags = 0;
330 | return;
331 | }
332 | if (bool(PARTICLE.flags & PARTICLE_FLAG_TRAILED) && ((PARTICLE.flags >> PARTICLE_FRAME_SHIFT) == (FRAME.frame & PARTICLE_FRAME_MASK))) {
333 |
334 | PARTICLE.flags = PARTICLE_FLAG_ACTIVE | (particles.data[src_idx].flags & (PARTICLE_FRAME_MASK << PARTICLE_FRAME_SHIFT));
335 | return;
336 | }
337 |
338 | } else {
339 | PARTICLE.flags &= ~PARTICLE_FLAG_STARTED;
340 | }
341 |
342 | bool collided = false;
343 | vec3 collision_normal = vec3(0.0);
344 | float collision_depth = 0.0;
345 |
346 | vec3 attractor_force = vec3(0.0);
347 |
348 | #if !defined(DISABLE_VELOCITY)
349 |
350 | if (bool(PARTICLE.flags & PARTICLE_FLAG_ACTIVE)) {
351 | PARTICLE.xform[3].xyz += PARTICLE.velocity * local_delta;
352 | }
353 | #endif
354 |
355 | if (!params.trail_pass && params.sub_emitter_mode) {
356 | if (!bool(PARTICLE.flags & PARTICLE_FLAG_ACTIVE)) {
357 | int src_index = atomicAdd(src_particles.particle_count, -1) - 1;
358 |
359 | if (src_index >= 0) {
360 | PARTICLE.flags = (PARTICLE_FLAG_ACTIVE | PARTICLE_FLAG_STARTED | (FRAME.cycle << PARTICLE_FRAME_SHIFT));
361 | restart = true;
362 |
363 | if (bool(src_particles.data[src_index].flags & EMISSION_FLAG_HAS_POSITION)) {
364 | PARTICLE.xform[3] = src_particles.data[src_index].xform[3];
365 | } else {
366 | PARTICLE.xform[3] = vec4(0, 0, 0, 1);
367 | restart_position = true;
368 | }
369 | if (bool(src_particles.data[src_index].flags & EMISSION_FLAG_HAS_ROTATION_SCALE)) {
370 | PARTICLE.xform[0] = src_particles.data[src_index].xform[0];
371 | PARTICLE.xform[1] = src_particles.data[src_index].xform[1];
372 | PARTICLE.xform[2] = src_particles.data[src_index].xform[2];
373 | } else {
374 | PARTICLE.xform[0] = vec4(1, 0, 0, 0);
375 | PARTICLE.xform[1] = vec4(0, 1, 0, 0);
376 | PARTICLE.xform[2] = vec4(0, 0, 1, 0);
377 | restart_rotation_scale = true;
378 | }
379 | if (bool(src_particles.data[src_index].flags & EMISSION_FLAG_HAS_VELOCITY)) {
380 | PARTICLE.velocity = src_particles.data[src_index].velocity;
381 | } else {
382 | PARTICLE.velocity = vec3(0);
383 | restart_velocity = true;
384 | }
385 | if (bool(src_particles.data[src_index].flags & EMISSION_FLAG_HAS_COLOR)) {
386 | PARTICLE.color = src_particles.data[src_index].color;
387 | } else {
388 | PARTICLE.color = vec4(1);
389 | restart_color = true;
390 | }
391 |
392 | if (bool(src_particles.data[src_index].flags & EMISSION_FLAG_HAS_CUSTOM)) {
393 | PARTICLE.custom = src_particles.data[src_index].custom;
394 | } else {
395 | PARTICLE.custom = vec4(0);
396 | restart_custom = true;
397 | }
398 | }
399 | }
400 |
401 | } else if (FRAME.emitting) {
402 | float restart_phase = float(index) / float(params.total_particles);
403 |
404 | if (FRAME.randomness > 0.0) {
405 | uint seed = FRAME.cycle;
406 | if (restart_phase >= FRAME.system_phase) {
407 | seed -= uint(1);
408 | }
409 | seed *= uint(params.total_particles);
410 | seed += uint(index);
411 | float random = float(hash(seed) % uint(65536)) / 65536.0;
412 | restart_phase += FRAME.randomness * random * 1.0 / float(params.total_particles);
413 | }
414 |
415 | restart_phase *= (1.0 - FRAME.explosiveness);
416 |
417 | if (FRAME.system_phase > FRAME.prev_system_phase) {
418 |
419 |
420 | if (restart_phase >= FRAME.prev_system_phase && restart_phase < FRAME.system_phase) {
421 | restart = true;
422 | if (params.use_fractional_delta) {
423 | local_delta = (FRAME.system_phase - restart_phase) * params.lifetime;
424 | }
425 | }
426 |
427 | } else if (FRAME.delta > 0.0) {
428 | if (restart_phase >= FRAME.prev_system_phase) {
429 | restart = true;
430 | if (params.use_fractional_delta) {
431 | local_delta = (1.0 - restart_phase + FRAME.system_phase) * params.lifetime;
432 | }
433 |
434 | } else if (restart_phase < FRAME.system_phase) {
435 | restart = true;
436 | if (params.use_fractional_delta) {
437 | local_delta = (FRAME.system_phase - restart_phase) * params.lifetime;
438 | }
439 | }
440 | }
441 |
442 | if (params.trail_pass) {
443 | restart = false;
444 | }
445 |
446 | if (restart) {
447 | PARTICLE.flags = FRAME.emitting ? (PARTICLE_FLAG_ACTIVE | PARTICLE_FLAG_STARTED | (FRAME.cycle << PARTICLE_FRAME_SHIFT)) : 0;
448 | restart_position = true;
449 | restart_rotation_scale = true;
450 | restart_velocity = true;
451 | restart_color = true;
452 | restart_custom = true;
453 | }
454 | }
455 |
456 | bool particle_active = bool(PARTICLE.flags & PARTICLE_FLAG_ACTIVE);
457 |
458 | uint particle_number = (PARTICLE.flags >> PARTICLE_FRAME_SHIFT) * uint(params.total_particles) + index;
459 |
460 | if (restart && particle_active) {
461 | {
462 | m_MASS=1.0;
463 | PARTICLE.xform[3].xyz=vec3(0.0,0.0,0.0);
464 | PARTICLE.velocity.x=2.0;
465 | }
466 | }
467 |
468 | if (particle_active) {
469 | for (uint i = 0; i < FRAME.attractor_count; i++) {
470 | vec3 dir;
471 | float amount;
472 | vec3 rel_vec = PARTICLE.xform[3].xyz - FRAME.attractors[i].transform[3].xyz;
473 | vec3 local_pos = rel_vec * mat3(FRAME.attractors[i].transform);
474 |
475 | switch (FRAME.attractors[i].type) {
476 | case ATTRACTOR_TYPE_SPHERE: {
477 | dir = safe_normalize(rel_vec);
478 | float d = length(local_pos) / FRAME.attractors[i].extents.x;
479 | if (d > 1.0) {
480 | continue;
481 | }
482 | amount = max(0.0, 1.0 - d);
483 | } break;
484 | case ATTRACTOR_TYPE_BOX: {
485 | dir = safe_normalize(rel_vec);
486 |
487 | vec3 abs_pos = abs(local_pos / FRAME.attractors[i].extents);
488 | float d = max(abs_pos.x, max(abs_pos.y, abs_pos.z));
489 | if (d > 1.0) {
490 | continue;
491 | }
492 | amount = max(0.0, 1.0 - d);
493 |
494 | } break;
495 | case ATTRACTOR_TYPE_VECTOR_FIELD: {
496 | vec3 uvw_pos = (local_pos / FRAME.attractors[i].extents + 1.0) * 0.5;
497 | if (any(lessThan(uvw_pos, vec3(0.0))) || any(greaterThan(uvw_pos, vec3(1.0)))) {
498 | continue;
499 | }
500 | vec3 s = texture(sampler3D(sdf_vec_textures[FRAME.attractors[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos).xyz * -2.0 + 1.0;
501 | dir = mat3(FRAME.attractors[i].transform) * safe_normalize(s);
502 | amount = length(s);
503 |
504 | } break;
505 | }
506 | amount = pow(amount, FRAME.attractors[i].attenuation);
507 | dir = safe_normalize(mix(dir, FRAME.attractors[i].transform[2].xyz, FRAME.attractors[i].directionality));
508 | attractor_force -= amount * dir * FRAME.attractors[i].strength;
509 | }
510 |
511 | float particle_size = FRAME.particle_size;
512 |
513 | #ifdef USE_COLLISION_SCALE
514 |
515 | particle_size *= dot(vec3(length(PARTICLE.xform[0].xyz), length(PARTICLE.xform[1].xyz), length(PARTICLE.xform[2].xyz)), vec3(0.33333333333));
516 |
517 | #endif
518 |
519 | if (FRAME.collider_count == 1 && FRAME.colliders[0].type == COLLIDER_TYPE_2D_SDF) {
520 |
521 |
522 | vec2 pos = PARTICLE.xform[3].xy;
523 | vec4 to_sdf_x = FRAME.colliders[0].transform[0];
524 | vec4 to_sdf_y = FRAME.colliders[0].transform[1];
525 | vec2 sdf_pos = vec2(dot(vec4(pos, 0, 1), to_sdf_x), dot(vec4(pos, 0, 1), to_sdf_y));
526 |
527 | vec4 sdf_to_screen = vec4(FRAME.colliders[0].extents, FRAME.colliders[0].scale);
528 |
529 | vec2 uv_pos = sdf_pos * sdf_to_screen.xy + sdf_to_screen.zw;
530 |
531 | if (all(greaterThan(uv_pos, vec2(0.0))) && all(lessThan(uv_pos, vec2(1.0)))) {
532 | vec2 pos2 = pos + vec2(0, particle_size);
533 | vec2 sdf_pos2 = vec2(dot(vec4(pos2, 0, 1), to_sdf_x), dot(vec4(pos2, 0, 1), to_sdf_y));
534 | float sdf_particle_size = distance(sdf_pos, sdf_pos2);
535 |
536 | float d = texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uv_pos).r * SDF_MAX_LENGTH;
537 |
538 | d -= sdf_particle_size;
539 |
540 | if (d < 0.0) {
541 | const float EPSILON = 0.001;
542 | vec2 n = normalize(vec2(
543 | texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uv_pos + vec2(EPSILON, 0.0)).r - texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uv_pos - vec2(EPSILON, 0.0)).r,
544 | texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uv_pos + vec2(0.0, EPSILON)).r - texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uv_pos - vec2(0.0, EPSILON)).r));
545 |
546 | collided = true;
547 | sdf_pos2 = sdf_pos + n * d;
548 | pos2 = vec2(dot(vec4(sdf_pos2, 0, 1), FRAME.colliders[0].transform[2]), dot(vec4(sdf_pos2, 0, 1), FRAME.colliders[0].transform[3]));
549 |
550 | n = pos - pos2;
551 |
552 | collision_normal = normalize(vec3(n, 0.0));
553 | collision_depth = length(n);
554 | }
555 | }
556 |
557 | } else {
558 | for (uint i = 0; i < FRAME.collider_count; i++) {
559 | vec3 normal;
560 | float depth;
561 | bool col = false;
562 |
563 | vec3 rel_vec = PARTICLE.xform[3].xyz - FRAME.colliders[i].transform[3].xyz;
564 | vec3 local_pos = rel_vec * mat3(FRAME.colliders[i].transform);
565 |
566 |
567 | const float EPSILON = 0.001;
568 | switch (FRAME.colliders[i].type) {
569 | case COLLIDER_TYPE_SPHERE: {
570 | float d = length(rel_vec) - (particle_size + FRAME.colliders[i].extents.x);
571 |
572 | if (d <= EPSILON) {
573 | col = true;
574 | depth = -d;
575 | normal = normalize(rel_vec);
576 | }
577 |
578 | } break;
579 | case COLLIDER_TYPE_BOX: {
580 | vec3 abs_pos = abs(local_pos);
581 | vec3 sgn_pos = sign(local_pos);
582 |
583 | if (any(greaterThan(abs_pos, FRAME.colliders[i].extents))) {
584 |
585 |
586 | vec3 closest = min(abs_pos, FRAME.colliders[i].extents);
587 | vec3 rel = abs_pos - closest;
588 | depth = length(rel) - particle_size;
589 | if (depth <= EPSILON) {
590 | col = true;
591 | normal = mat3(FRAME.colliders[i].transform) * (normalize(rel) * sgn_pos);
592 | depth = -depth;
593 | }
594 | } else {
595 |
596 | vec3 axis_len = FRAME.colliders[i].extents - abs_pos;
597 |
598 | if (all(lessThan(axis_len.xx, axis_len.yz))) {
599 | normal = vec3(1, 0, 0);
600 | } else if (all(lessThan(axis_len.yy, axis_len.xz))) {
601 | normal = vec3(0, 1, 0);
602 | } else {
603 | normal = vec3(0, 0, 1);
604 | }
605 |
606 | col = true;
607 | depth = dot(normal * axis_len, vec3(1)) + particle_size;
608 | normal = mat3(FRAME.colliders[i].transform) * (normal * sgn_pos);
609 | }
610 |
611 | } break;
612 | case COLLIDER_TYPE_SDF: {
613 | vec3 apos = abs(local_pos);
614 | float extra_dist = 0.0;
615 | if (any(greaterThan(apos, FRAME.colliders[i].extents))) {
616 | vec3 mpos = min(apos, FRAME.colliders[i].extents);
617 | extra_dist = distance(mpos, apos);
618 | }
619 |
620 | if (extra_dist > particle_size) {
621 | continue;
622 | }
623 |
624 | vec3 uvw_pos = (local_pos / FRAME.colliders[i].extents) * 0.5 + 0.5;
625 | float s = texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos).r;
626 | s *= FRAME.colliders[i].scale;
627 | s += extra_dist;
628 | if (s <= particle_size + EPSILON) {
629 | col = true;
630 | depth = particle_size - s;
631 |
632 | normal = mat3(FRAME.colliders[i].transform) *
633 | normalize(
634 | vec3(
635 | texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos + vec3(EPSILON, 0.0, 0.0)).r - texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos - vec3(EPSILON, 0.0, 0.0)).r,
636 | texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos + vec3(0.0, EPSILON, 0.0)).r - texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos - vec3(0.0, EPSILON, 0.0)).r,
637 | texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos + vec3(0.0, 0.0, EPSILON)).r - texture(sampler3D(sdf_vec_textures[FRAME.colliders[i].texture_index], SAMPLER_LINEAR_CLAMP), uvw_pos - vec3(0.0, 0.0, EPSILON)).r));
638 | }
639 |
640 | } break;
641 | case COLLIDER_TYPE_HEIGHT_FIELD: {
642 | vec3 local_pos_bottom = local_pos;
643 | local_pos_bottom.y -= particle_size;
644 |
645 | if (any(greaterThan(abs(local_pos_bottom), FRAME.colliders[i].extents))) {
646 | continue;
647 | }
648 | const float DELTA = 1.0 / 8192.0;
649 |
650 | vec3 uvw_pos = vec3(local_pos_bottom / FRAME.colliders[i].extents) * 0.5 + 0.5;
651 |
652 | float y = texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uvw_pos.xz).r;
653 |
654 | if (y + EPSILON >= uvw_pos.y) {
655 |
656 |
657 | vec3 pos1 = (vec3(uvw_pos.x, y, uvw_pos.z) * 2.0 - 1.0) * FRAME.colliders[i].extents;
658 | vec3 pos2 = (vec3(uvw_pos.x + DELTA, texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uvw_pos.xz + vec2(DELTA, 0)).r, uvw_pos.z) * 2.0 - 1.0) * FRAME.colliders[i].extents;
659 | vec3 pos3 = (vec3(uvw_pos.x, texture(sampler2D(height_field_texture, SAMPLER_LINEAR_CLAMP), uvw_pos.xz + vec2(0, DELTA)).r, uvw_pos.z + DELTA) * 2.0 - 1.0) * FRAME.colliders[i].extents;
660 |
661 | normal = normalize(cross(pos1 - pos2, pos1 - pos3));
662 | float local_y = (vec3(local_pos / FRAME.colliders[i].extents) * 0.5 + 0.5).y;
663 |
664 | col = true;
665 | depth = dot(normal, pos1) - dot(normal, local_pos_bottom);
666 | }
667 |
668 | } break;
669 | }
670 |
671 | if (col) {
672 | if (!collided) {
673 | collided = true;
674 | collision_normal = normal;
675 | collision_depth = depth;
676 | } else {
677 | vec3 c = collision_normal * collision_depth;
678 | c += normal * max(0.0, depth - dot(normal, c));
679 | collision_normal = normalize(c);
680 | collision_depth = length(c);
681 | }
682 | }
683 | }
684 | }
685 | }
686 |
687 | if (particle_active) {
688 | {
689 | }
690 | }
691 |
692 | PARTICLE.flags &= ~PARTICLE_FLAG_ACTIVE;
693 | if (particle_active) {
694 | PARTICLE.flags |= PARTICLE_FLAG_ACTIVE;
695 | }
696 | }
697 |
698 |
servers/rendering/rendering_device.cpp:4304 - Parameter "pipeline" is null.
This compute pipeline requires (0) bytes of push constant data, supplied: (32)
No compute pipeline was set before attempting to draw.
***
The last three lines above repeat forever.
***
```
### Steps to reproduce
Set the Process Material to a GPUParticles3D to a ShaderMaterial, write in the start() function of the shader script the following:
```
void start() {
// Called when a particle is spawned.
MASS = 1.0;
TRANSFORM[3].xyz = vec3(0.0);
VELOCITY.x = 2.0;
}
```
### Minimal reproduction project (MRP)
[particle-shadermaterial.zip](https://github.com/user-attachments/files/18547694/particle-shadermaterial.zip) | bug,good first issue,topic:shaders | low | Critical |
2,811,155,648 | godot | Crash in Language Server (LSP) while game is running | ### Tested versions
4.3.1.rc.custom_build.90f21a35c
4.3.stable
### System information
Godot v4.3.1.rc (90f21a35c) - Arch Linux #1 SMP PREEMPT_DYNAMIC Sat, 18 Jan 2025 02:26:57 +0000 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 (nvidia; 565.77) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)
### Issue description
Godot periodically crashes while my game is running in the editor. The game itself keeps running, but the editor crashes and closes.
It's not obvious exactly what triggers this, but I have a LSP client attached, and the crash appears to be in the LSP code.
```
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x00007805ffdcd463 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#2 0x00007805ffd74120 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3 0x00007805ffd5b4c3 in __GI_abort () at abort.c:79
#4 0x000056edddc44dfb in handle_crash (sig=<optimized out>) at platform/linuxbsd/crash_handler_linuxbsd.cpp:145
#5 <signal handler called>
#6 0x000056ede20199c1 in Variant::reference (this=0x78059d9f9b70, p_variant=...) at core/variant/variant.cpp:1159
#7 0x000056ede0cc4b1c in Variant::Variant (this=0x78059d9f9b70, p_variant=...) at core/variant/variant.cpp:2922
#8 SceneState::instantiate (this=<optimized out>, p_edit_state=p_edit_state@entry=SceneState::GEN_EDIT_STATE_DISABLED) at scene/resources/packed_scene.cpp:357
#9 0x000056ede0cc9357 in PackedScene::instantiate (this=this@entry=0x56ee1f2609d0, p_edit_state=p_edit_state@entry=PackedScene::GEN_EDIT_STATE_DISABLED) at ./core/object/ref_counted.h:104
#10 0x000056ede0cc4d2d in SceneState::instantiate (this=<optimized out>, p_edit_state=p_edit_state@entry=SceneState::GEN_EDIT_STATE_DISABLED) at scene/resources/packed_scene.cpp:232
#11 0x000056ede0cc9357 in PackedScene::instantiate (this=0x56ee2048d1c0, p_edit_state=PackedScene::GEN_EDIT_STATE_DISABLED) at ./core/object/ref_counted.h:104
#12 0x000056edde082b10 in GDScriptWorkspace::_get_owner_scene_node (this=0x56ee11f66740, p_path=...) at modules/gdscript/language_server/gdscript_workspace.cpp:627
#13 GDScriptWorkspace::completion (this=0x56ee11f66740, p_params=..., r_options=0x78059d9fa130) at modules/gdscript/language_server/gdscript_workspace.cpp:641
#14 GDScriptTextDocument::completion (this=<optimized out>, p_params=...) at modules/gdscript/language_server/gdscript_text_document.cpp:182
#15 0x000056edde0e6eb7 in call_with_variant_args_ret_helper<__UnexistingClass, Array, Dictionary const&, 0ul> (p_instance=<optimized out>, p_method=<optimized out>, p_args=<synthetic pointer>, r_ret=..., r_error=...) at ./core/variant/binder_common.h:756
#16 call_with_variant_args_ret_dv<__UnexistingClass, Array, Dictionary const&> (p_instance=<optimized out>, p_method=<optimized out>, p_args=<optimized out>, p_argcount=<optimized out>, r_ret=..., r_error=..., default_values=...) at ./core/variant/binder_common.h:535
#17 MethodBindTR<Array, Dictionary const&>::call (this=<optimized out>, p_object=<optimized out>, p_args=<optimized out>, p_arg_count=<optimized out>, r_error=...) at ./core/object/method_bind.h:524
#18 0x000056ede22489d6 in Object::callp (this=0x56ee169a3820, p_method=..., p_args=<optimized out>, p_argcount=<optimized out>, r_error=...) at core/object/object.cpp:811
#19 0x000056ede2226dd1 in Object::callv (this=0x56ee169a3820, p_method=..., p_args=...) at core/object/object.cpp:749
#20 0x000056edde3b2b17 in JSONRPC::process_action (this=this@entry=0x56ee169a3018, p_action=..., p_process_arr_elements=p_process_arr_elements@entry=true) at modules/jsonrpc/jsonrpc.cpp:130
#21 0x000056edde3b37bc in JSONRPC::process_string (this=0x56ee169a3018, p_input=...) at modules/jsonrpc/jsonrpc.cpp:162
#22 0x000056edde02b1d0 in GDScriptLanguageProtocol::process_message (this=<optimized out>, p_text=...) at modules/gdscript/language_server/gdscript_language_protocol.cpp:143
#23 GDScriptLanguageProtocol::LSPeer::handle_data (this=0x78057000af50) at modules/gdscript/language_server/gdscript_language_protocol.cpp:98
#24 GDScriptLanguageProtocol::poll (this=this@entry=0x56ee169a3018, p_limit_usec=<optimized out>) at modules/gdscript/language_server/gdscript_language_protocol.cpp:252
#25 0x000056edde02b760 in GDScriptLanguageServer::thread_main (p_userdata=0x56ee169a29c0) at modules/gdscript/language_server/gdscript_language_server.cpp:88
#26 0x000056ede1d0ae5d in Thread::callback (p_caller_id=<optimized out>, p_settings=..., p_callback=0x56edde02b700 <GDScriptLanguageServer::thread_main(void*)>, p_userdata=0x56ee169a29c0) at core/os/thread.cpp:64
#27 0x000056edddbb7264 in execute_native_thread_routine ()
#28 0x00007805ffdcb39d in start_thread (arg=<optimized out>) at pthread_create.c:447
#29 0x00007805ffe5049c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
```
It appears to have something to do with setting a variant to a Transform3D?
```
(gdb) frame 6
#6 0x000056ede20199c1 in Variant::reference (this=0x78059d9f9b70, p_variant=...) at core/variant/variant.cpp:1159
1159 memnew_placement(_data._transform3d, Transform3D(*p_variant._data._transform3d));
(gdb) l
1154 _data._basis = (Basis *)Pools::_bucket_medium.alloc();
1155 memnew_placement(_data._basis, Basis(*p_variant._data._basis));
1156 } break;
1157 case TRANSFORM3D: {
1158 _data._transform3d = (Transform3D *)Pools::_bucket_medium.alloc();
1159 memnew_placement(_data._transform3d, Transform3D(*p_variant._data._transform3d));
1160 } break;
1161 case PROJECTION: {
1162 _data._projection = (Projection *)Pools::_bucket_large.alloc();
1163 memnew_placement(_data._projection, Projection(*p_variant._data._projection));
(gdb) p p_variant
$4 = (const Variant &) @0x56ee2343e520: {type = Variant::TRANSFORM3D, _data = {_bool = false, _int = 0, _float = 0, _transform2d = 0x0, _aabb = 0x0, _basis = 0x0, _transform3d = 0x0, _projection = 0x0, packed_array = 0x0, _ptr = 0x0, _mem = '\000' <repeats 15 times>}}
(gdb) p _data
$5 = {_bool = 144, _int = 131967152792464, _float = 6.5200436574239189e-310, _transform2d = 0x7805ff43a390, _aabb = 0x7805ff43a390, _basis = 0x7805ff43a390, _transform3d = 0x7805ff43a390, _projection = 0x7805ff43a390, packed_array = 0x7805ff43a390, _ptr = 0x7805ff43a390,
_mem = "\220\243C\377\005x\000\000\000\000\000\000\000\000\000"}
```
### Steps to reproduce
1. Open a godot project
2. Open an editor with a LSP client
3. Launch the game
4. Play the game for a bit
5. The editor crashes
### Minimal reproduction project (MRP)
I don't have a minimal project, but here's the one I've reproed in many times:
https://github.com/rcorre/zambus | bug,topic:gdscript,topic:editor,crash | low | Critical |
2,811,155,766 | electron | /dev/shm fills up when using net.request | ### 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
34.0.1
### What operating system(s) are you using?
Ubuntu, Other Linux
### Operating System Version
Ubuntu 6.8.0-51
### What arch are you using?
x64
### Last Known Working Electron version
Unknown
### Expected Behavior
Memory usage to remain normal
### Actual Behavior
I was using `net.request` to perform an availability check, this appears to run normally on MacOS and Windows, however on Linux when using the default mechanism `/dev/shm`, it continually fills up. Using the flag `app.commandLine.appendSwitch('disable-dev-shm-usage', true);` appears to resolve it (though is just pushing the cache to disk).
I found a reference to this [here](https://github.com/electron/electron/issues/40711) but it seems it was closed. I have resolved it by using a different module but just for your awareness.
### Testcase Gist URL
_No response_
### Additional Information
_No response_ | platform/linux,bug :beetle:,component/net,memory leak,34-x-y,35-x-y | low | Critical |
2,811,157,549 | godot | Navigation map synchronization error | ### Tested versions
- Reproductible with Godot 4.3 and all 4.4 rc/beta versions
### System information
macOS 15.2 - Apple M3 PRO
### Issue description
I'm using navigation on a 2D game
When baking navigation and launching game, error log produces the following error message but navigation agents work correctly
```
E 0:00:01:0730 _build_step_find_edge_connection_pairs: Navigation map synchronization error. Attempted to merge a navigation mesh polygon edge with another already-merged edge. This is usually caused by crossing edges, overlapping polygons, or a mismatch of the NavigationMesh / NavigationPolygon baked 'cell_size' and navigation map 'cell_size'. If you're certain none of above is the case, change 'navigation/3d/merge_rasterizer_cell_scale' to 0.001.
<C++ Source> modules/navigation/3d/nav_map_builder_3d.cpp:151 @ _build_step_find_edge_connection_pairs()
```
The error disappears if I remove the big tree alone on the map.
Trees are on a dedicated tilemaplayer
It seems the collision shape of some tileset tiles influence the error (the small trees do not trigger the error)
What I checked:
- navigation server polygon cell size = 1, same value as NavigationServer2D.map_get_cell_size(navigation_agent.get_navigation_map())
- enable/disable "Use Edge Connections"
- error code refers to method void NavMapBuilder3D::_build_step_find_edge_connection_pairs on GitHub related to 3D (?)
I did not find any issue or help somewhere concerning this error.
### Steps to reproduce
I cannot give more information
### Minimal reproduction project (MRP)
I don't have a minimal project, I don't know if the error is related to my game (I guess so, but I have no clue where to look after all the tests I did) | needs testing,topic:navigation | low | Critical |
2,811,158,117 | next.js | `Link` component is buggy when used in app router | ### Link to the code that reproduces this issue
https://github.com/mehulmpt/nextjs-app-router-link-bug
### To Reproduce
1. Clone the GitHub repository
2. Run `npm run bugcheck` command in your terminal
3. Visit `http://localhost:3000`
### Current vs. Expected behavior
Current behavior:
The links rightly point to `/link?productid=1` / `/link?productid=2` ... and so on. However, when you click on it, they redirect you to the wrong page!
Expected behavior:
Redirect works properly
### Provide environment information
```bash
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
Available memory (MB): 16384
Available CPU cores: 8
Binaries:
Node: 18.20.4
npm: 8.19.2
Yarn: 1.22.19
pnpm: 8.7.6
Relevant Packages:
next: 15.1.3 // There is a newer version (15.1.6) available, upgrade recommended!
eslint-config-next: N/A
react: 19.0.0
react-dom: 19.0.0
typescript: 5.7.3
Next.js Config:
output: export
```
### Which area(s) are affected? (Select all that apply)
Navigation
### Which stage(s) are affected? (Select all that apply)
Other (Deployed), Vercel (Deployed), next start (local)
### Additional context
I spent 20 minutes debugging this for one of our clients today and finally figured out this is a bug with Next.js itself. The reproduction code above is extremely minimal and does not include anything else other than the required code.
The behavior is very weird, the link shown is correct in the browser preview on the bottom left but the moment it is clicked, it takes you to the wrong page. I am also attaching the video that showcases it:
- In the first half of the video I show you wrong behavior
- In the second half of the video I disable javascript and show you how it should actually work
https://github.com/user-attachments/assets/d64a0fe2-57bf-4d5d-b081-faa5220b7cee | Link (next/link) | low | Critical |
2,811,164,033 | svelte | Clarify status of class:directive | ### Describe the bug
Currently, the [docs on svelte class directive](https://svelte.dev/docs/svelte/class#The-class:-directive) state:
> Unless you’re using an older version of Svelte, consider avoiding `class:`, since the attribute is more powerful and composable.
Upon [requesting the `cli` maintainers to work on a migration script](https://github.com/sveltejs/cli/issues/393), the svelte team member said that perhaps the docs is pushing the new syntax a bit too much and may require clarification.
As I do not have the data or heuristics to know if and when there is noticeable differences in performance or DevEx, it seems best for a maintainer to edit the docs in one or two sentences to clarify the future of class:directives, performance gains/losses, and whether this is opt-in or the new norm.
A starting point could be
> You can opt-in to the more powerful and composable attribute syntax above. There is currently no plan to deprecate the directive syntax.
### Reproduction
N/A
### Logs
```shell
```
### System Info
```shell
N/A
```
### Severity
annoyance | documentation | low | Critical |
2,811,166,655 | angular | Provide better type safety for viewChild (and viewChildren) | ### Which @angular/* package(s) are relevant/related to the feature request?
core
### Description
At the moment, it is easy to incorrectly type a `viewChild()` (or `viewChildren()`) signal. For example:
```
readonly myElement = viewChild<HTMLInputElement>('someSelector');
```
Here I am passing a generic argument, HTMLInputElement, but the element may have a different type. Often I forget to wrap the element within an `ElementRef`, as I did here, but I digress. The point is, I often waste time being unsure of what is actually being injected by Angular in the component class.
### Proposed solution
I believe that the easiest solution would be to include some kind of validator function:
```
readonly myElement = viewChild('someSelector', { validator: e => e instanceof HTMLInputElement });
```
Type signature would be as follows:
```
<T>(selector: string, options: { validator: (el: unknown) => el is T }) : Signal<T>;
```
### Alternatives considered
**Alternative 1:**
The current API is not as ergonomic as it could be. Why can't the Angular Language service ensure that `myElement` is of the correct type:
```
readonly myElement: HTMLElement;
```
... and in the template:
```
<input #myElement /> <!-- throw error here (if not of type HTMLElement) -->
```
**Alternative 2:**
I thought about creating an external utility function that wraps the existing functionality but does an additional type check when the signal is invoked. I was unsuccessful. Perhaps you could tell me how to facilitate this. | area: core,core: queries | low | Critical |
2,811,167,902 | tauri | [breaking] Remove v1Compatible | Opening an issue for this because it was planned for v3 but may be pushed back to v4. Ref https://discord.com/channels/616186924390023171/731495028677148753/1332806348664209490
Edit: We should also update the deprecation warnings if we end up pushing it back. | type: breaking change | low | Minor |
2,811,176,273 | flutter | [Text Selection] Cannot select consecutive emojis when starting from one, and selection may stop unexpectedly with emojis. | ### Steps to reproduce
To reproduce the issue, please use the sample code from [this GitHub comment](https://github.com/flutter/flutter/issues/162197#issuecomment-2613746878), alongside the flow demonstrated in the attached videos. Tested on iphone 13pro iOS 17.4.1.
The issue occurs when the user types a few emojis and then starts selecting from one of the emojis. The selection tool quits unexpectedly, preventing the user from dragging to select multiple emojis.
https://github.com/user-attachments/assets/f8000041-5fa8-4624-adbc-e88e31ddc48c
Similar issue occur when user select an initial text placed after emojis and move handler to the left, the selection quits.
https://github.com/user-attachments/assets/8b30d033-c7ae-4e71-8ae9-83c184c561bf
### Expected results
User should be able to select a single emoji or more emoji starting the selection from one emoji or text after emojis.
### Actual results
User cannot select emojis when starting the selection from one emoji and selection quits unexpectedly with emojis if user start selection on text and emojis get selected, especially from right to left side.
### Code sample
<details open><summary>Code sample</summary>
```dart
The code from this issue can be used for testing.
https://github.com/flutter/flutter/issues/162197#issuecomment-2613746878
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[!] Flutter (Channel [user-branch], 3.24.5, on macOS 14.2.1 23C71 darwin-arm64, locale en-IT)
! Flutter version 3.24.5 on channel [user-branch] at /Users/delfme/Development/flutter
Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
! Upstream repository unknown source is not a standard remote.
Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] Connected device (4 available)
! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area
network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources
```
</details>
| in triage | low | Critical |
2,811,178,258 | godot | StyleBox inconsistencies - referred to as both "style_box" and "stylebox" | ### Tested versions
All
### System information
N/A
### Issue description
To start I'll show this single line:
```cpp
draw_style_box(get_theme_stylebox(SN_STYLEBOX_PLUS), plus_rect);
```
Here you can see in `draw_style_box` the StyleBox is referred to as `style_box` while in `get_theme_stylebox` it is `stylebox`, missing an underscore.
In some places, variables that use StyleBox call it `style_box` while others call it `stylebox`. The class StyleBox has Box uppercase, so I think `style_box` makes more sense.
This isn't a major issue, this is just a thing I noticed that could be adjusted later for consistency. (or rename & deprecate functions or something)
### Steps to reproduce
N/A
### Minimal reproduction project (MRP)
N/A | discussion,topic:gui,topic:codestyle | low | Minor |
2,811,182,835 | rust | Suggest `{to,from}_ne_bytes` when people use transmute between arrays and integers | ### Code
```Rust
fn bytes_at_home_1(a: [u8; 4]) -> u32 {
unsafe { std::mem::transmute(a) }
}
fn bytes_at_home_2(x: u32) -> [u8; 4] {
unsafe { std::mem::transmute(x) }
}
```
### Current output
```Shell
(no warnings)
```
### Desired output
```text
Warning: use the safe alternative instead
|
| unsafe { std::mem::transmute(a) }
| ^^^^^^^^^^^^^^^^^^^ This can be done with `u32::from_ne_bytes(a)` instead
|
hint: there's also `from_le_bytes` and `from_ne_bytes` if you expect a particular byte order
Warning: use the safe alternative instead
|
| unsafe { std::mem::transmute(x) }
| ^^^^^^^^^^^^^^^^^^^ This can be done with `x.to_ne_bytes()` instead
|
hint: there's also `to_le_bytes` and `to_ne_bytes` if you expect a particular byte order
```
### Rationale and extra context
I see people doing this a bunch, like it just came up [in Discord](https://discord.com/channels/273534239310479360/592856094527848449/1332818871920492594).
It would be nice to point them to the safe alternative when possible.
### Other cases
```Rust
```
### Rust Version
```Shell
Playground nightly ⬇
```
### Anything else?
<https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=a89dfdaa49736b9d106b2099ca48ddd7>
<!-- TRIAGEBOT_START -->
<!-- TRIAGEBOT_ASSIGN_START -->
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"bend-n"}$$TRIAGEBOT_ASSIGN_DATA_END -->
<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END --> | A-diagnostics,T-compiler | low | Critical |
2,811,193,976 | langchain | abatch_as_completed does not respect max_concurrency config the same way that abatch does | ### Checked other resources
- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).
### Example Code
Test code illustrating the issue:
```python
import asyncio
import time
from langchain_core.runnables import RunnableConfig, RunnableLambda
async def test_concurrency():
# Track currently running tasks
running_tasks = 0
max_running_tasks = 0
lock = asyncio.Lock()
async def tracked_function(x):
nonlocal running_tasks, max_running_tasks
async with lock:
running_tasks += 1
max_running_tasks = max(max_running_tasks, running_tasks)
print(f"Starting task. Current running: {running_tasks}")
# Simulate some work
await asyncio.sleep(1)
async with lock:
running_tasks -= 1
print(f"Finishing task. Current running: {running_tasks}")
return f"Completed {x}"
# Create runnable
runnable = RunnableLambda(tracked_function)
# Test parameters
num_tasks = 10
max_concurrency = 3
# Test abatch_as_completed
print(f"\nTesting abatch_as_completed with max_concurrency={max_concurrency}...")
start_time = time.time()
config = RunnableConfig(max_concurrency=max_concurrency)
results = []
async for idx, result in runnable.abatch_as_completed(
range(num_tasks), config=config
):
print(f"Got result {idx}: {result}")
results.append(result)
end_time = time.time()
print("\nResults for abatch_as_completed:")
print(f"Max concurrent tasks observed: {max_running_tasks}")
print(f"Expected max concurrent tasks: {max_concurrency}")
print(f"Total time: {end_time - start_time:.2f} seconds")
print(f"Number of results: {len(results)}")
# Reset counters
running_tasks = 0
max_running_tasks = 0
# Test abatch
print(f"\nTesting abatch with max_concurrency={max_concurrency}...")
start_time = time.time()
results = await runnable.abatch(range(num_tasks), config=config)
end_time = time.time()
print("\nResults for abatch:")
print(f"Max concurrent tasks observed: {max_running_tasks}")
print(f"Expected max concurrent tasks: {max_concurrency}")
print(f"Total time: {end_time - start_time:.2f} seconds")
print(f"Number of results: {len(results)}")
# Run the test
if __name__ == "__main__":
asyncio.run(test_concurrency())
```
### Error Message and Stack Trace (if applicable)
I expect the results for both abatch and abatch_as_completed to show that only 3 concurrent tasks are observed at any one time. Instead, for abatch_as_completed it shows all 10 tasks running at the same time. Results:
```
Testing abatch_as_completed with max_concurrency=3...
Starting task. Current running: 1
Starting task. Current running: 2
Starting task. Current running: 3
Starting task. Current running: 4
Starting task. Current running: 5
Starting task. Current running: 6
Starting task. Current running: 7
Starting task. Current running: 8
Starting task. Current running: 9
Starting task. Current running: 10
Finishing task. Current running: 9
Finishing task. Current running: 8
Finishing task. Current running: 7
Finishing task. Current running: 6
Finishing task. Current running: 5
Finishing task. Current running: 4
Finishing task. Current running: 3
Finishing task. Current running: 2
Finishing task. Current running: 1
Finishing task. Current running: 0
Got result 7: Completed 7
Got result 9: Completed 9
Got result 0: Completed 0
Got result 2: Completed 2
Got result 4: Completed 4
Got result 6: Completed 6
Got result 8: Completed 8
Got result 1: Completed 1
Got result 3: Completed 3
Got result 5: Completed 5
Results for abatch_as_completed:
Max concurrent tasks observed: 10
Expected max concurrent tasks: 3
Total time: 1.08 seconds
Number of results: 10
Testing abatch with max_concurrency=3...
Starting task. Current running: 1
Starting task. Current running: 2
Starting task. Current running: 3
Finishing task. Current running: 2
Finishing task. Current running: 1
Finishing task. Current running: 0
Starting task. Current running: 1
Starting task. Current running: 2
Starting task. Current running: 3
Finishing task. Current running: 2
Finishing task. Current running: 1
Finishing task. Current running: 0
Starting task. Current running: 1
Starting task. Current running: 2
Starting task. Current running: 3
Finishing task. Current running: 2
Finishing task. Current running: 1
Finishing task. Current running: 0
Starting task. Current running: 1
Finishing task. Current running: 0
Results for abatch:
Max concurrent tasks observed: 3
Expected max concurrent tasks: 3
Total time: 4.02 seconds
Number of results: 10```
### Description
* I'm trying to use abatch_as_completed on a Runnable but limit the max number of concurrently running tasks.
* I expect the "max_concurrency" config value to effectively limit this, and it appears it indeed has this behavior with abatch.
* When I try it with abatch_as_completed, it appears all of the tasks are started concurrently, ignoring the "max_concurrency" limit I specify.
### System Info
(.venv) keenanpepper@mac langchain-goodfire % python -m langchain_core.sys_info
System Information
------------------
> OS: Darwin
> OS Version: Darwin Kernel Version 24.2.0: Fri Dec 6 19:03:40 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041
> Python Version: 3.12.8 (main, Dec 3 2024, 18:42:41) [Clang 16.0.0 (clang-1600.0.26.4)]
Package Information
-------------------
> langchain_core: 0.3.31
> langchain: 0.3.15
> langchain_community: 0.3.15
> langsmith: 0.3.1
> langchain_anthropic: 0.3.4
> langchain_openai: 0.3.2
> langchain_text_splitters: 0.3.5
Optional packages not installed
-------------------------------
> langserve
Other Dependencies
------------------
> aiohttp: 3.11.11
> anthropic: 0.45.0
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> defusedxml: 0.7.1
> httpx: 0.27.2
> httpx-sse: 0.4.0
> jsonpatch: 1.33
> langsmith-pyo3: Installed. No version info available.
> numpy: 2.2.2
> openai: 1.60.1
> orjson: 3.10.15
> packaging: 24.2
> pydantic: 2.10.6
> pydantic-settings: 2.7.1
> pytest: Installed. No version info available.
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> rich: Installed. No version info available.
> SQLAlchemy: 2.0.37
> tenacity: 9.0.0
> tiktoken: 0.8.0
> typing-extensions: 4.12.2
> zstandard: 0.23.0 | 🤖:bug | low | Critical |
2,811,195,168 | vscode | Co pilote pro |
Type: <b>Bug</b>
Bonjour ,
J'utilise co-pilote pro , et j'ai le message comme quoi j'ai atteint le maximum de message et qu'il faut que j'upgrade pour co-pilote pro , sauf que je l'ai deja je comprend pas trop
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12700H (20 x 2688)|
|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.64GB (4.98GB free)|
|Process Argv|C:\\Users\\jorda\\Desktop\\Serveur GTA\\Radiance V\\resources\\[dev2]\\radiance_permis --crash-reporter-id fe697b13-1dd6-4730-9124-2b66f3333435|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (26)</summary>
Extension|Author (truncated)|Version
---|---|---
nodejs-bundle|1Yi|1.0.0
svelte-bundle|1Yi|1.0.0
svelte-intellisense|ard|0.7.1
dart-code|Dar|3.102.0
flutter|Dar|3.102.0
fivem-lua|dha|1.0.1
vscode-html-css|ecm|2.0.13
fivem-esx-snippets|eth|1.5.0
fivem-vscode|fiv|0.3.3
vscode-svelte-snippets|fiv|0.5.0
copilot|Git|1.259.0
copilot-chat|Git|0.23.2
svg|joc|1.5.4
vscode-language-pack-fr|MS-|1.96.2024121109
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
cfxlua-vscode|ove|1.7.32
roo-cline|Roo|3.3.1
vs-code-prettier-eslint|rve|6.0.0
claude-dev|sao|3.2.5
html5-boilerplate|sid|1.1.1
vscode-standard|sta|2.1.3
lua|sum|3.13.5
svelte-vscode|sve|109.5.2
vscode-surround|yat|1.5.0
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
9064b325:31222308
copilot_t_ci:31222730
```
</details>
<!-- generated by issue reporter --> | info-needed,*english-please,translation-required-french | low | Critical |
2,811,199,286 | godot | Embedded Game window stops rendering when editing other nodes in the editor | ### Tested versions
Differences between Godot 4.3 and the new embedded game window feature in Godot 4.4
### System information
Godot v4.4.beta1 - Ubuntu 22.04.5 LTS 22.04 on X11 - X11 display driver, Multi-window, 2 monitors - OpenGL 3 (Compatibility) - AMD Radeon RX 6600 (navi23, LLVM 15.0.7, DRM 3.57, 6.8.0-51-generic) - AMD Ryzen 7 5700X 8-Core Processor (16 threads)
### Issue description
Godot4.3 works great already for gaming while editing it at the same time. I run the game, and then 'windows key + tab' over to the editor to make changes and see it in real time. I was curious if the embedded game window would make this even better somehow but certain what the added functionality would be.
In Godot 4.4 beta, when running the game, it pops up in the new window, on my second screen. If i tab over to the editor to make a change to any nodes, it detects i'm now looking at a specific object , or script, and not the game anymore and so stops rendering the game in the second window. This is very frustrating. I'd normally pop over to the editor to adjust a Directional Light, or Environment Fog, and see it in real time in the game, but the embeded view stops rendering so now i have to tweak, and then tab back, and tweak and tab back. And it's a lot more work to see changes in real time.
I can't seem to find a settting to have it 'always on' even when not on that tab, or revert back to a classic mode or something.
EDIT:
Aha! So these are the settings to go back to a classic mode. The wording on both is a little odd. Since Embed and Docked can have similar meanings and these two settings next to each other aren't clear because of it. I was going to close the ticket but instead i'll edit it to reflect the wording issue, and that when floating the game workspace, it should keep rendering even when editing other things. That's seems the whole reason to make it a floating window no?
So wording wise:
Enabling a bool for "_Make Game Floating on next play_" is the most curious to me. I'd think this wording better:
"_Dock Game Window_" (Enable the bool to dock, and disable to make floating, inverse of what is current here)
And the other setting "Embed Game on next play" add confusion since embed and dock have similar ideas. I was unsure what it meant since it sounds like docking/floating, the window and isn't clear it means it's going to actually enable or disabled in-editor game workspace.
Perhaps better wording there too:
"_Enable in-editor game workspace_" (disable to run externally)
### Steps to reproduce
I start any game running using the "embeded game on next play" and "make floating" settings enabled.
See it running on your second monitor
Tab back over to the editor.
See the game stop rendering the second you go to edit anything.
Click back to the game and see it come back.
### Minimal reproduction project (MRP)
Load a project.
Start the game
Move the game to a second scree or even just split your screen into section.
Click on any node in the editor. the game stops rendering, swaps to 3D, Script, 2D etc, tabs, and you can't make realtime edits and see them in game. | bug,platform:linuxbsd,topic:editor,usability,regression | low | Minor |
2,811,202,013 | vscode | The `cwd` cannot be resolved in a multi folder workspace. Solution: "cwd" : "${Workspacefolder.name}" | <!-- ⚠️⚠️ 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/No
<!-- 🪓 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.4
- OS Version: Windows 10
Steps to Reproduce:
1. idk i just started using vscode
2.
| info-needed | low | Critical |
2,811,202,155 | PowerToys | Window Centering Helper | ### Description of the new feature / enhancement
There is a Window Centering Helper program, add its PowerToys functionality.
### Scenario when this would be used?
There is a Window Centering Helper program, add its PowerToys functionality.
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,811,207,826 | react-native | App freezes on startup after adding custom native module | ### Description
After adding a custom native module to my React Native app, the app freezes on startup and never loads the main screen. I followed the documentation for creating a native module and linked it properly, but after that, the app simply hangs on the splash screen and does not proceed.
I’ve tried cleaning the build, resetting the cache, and running the app on different devices, but the issue persists.
Expected Behavior:
The app should start normally and load the main screen even after adding the custom native module.
Steps to Reproduce:
Create a custom native module following the official React Native documentation.
Link the native module (manually or via auto-linking).
Run the app on either an Android or iOS device using react-native run-android or react-native run-ios.
Observe the app freezing on the splash screen with no further progress.
Environment:
React Native version: (Not mentioned)
Node.js version: 16.x
npm or yarn version: npm 8.x
Operating System: macOS Big Sur
Device: iPhone 13 (iOS) / Samsung Galaxy S21 (Android)
Logs:
2025-01-25 12:34:56.789 MyApp[1234:56789] App launched
2025-01-25 12:34:57.001 MyApp[1234:56789] NativeModule: MyCustomModule initialization failed
2025-01-25 12:34:57.099 MyApp[1234:56789] App is freezing on splash screen, no further logs.
Additional Context:
I’m using a custom native module to interact with a third-party SDK.
The issue happens on both Android and iOS devices.
I’ve checked the Android logs, and the ReactContext for the module seems to be null at the time of initialization.
The app works fine when the custom module is removed.
Possible Solution (if applicable):
I’m unsure what the exact cause might be. Could this be an issue with how the native module is initialized or linked? Any ideas on how to debug further or a potential solution to this freezing problem would be greatly appreciated!
### Steps to reproduce
Create a new React Native project:
npx react-native init MyApp
Navigate to the project directory:
cd MyApp
Install a custom native module (e.g., a module to integrate with a third-party SDK):
npm install react-native-custom-sdk
Link the custom native module (if manual linking is required):
npx react-native link react-native-custom-sdk
Modify the Android native code (e.g., add required permissions or SDK initialization):
Open android/app/src/main/java/com/myapp/MainActivity.java
Add necessary import and initialization code for the custom SDK.
Update App.js to use the native module:
Import and call functions from the native module inside App.js.
Build and run the app on an Android device:
npx react-native run-android
Observe the crash: The app will freeze or crash on startup with a "NativeModule: null" error or similar issue.
Clear cache and rebuild (if applicable):
npx react-native start --reset-cache
Re-run the app:
npx react-native run-android
Confirm issue persists: The app should still freeze or fail to load correctly.
### React Native Version
0.77.0
### Affected Platforms
Runtime - iOS
### Output of `npx react-native info`
```text
React Native Environment Info:
System:
OS: macOS 12.5.1
CPU: (8) arm64 Apple M1
Memory: 16 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.14.2 - /usr/local/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 8.3.1 - /usr/local/bin/npm
Watchman: 2021.08.02.00 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 15.2, macOS 12.1, tvOS 15.2
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Android SDK:
API Levels: 30, 29, 28
Build Tools: 30.0.3, 29.0.3
Platform Tools: 31.0.3
Android NDK: 23.1.7779620
IDEs:
Xcode: 13.2.1 - /usr/bin/xcodebuild
Android Studio: 2021.1.1.25 - /Applications/Android Studio.app/Contents
Languages:
Java: 11.0.9.1 - /usr/bin/javac
Kotlin: 1.5.30 - /usr/local/bin/kotlinc
Python: 3.9.7 - /usr/bin/python3
npmPackages:
react: 18.0.0 - node_modules/react
react-native: 0.67.2 - node_modules/react-native
Expo:
SDK: N/A
Installed Android Emulators:
Pixel_3_API_30: Android 10 (API 30) - emulator
Pixel_4_API_31: Android 11 (API 31) - emulator
```
### Stacktrace or Logs
```text
2025-01-25 12:34:56.789 MyApp[1234:56789] App launched
2025-01-25 12:34:56.890 MyApp[1234:56789] React Native: Starting up...
2025-01-25 12:34:56.999 MyApp[1234:56789] NativeModule: CustomSDK initialization failed
2025-01-25 12:34:57.123 MyApp[1234:56789] Error: Attempt to invoke virtual method 'com.reactlibrary.CustomSDK.getReactApplicationContext()' on a null object reference
at com.myapp.MainActivity.onCreate(MainActivity.java:45)
at android.app.Activity.performCreate(Activity.java:8024)
at android.app.Activity.performCreate(Activity.java:8014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3543)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3717)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2126)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:246)
at android.app.ActivityThread.main(ActivityThread.java:8637)
at java.lang.reflect.Method.invoke(Method.java:0)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1034)
```
### Reproducer
https://github.com/iaceene/react-native-custom-sdk-issue
### Screenshots and Videos
_No response_ | Needs: Author Feedback,Needs: Repro | low | Critical |
2,811,211,133 | pytorch | [Inductor-CPU] `add` is not being fused with templated int8 WoQ GEMM while running LLaMA2 | ### 🐛 Describe the bug
When max-autotune is enabled with Inductor-CPU, and when int8 WoQ GEMM is used with auto-tuning enabled, `add` isn't being fused with it.
So, there's an opportunity cost. i.e. For LLaMA, for BF16 dtype, with BF16 templated GEMM, we are even able to fuse `add` & RMSNorm's decomposed ops as epilogues.
But the same doesn't happen when the activation is BF16 & the weights are quantized to int8.
This issue is not reproducible with a simple UT, so will have to check the precise scenario in LLaMA2 to ascertain why the intended fusions are not happening.
cc @leslie-fang-intel @Guobing-Chen @chunyuan-w @jianan-gu
### Versions
Current main branch | oncall: cpu inductor | low | Critical |
2,811,251,234 | terminal | Allow opening cmd.exe as service user such as SYSTEM or LOCALSERVICE | ### Description of the new feature
currently I use `psexec -i -s cmd` or `pxexec -i -u "nt authority\localservice" cmd` to open a cmd as servcie account. But it opens a new cmd window and it will not have some of the customizations availble to the terminal. Such as For example `Ctrl+shift+F` to search.
### Proposed technical implementation details
_No response_ | Issue-Feature,Needs-Triage,Needs-Tag-Fix | low | Minor |
2,811,254,336 | go | cmd/compile: unnecessary bounds check when indexing slice from range | ### Go version
go1.23
### Output of `go env` in your module/workspace:
```shell
GOARCH=amd64
GOOS=linux
```
### What did you do?
Compile the following:
```go
package main
import "archive/tar"
var src []tar.Header
var dst *tar.Header
func main() {
for i := range src {
dst = &src[i] // line 10
}
}
```
### What did you see happen?
I see this compiled out:
```
...
0x0069 00105 (main.go:10) PCDATA $1, $0
0x0069 00105 (main.go:10) CALL runtime.panicIndex(SB)
0x006e 00110 (main.go:10) XCHGL AX, AX
...
```
### What did you expect to see?
No such call to `runtime.panicIndex`. The slice is indexed from an iteration integer that is provably bounded by the length of `src` itself. The only possible way a panic occurs is if `src` is mutated during the iteration (or asynchronously in another goroutine, in which case there must be synchronization primitives). | NeedsInvestigation,compiler/runtime,BugReport | low | Minor |
2,811,269,916 | node | `path.win32.isAbsolute` considers relative paths absolute | ### Version
22.11.0
### Platform
```text
Linux pc 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```
### Subsystem
_No response_
### What steps will reproduce the bug?
```
require('path').win32.isAbsolute('\\foo') === true
```
### How often does it reproduce? Is there a required condition?
Yes. No.
### What is the expected behavior? Why is that the expected behavior?
Here's a behavior of `cd` on `Windows`:
```
C:\Users\user> cd \Windows
C:\Windows>
```
`\Windows` is relative to drive name.
Expected output for `isAbsolute()` is false.
### What do you see instead?
`isAbsolute()` is true.
### Additional information
_No response_ | path | low | Critical |
2,811,278,439 | pytorch | AMD MI300A Unified Memory Support | ### 🚀 The feature, motivation and pitch
I am working on improving performance for LLM workloads on AMD Instinct™ MI300A Accelerator. This APU is equipped with a fully unified-memory architecture not taken advantage by PyTorch at this time. Because both the GPU and CPU share the same physical memory, memcpy ops become redundant and can limit the size of the model we can train. Adding support for unified memory on ROCm for that particular APU would allow for zero-copy operations.
The motivation is similar that of #140787, but for ROCm instead of MPS.
Given that this APU is targeted for the most demanding HPC ML workloads, there is a great interest in optimizing the performance of PyTorch for it. Notably, El Capitan, the top1 Supercomputer from [top500](https://top500.org/) runs exclusively with AMD's MI300A.
### Alternatives
_No response_
### Additional context
To facilitate understanding I provide more details as to the kind of changes this involves.
To understand the differences in operations between non-unified and unified memory, let us consider a regular matrix multiplication of matrices $A$ and $B$ where the result is stored in matrix $C$.
In a non-unified setup with a discrete GPU (device):
1. `malloc` matrices $A,B,C$ on the host each of size $n \times n$.
2. ... values are written on matrices $A$,$B$
3. `CudaMalloc` to allocate memory for matrices $A',B',C'$
4. `CudaMemcpy` $A \rightarrow A'$, and $B \rightarrow B'$ (`hostToDevice`)
5. Kernel launch (results are written in $C'$).
6. `CudaMemcpy` $C' \rightarrow C$ (`DeviceToHost`) to get back the results
Whereas with unified-memory you would have:
1. `CudaMallocManaged` matrices $A,B,C$ on the host each of size $n \times n$.
2. ... values are written on matrices $A$,$B$
5. Kernel launch (results are written in $C$).
On machines with discrete GPUs the concept of unified-memory is purely virtual and still results in memory movement by way of page faults and page migrations. This adds a lot of overhead.
On architectures where CPU and GPU share the same physical memory such as the MAC, AMD MI300A, any memcpy operation becomes pointless and wastes space and time.
The quickest and dirtiest *hack* for the support of unified memory on Pytorch is to replace all `cudaMalloc` by `cudaMallocManaged` and to get rid of `memCopy` operations. [Like in this paper](https://doi.org/10.1109/ACSOS-C52956.2021.00029). This however is not ideal, nor portable.
Perhaps a better way to do it would be to toggle on or off the unified memory. Given that this is a relatively new architecture, more hardware is likely to come out with such configuration from different manufacturers and so it would be great to have a device-agnostic support of unified memory.
cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd | module: rocm | low | Major |
2,811,283,359 | flutter | Cannot add Flutter to existing Android app, Gradle fails to resolve dependencies ("module source code" option) | ### Steps to reproduce
I'm experimenting with Flutter's add-to-app feature. I have [an existing Jetpack Compose app ](https://github.com/kacaleksandra/notes) and I want to add a new FlutterActivity to it. I follow [this guide](https://docs.flutter.dev/add-to-app/android/project-setup), [here is the PR](https://github.com/kacaleksandra/notes/pull/25).
To reproduce:
1. Clone the repository, switch to the `embed_flutter` branch
2. `cd mobile`
3. `./gradlew :app:assembleDebug`
### Expected results
I expect the app to be built.
### Actual results
I get a dependency resolution failure (see logs).
### Code sample
Available in a separate repo on a branch: https://github.com/kacaleksandra/notes/pull/25
### Screenshots or Video
n/a
### Logs
<details open><summary>Logs</summary>
```console
$ ./gradlew :app:assembleDebug
> Configure project :flutter
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by plugin 'dev.flutter.flutter-gradle-plugin'
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by plugin 'dev.flutter.flutter-gradle-plugin'
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by plugin 'dev.flutter.flutter-gradle-plugin'
> Task :app:checkDebugAarMetadata FAILED
[Incubating] Problems report is available at: file:///Users/bartek/projects/notes/mobile/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
> Could not find io.flutter:flutter_embedding_debug:1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/io/flutter/flutter_embedding_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/flutter_embedding_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
- https://repo.maven.apache.org/maven2/io/flutter/flutter_embedding_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/flutter_embedding_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
Required by:
project :app > project :flutter
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
> Could not find io.flutter:armeabi_v7a_debug:1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/io/flutter/armeabi_v7a_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/armeabi_v7a_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
- https://repo.maven.apache.org/maven2/io/flutter/armeabi_v7a_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/armeabi_v7a_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
Required by:
project :app > project :flutter
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
> Could not find io.flutter:arm64_v8a_debug:1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/io/flutter/arm64_v8a_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/arm64_v8a_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
- https://repo.maven.apache.org/maven2/io/flutter/arm64_v8a_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/arm64_v8a_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
Required by:
project :app > project :flutter
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
> Could not find io.flutter:x86_64_debug:1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/io/flutter/x86_64_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/x86_64_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
- https://repo.maven.apache.org/maven2/io/flutter/x86_64_debug/1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b/x86_64_debug-1.0.0-e672b006cb34c921db85b8e2f482ed3144a4574b.pom
Required by:
project :app > project :flutter
* Try:
> The project declares repositories, effectively ignoring the repositories you have declared in the settings.
To determine how project repositories are declared, configure your build to fail on project repositories.
For more information, please refer to https://docs.gradle.org/8.12/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories in the Gradle documentation.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.12/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 10s
8 actionable tasks: 4 executed, 4 up-to-dat
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.27.3, on macOS 15.2 24C101 darwin-arm64, locale en-US)
• Flutter version 3.27.3 on channel stable at /Users/bartek/.cache/fvm/versions/3.27.3
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (4 days ago), 2025-01-21 10:32:23 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
• Android SDK at /Users/bartek/androidsdk
• Platform android-35, build-tools 35.0.0
• ANDROID_HOME = /Users/bartek/androidsdk
• Java binary at: /Library/Java/JavaVirtualMachines/openjdk.jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment Homebrew (build 23.0.2)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
• Xcode at /Applications/Xcode-16.0.0.app/Contents/Developer
• Build 16A242d
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.2)
• Android Studio at /Users/bartek/Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.4+-12422083-b607.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.3.2.1)
• IntelliJ at /Users/bartek/Applications/IntelliJ IDEA Ultimate.app
• Flutter plugin version 83.0.4
• Dart plugin version 243.23654.44
[✓] VS Code (version 1.96.4)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (5 available)
• sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64 • Android 14 (API 34) (emulator)
• Barteks-iPhone (mobile) • 00008120-001E352E22B8201E • ios • iOS 18.2.1 22C161
• macOS (desktop) • macos • darwin-arm64 • macOS 15.2 24C101 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 15.2 24C101 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.265
[✓] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| t: gradle,a: existing-apps,in triage | low | Critical |
2,811,284,210 | go | runtime: binary analysis failed due to fake PC in gosave_systemstack_switch | ### Go version
go version go 1.22.6 linux/amd64
### Output of `go env` in your module/workspace:
```shell
GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/usr1/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/opt/go_workpace/pkg/mod'
GONOSUMDB='*'
GOOS='linux'
GOPATH='/opt/go_workpace'
GOROOT='/root/tt/go-go1.22.6/'
GOSUMDB='off'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/root/tt/go-go1.22.6/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.6'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4051586591=/tmp/go-build -gno-record-gcc-switches'
```
### What did you do?
Hi, I want to build CFG of one binary but when I try to track the destination address of the instruction
`4735a0: 4c 8d 0d 21 0e 00 00 lea 0xe21(%rip),%r9 # 4743c8 <runtime.systemstack_switch.abi0+0x8>` ,
this address is in the middle of one instruction and causes a fault.
gosave_systemstack_switch:
```
00000000004735a0 <gosave_systemstack_switch>:
4735a0: 4c 8d 0d 21 0e 00 00 lea 0xe21(%rip),%r9 # 4743c8 <runtime.systemstack_switch.abi0+0x8>
4735a7: 4d 89 4e 40 mov %r9,0x40(%r14)
4735ab: 4c 8d 4c 24 08 lea 0x8(%rsp),%r9
4735b0: 4d 89 4e 38 mov %r9,0x38(%r14)
4735b4: 49 c7 46 58 00 00 00 movq $0x0,0x58(%r14)
4735bb: 00
4735bc: 49 89 6e 68 mov %rbp,0x68(%r14)
4735c0: 4d 8b 4e 50 mov 0x50(%r14),%r9
4735c4: 4d 85 c9 test %r9,%r9
4735c7: 74 05 je 4735ce <gosave_systemstack_switch+0x2e>
4735c9: e8 12 2b 00 00 call 4760e0 <runtime.abort.abi0>
4735ce: c3 ret
```
runtime.systemstack_switch.abi0:
```
00000000004743c0 <runtime.systemstack_switch.abi0>:
4743c0: 55 push %rbp
4743c1: 48 89 e5 mov %rsp,%rbp
4743c4: 0f 0b ud2
4743c6: e8 15 1d 00 00 call 4760e0 <runtime.abort.abi0>
4743cb: 5d pop %rbp
4743cc: c3 ret
```
### What did you see happen?
Since the value here is in the middle of instruction, I couldn't finish CFG build work.
### What did you expect to see?
The explanation for the "+8" in function gosave_systemstack_switch is to skip the prologue. And the prologue of amd64 should be 4 bytes, maybe better to change this vaule to 4?
gosave_systemstack_switch in runtime/asm_amd64.s:
```
// Save state of caller into g->sched,
// but using fake PC from systemstack_switch.
// Must only be called from functions with frame pointer
// and without locals ($0) or else unwinding from
// systemstack_switch is incorrect.
// Smashes R9.
TEXT gosave_systemstack_switch<>(SB),NOSPLIT|NOFRAME,$0
// Take systemstack_switch PC and add 8 bytes to skip
// the prologue. The final location does not matter
// as long as we are between the prologue and the epilogue.
MOVQ $runtime·systemstack_switch+8(SB), R9
MOVQ R9, (g_sched+gobuf_pc)(R14)
LEAQ 8(SP), R9
MOVQ R9, (g_sched+gobuf_sp)(R14)
MOVQ $0, (g_sched+gobuf_ret)(R14)
MOVQ BP, (g_sched+gobuf_bp)(R14)
// Assert ctxt is zero. See func save.
MOVQ (g_sched+gobuf_ctxt)(R14), R9
TESTQ R9, R9
JZ 2(PC)
CALL runtime·abort(SB)
RET
``` | WaitingForInfo,compiler/runtime,BugReport | low | Critical |
2,811,284,294 | kubernetes | Inconsistent workloads and the pod ready state | ### What would you like to be added?
k8s version is 1.28.1.
The problem handling process is as follows:
1. Use STS to create a pod webswingservice.
2. A CSI plug-in is customized. webswingservice depends on this plug-in.
3. The first startup process is smooth.
4. The node is powered off once after startup.
5. After the system is powered on, the customized CSI fault is not rectified. As a result, volumes fail to be mounted to webswingservice.
6. The webswingservice does not execute the probe because the volume fails to be attached. Therefore, the phase and conditions.Ready in the pod are still in the ready state.
7. In this case, the pod status is not ready, but the workload is not updated. As a result, the inconsistency occurs.
8. The following figure shows the proble
```
[root@master1 ~]# kubectl get po -A | grep webswingservice
webswingservice-0 0/2 Unknown 47h
webswingservice-1 0/2 Unknown 47h
webswingservice-2 0/2 Unknown 47h
[root@master1 ~]#
[root@master1 ~]#
[root@master1 ~]#
[root@master1 ~]# kubectl get sts -n test webswingservice
NAME ReADY AGE
webswingservice 3/3 47h
[root@master1 ~]#
```
Code snippet:
1. The probe is executed only when the volume is successfully attached to the SyncPod.
https://github.com/kubernetes/kubernetes/blob/9d9e08b3179aa8df23909b495c2001b8cccf494a/pkg/kubelet/kubelet.go#L1911-L1933
2. The sts checks whether the pod is ready.
https://github.com/kubernetes/kubernetes/blob/9d9e08b3179aa8df23909b495c2001b8cccf494a/pkg/controller/statefulset/stateful_set_utils.go#L461-L464
### Why is this needed?
Is this a problem? Is there any solution?
| sig/storage,sig/node,kind/feature,needs-triage | low | Minor |
2,811,313,865 | vscode | After New Copilot coding doesn't save! |
Type: <b>Bug</b>
After the Copilot update, whenever I finish coding, save my work, and exit VS Code, the changes are not saved in the actual document but are only recorded in the timeline. As a result, I have to restore my work every time I reopen VS Code. Additionally, there are instances where the saved work in the timeline has errors or is documented at random times, with coding sessions being saved prematurely.
This issue means that when I open VS Code, I have to manually restore my work from the last session because the script file itself never ends up saving properly.
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
<!-- generated by issue reporter --> | info-needed | low | Critical |
2,811,368,324 | ollama | Compile ollama failed in debian | ### What is the issue?
I tried to compile ollama in debian, but it give these information and quit compile. Please help me. Thank you!
```
root@debian:~/ollama# make -j12
GOARCH=amd64 go build -buildmode=pie "-ldflags=-w -s \"-X=github.com/ollama/ollama/version.Version=0.5.7-5-g453e4d0\" " -trimpath -tags "avx" -o llama/build/linux-amd64/runners/cpu_avx/ollama_llama_server ./cmd/runner
GOARCH=amd64 go build -buildmode=pie "-ldflags=-w -s \"-X=github.com/ollama/ollama/version.Version=0.5.7-5-g453e4d0\" " -trimpath -tags "avx,avx2" -o llama/build/linux-amd64/runners/cpu_avx2/ollama_llama_server ./cmd/runner
GOARCH=amd64 go build -buildmode=pie "-ldflags=-w -s \"-X=github.com/ollama/ollama/version.Version=0.5.7-5-g453e4d0\" " -trimpath -o ollama .
# github.com/ollama/ollama/llama
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 72 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 88 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 104 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 120 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# github.com/ollama/ollama/llama
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 72 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 88 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 104 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 16 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 120 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# github.com/ollama/ollama/llama
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 32 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 72 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘block_q4_0x4 make_block_q4_0x4(block_q4_0*, unsigned int)’,
inlined from ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’ at ggml-cpu-aarch64.cpp:3711:39:
ggml-cpu-aarch64.cpp:3640:19: warning: writing 32 bytes into a region of size 0 [-Wstringop-overflow=]
3640 | memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ggml-cpu-aarch64.cpp: In function ‘int repack_q4_0_to_q4_0_4_bl(ggml_tensor*, int, const void*, size_t)’:
ggml-cpu-aarch64.cpp:3711:20: note: at offset 104 into destination object ‘<anonymous>’ of size 72
3711 | *dst++ = make_block_q4_0x4(dst_tmp, interleave_block);
| ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
>
=============================
gcc version 12.2.0 (Debian 12.2.0-14)
go version go1.23.5 linux/amd64
### OS
Linux
### GPU
_No response_
### CPU
AMD
### Ollama version
0.5.7 | bug | low | Critical |
2,811,375,381 | ollama | Improve Documentation for Ollama | Currently, the documentation consists of .md content which is located [here](https://github.com/ollama/ollama/tree/main/docs). I think that the documentation can be greatly improved if it is hosted as a static site using [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/). It uses markdown content for the site and can be incorporated into the current project without having any breaking changes of existing documentation.
I can help to set-up this site by contributing a PR towards this issue. Could you please let me know?
cc: @dhiltgen | feature request | low | Minor |
2,811,377,122 | langchain | Can not implement stream in langchain with vllm (qwen2.5) | ### Checked other resources
- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).
### Example Code
The following code:
```python
from langchain_community.llms import VLLM
llm = VLLM(
model="./models/Qwen2.5-14B-Instruct",
trust_remote_code=True,
max_new_tokens=128,
top_k=10,
top_p=0.95,
temperature=0.8,
)
for chunk in llm.stream("What is the capital of France ?"):
print(chunk, end="|", flush=True)
```
### Error Message and Stack Trace (if applicable)
Output from langchain (not stream):
```
Correct! The capital of France is Paris. It is known for its iconic landmarks like the Eiffel Tower, Louvre Museum, and Notre-Dame Cathedral, among many others. Do you have any other questions about France or Paris? I'd be happy to help!
Is there something specific you would like to know about Paris or France in general? For example:
1. History
2. Culture
3. Cuisine
4. Attractions
5. Transportation
6. Language
7. Weather
8. Population
9. Economy
10. Education
Let me know if you have any particular interests|[rank0]:[W126 15:42:23.470267241 ProcessGroupNCCL.cpp:1250] Warning: WARNING: process group has NOT been destroyed before we destruct ProcessGroupNCCL. On normal program exit, the application should call destroy_process_group to ensure that any pending NCCL operations have finished in this process. In rare cases this process can exit before this point and block the progress of another member of the process group. This constraint has always been present, but this warning has only been added since PyTorch 2.4 (function operator())
```
### Description
These code can not output in stream, and I know vllm with qwen2.5 can output in stream (I make it), so is there something wrong to config in langchain? Is there anyone tell me the right code? I want to realize vllm with qwen2.5 and output in stream inside langchain.
I have search the whole web, and none of code can work.
### System Info
System Information
------------------
> OS: Linux
> OS Version: #1 SMP Fri Mar 24 10:04:47 CST 2023
> Python Version: 3.12.8 | packaged by Anaconda, Inc. | (main, Dec 11 2024, 16:31:09) [GCC 11.2.0]
Package Information
-------------------
> langchain_core: 0.3.31
> langchain: 0.3.15
> langchain_community: 0.3.15
> langsmith: 0.3.1
> langchain_text_splitters: 0.3.5
> langgraph_sdk: 0.1.51
Optional packages not installed
-------------------------------
> langserve
Other Dependencies
------------------
> aiohttp: 3.11.11
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> httpx: 0.28.1
> httpx-sse: 0.4.0
> jsonpatch: 1.33
> langsmith-pyo3: Installed. No version info available.
> numpy: 1.26.4
> orjson: 3.10.13
> packaging: 24.2
> pydantic: 2.10.4
> pydantic-settings: 2.7.1
> pytest: 8.3.4
> PyYAML: 6.0.2
> requests: 2.32.2
> requests-toolbelt: 1.0.0
> rich: 13.9.4
> SQLAlchemy: 2.0.37
> tenacity: 9.0.0
> typing-extensions: 4.12.2
> zstandard: 0.23.0 | 🤖:bug | low | Critical |
2,811,377,321 | kubernetes | NodeUnstageVolume should be called even when stagingPath doesn't exist | ### What happened?
[pkg/volume/csi/csi_block.go](https://github.com/kubernetes/kubernetes/blob/release-1.32/pkg/volume/csi/csi_block.go#L458)
```go
// Call NodeUnstageVolume
stagingPath := m.GetStagingPath()
if _, err := os.Stat(stagingPath); err != nil {
if os.IsNotExist(err) {
klog.V(4).Info(log("blockMapper.TearDownDevice stagingPath(%s) has already been deleted, skip calling NodeUnstageVolume", stagingPath))
} else {
return err
}
} else {
err := m.unstageVolumeForBlock(ctx, csiClient, stagingPath)
if err != nil {
return err
}
}
```
If the stagingPath doesn't exist, NodeUnstageVolume won't be called.
In my opinion, NodeUnstageVolume should be called even when stagingPath doesn't exist, for the following reasons:
1. As long as CSI supports StageUnstage capability, the CSI should be able to properly handle cases where stagingPath doesn't exist
2. If NodeUnstageVolume return error but stagingPath is cleaned up, NodeUnstageVolume won't be called again in next retry
3. For filesystem PVCs, NodeUnstageVolume is called normally even when stagingPath doesn't exist
4. When a CSI driver is upgraded from non-StageUnstage to StageUnstage support, volumes mounted before the upgrade won't have stagingPath. However, these pre-upgrade volumes still need NodeUnstageVolume to be called for proper unmounting
### What did you expect to happen?
For block pvc, NodeUnstageVolume should be called even when stagingPath doesn't exist
### How can we reproduce it (as minimally and precisely as possible)?
It can be intuitively seen from the code
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
```console
1.32
```
</details>
### Cloud provider
<details>
</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>
| kind/bug,sig/storage,needs-triage | low | Critical |
2,811,385,412 | ant-design | 在`startTransition`中使用`message`会产生死循环渲染 | ### Reproduction link
[](https://codesandbox.io/p/sandbox/antd-52252-react18-mqldlr)
### Steps to reproduce
- 通过App.useApp() 获取 message
- 调用message，然后立刻通过startTransition调用message
### What is expected?
message正常工作
### What is actually happening?
startTransition中调用的message不展示， 控制台出现Maximum update depth exceeded警告，多次调用后弹出的message不停闪烁
| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18.3.1, 19.0.0 |
| System | windows 11 |
| Browser | Edge 131 |
---
初步怀疑是useNotification这里的队列处理在transition中有问题, 在不停更新taskQueue
https://github.com/react-component/notification/blob/0a6f542dc279f013da3eec18a9ff54a49646e588/src/hooks/useNotification.tsx#L163
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | unconfirmed | low | Minor |
2,811,388,420 | ant-design | Space.Compact does not collapse the border when wrapping a Form.Item | ### Reproduction link
[](https://codesandbox.io/p/sandbox/registration-antd-5-23-2-forked-7zpwhj?file=%2Findex.html&workspaceId=ws_UJWDJFW6u5eT5bSdmMxLcC)
### Steps to reproduce
Look at the borders between inputs middle and input & button right. When using `Space.Compact` with a `Form.Item` wrapped around it, the border does not collapse correctly.
### What is expected?
* The border should collapse correctly when `Space.Compact` is used with a `Form.Item`
### What is actually happening?
No collapsing (double-border)
| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18.3.1 |
| System | Windows 11 |
| Browser | Latest Chrome |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | unconfirmed | low | Minor |
2,811,390,556 | rust | Unable to build for aarch64-unknown-linux-musl due to linker error | <!--
Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->
### Code
```Rust
// Any general rust binary
fn main() {
}
```
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
```
2025-01-26
rust version 1.86.0-nightly
```
### Error output
```
error: linker stderr: + set -euo pipefail
+ main /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crt1.o /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crti.o /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtbegin.o /tmp/rustcMRMm0k/symbols.o /target/aarch64-unknown-linux-musl/release/deps/lead-1f9b10ec67568278.lead.3071a641ae748844-cgu.0.rcgu.o /target/aarch64-unknown-linux-musl/release/deps/lead-1f9b10ec67568278.c7k22yv4ejhuebl8qlxz30v80.rcgu.o -Wl,--as-needed -Wl,-Bstatic /target/aarch64-unknown-linux-musl/release/deps/liblead_lib-bacbb8bfd222c4bc.rlib /target/aarch64-unknown-linux-musl/release/deps/libtokio-2a08c53988ff36e2.rlib /target/aarch64-unknown-linux-musl/release/deps/libpin_project_lite-780a0af350feaf81.rlib /target/aarch64-unknown-linux-musl/release/deps/libserde_json-47ec56fca705be98.rlib /target/aarch64-unknown-linux-musl/release/deps/libitoa-2b078b22c12625d1.rlib /target/aarch64-unknown-linux-musl/release/deps/libryu-bf0d602fea867257.rlib /target/aarch64-unknown-linux-musl/release/deps/libserde-a1e14f5d7bb654b5.rlib /target/aarch64-unknown-linux-musl/release/deps/libsysinfo-eba4aaffb10bb843.rlib /target/aarch64-unknown-linux-musl/release/deps/libmemchr-9271502c4c235762.rlib /target/aarch64-unknown-linux-musl/release/deps/liblibc-c2df7424b4a503ee.rlib /target/aarch64-unknown-linux-musl/release/deps/libtermcolor-a0bf074affadcd0e.rlib /target/aarch64-unknown-linux-musl/release/deps/liblibloading-85d4fcd29f421964.rlib -ldl /target/aarch64-unknown-linux-musl/release/deps/libcfg_if-f51b0f5c6a991aaf.rlib /target/aarch64-unknown-linux-musl/release/deps/libinterpreter-2578f24c781ac431.rlib /target/aarch64-unknown-linux-musl/release/deps/libchalk_rs-0a1a1dda2caf4043.rlib /target/aarch64-unknown-linux-musl/release/deps/libstd-134d330340b3f11d.rlib /target/aarch64-unknown-linux-musl/release/deps/libpanic_unwind-874d3ed394a68975.rlib /target/aarch64-unknown-linux-musl/release/deps/libobject-b5d3c6a99dfa42fe.rlib /target/aarch64-unknown-linux-musl/release/deps/libmemchr-e8e488bcdb2cb511.rlib /target/aarch64-unknown-linux-musl/release/deps/libaddr2line-b69ae8fd75a99eb2.rlib /target/aarch64-unknown-linux-musl/release/deps/libgimli-8c254d9ac35de2d1.rlib /target/aarch64-unknown-linux-musl/release/deps/librustc_demangle-da6c261b96e0811c.rlib /target/aarch64-unknown-linux-musl/release/deps/libstd_detect-4df6928bf7ceb181.rlib /target/aarch64-unknown-linux-musl/release/deps/libhashbrown-e08e7bca1be74d3e.rlib /target/aarch64-unknown-linux-musl/release/deps/librustc_std_workspace_alloc-469d6ec4f00c806d.rlib /target/aarch64-unknown-linux-musl/release/deps/libminiz_oxide-f7340bd2d7755a3b.rlib /target/aarch64-unknown-linux-musl/release/deps/libadler2-0020ebc36cbafeb6.rlib /target/aarch64-unknown-linux-musl/release/deps/libunwind-a1edb29db249baea.rlib -lunwind /target/aarch64-unknown-linux-musl/release/deps/libcfg_if-77a284f515878d98.rlib /target/aarch64-unknown-linux-musl/release/deps/liblibc-31ad04b4538d525a.rlib -lc /target/aarch64-unknown-linux-musl/release/deps/liballoc-30aa088104f0fc7f.rlib /target/aarch64-unknown-linux-musl/release/deps/librustc_std_workspace_core-5466acb924e4ccef.rlib /target/aarch64-unknown-linux-musl/release/deps/libcore-a164a7b283c75181.rlib /target/aarch64-unknown-linux-musl/release/deps/libcompiler_builtins-c0dfb468808d9541.rlib -Wl,-Bdynamic -Wl,--eh-frame-hdr -Wl,-z,noexecstack -nostartfiles -L /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained -L /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib -o /target/aarch64-unknown-linux-musl/release/deps/lead-1f9b10ec67568278 -Wl,--gc-sections -static -no-pie -Wl,-z,relro,-z,now -Wl,-O1 -Wl,--strip-debug -nodefaultlibs /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtend.o /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtn.o
+ local minor
+ local patched_minor=48
++ rustc_minor_version
++ [[ -z 86 ]]
++ echo 86
+ minor=86
+ [[ 64 -eq 0 ]]
+ [[ 86 -ge 48 ]]
+ exec aarch64-linux-musl-gcc /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crt1.o /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crti.o /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtbegin.o /tmp/rustcMRMm0k/symbols.o /target/aarch64-unknown-linux-musl/release/deps/lead-1f9b10ec67568278.lead.3071a641ae748844-cgu.0.rcgu.o /target/aarch64-unknown-linux-musl/release/deps/lead-1f9b10ec67568278.c7k22yv4ejhuebl8qlxz30v80.rcgu.o -Wl,--as-needed -Wl,-Bstatic /target/aarch64-unknown-linux-musl/release/deps/liblead_lib-bacbb8bfd222c4bc.rlib /target/aarch64-unknown-linux-musl/release/deps/libtokio-2a08c53988ff36e2.rlib /target/aarch64-unknown-linux-musl/release/deps/libpin_project_lite-780a0af350feaf81.rlib /target/aarch64-unknown-linux-musl/release/deps/libserde_json-47ec56fca705be98.rlib /target/aarch64-unknown-linux-musl/release/deps/libitoa-2b078b22c12625d1.rlib /target/aarch64-unknown-linux-musl/release/deps/libryu-bf0d602fea867257.rlib /target/aarch64-unknown-linux-musl/release/deps/libserde-a1e14f5d7bb654b5.rlib /target/aarch64-unknown-linux-musl/release/deps/libsysinfo-eba4aaffb10bb843.rlib /target/aarch64-unknown-linux-musl/release/deps/libmemchr-9271502c4c235762.rlib /target/aarch64-unknown-linux-musl/release/deps/liblibc-c2df7424b4a503ee.rlib /target/aarch64-unknown-linux-musl/release/deps/libtermcolor-a0bf074affadcd0e.rlib /target/aarch64-unknown-linux-musl/release/deps/liblibloading-85d4fcd29f421964.rlib -ldl /target/aarch64-unknown-linux-musl/release/deps/libcfg_if-f51b0f5c6a991aaf.rlib /target/aarch64-unknown-linux-musl/release/deps/libinterpreter-2578f24c781ac431.rlib /target/aarch64-unknown-linux-musl/release/deps/libchalk_rs-0a1a1dda2caf4043.rlib /target/aarch64-unknown-linux-musl/release/deps/libstd-134d330340b3f11d.rlib /target/aarch64-unknown-linux-musl/release/deps/libpanic_unwind-874d3ed394a68975.rlib /target/aarch64-unknown-linux-musl/release/deps/libobject-b5d3c6a99dfa42fe.rlib /target/aarch64-unknown-linux-musl/release/deps/libmemchr-e8e488bcdb2cb511.rlib /target/aarch64-unknown-linux-musl/release/deps/libaddr2line-b69ae8fd75a99eb2.rlib /target/aarch64-unknown-linux-musl/release/deps/libgimli-8c254d9ac35de2d1.rlib /target/aarch64-unknown-linux-musl/release/deps/librustc_demangle-da6c261b96e0811c.rlib /target/aarch64-unknown-linux-musl/release/deps/libstd_detect-4df6928bf7ceb181.rlib /target/aarch64-unknown-linux-musl/release/deps/libhashbrown-e08e7bca1be74d3e.rlib /target/aarch64-unknown-linux-musl/release/deps/librustc_std_workspace_alloc-469d6ec4f00c806d.rlib /target/aarch64-unknown-linux-musl/release/deps/libminiz_oxide-f7340bd2d7755a3b.rlib /target/aarch64-unknown-linux-musl/release/deps/libadler2-0020ebc36cbafeb6.rlib /target/aarch64-unknown-linux-musl/release/deps/libunwind-a1edb29db249baea.rlib -lunwind /target/aarch64-unknown-linux-musl/release/deps/libcfg_if-77a284f515878d98.rlib /target/aarch64-unknown-linux-musl/release/deps/liblibc-31ad04b4538d525a.rlib -lc /target/aarch64-unknown-linux-musl/release/deps/liballoc-30aa088104f0fc7f.rlib /target/aarch64-unknown-linux-musl/release/deps/librustc_std_workspace_core-5466acb924e4ccef.rlib /target/aarch64-unknown-linux-musl/release/deps/libcore-a164a7b283c75181.rlib /target/aarch64-unknown-linux-musl/release/deps/libcompiler_builtins-c0dfb468808d9541.rlib -Wl,-Bdynamic -Wl,--eh-frame-hdr -Wl,-z,noexecstack -nostartfiles -L /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained -L /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib -o /target/aarch64-unknown-linux-musl/release/deps/lead-1f9b10ec67568278 -Wl,--gc-sections -static -no-pie -Wl,-z,relro,-z,now -Wl,-O1 -Wl,--strip-debug -nodefaultlibs /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtend.o /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtn.o
|
= note: `-D linker-messages` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(linker_messages)]`
error: could not compile `lead_cli` (bin "lead") due to 1 previous error
```
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Backtrace</strong></summary>
<p>
```
<backtrace>
```
</p>
</details>
| A-linkage,A-lints,T-compiler,C-discussion,L-linker_messages | low | Critical |
2,811,397,885 | vscode | VSCode Extensions enable arbitrary remote code execution via exec(). Not sure if this is a bug/vulnerability or a feature. | <!-- ⚠️⚠️ 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?: No
<!-- 🪓 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.4
- OS Version: Windows 11
All VSCode extensions enable arbitrary remote code execution.
It can be used with any powerShell or bash command of your choice.
As long as the user of VSCode has permissions they are able to run any code as far as I am concerned. I have only tested with opening Microsoft Apps and running Linux commands.
Steps to Reproduce:
0. Build a basic extension
1. import { exec } from "child_process";
2. The only thing that matters is exec() you dont need to return data to the front end like I did with this function.
function windowsCheckActiveApplication(){
// Run the ListActiveApps logic every second
const powershellCommand = "Get-Process | Where-Object { $_.MainWindowHandle -ne 0 } | Select-Object Name";
exec(`powershell.exe -Command "${powershellCommand}"`, (error, stdout, stderr) => {
if (error) {
console.error(`Error fetching active apps: ${error.message}`);
return;
}
if (stderr) {
console.error(`Stderr while fetching active apps: ${stderr}`);
return;
}
// Parse active applications
activeApplications = stdout
.split("\n")
.map((line) => line.trim())
.filter((line) => line && line !== "Name" && !line.startsWith("----")); // Remove empty lines, headers, and separators
});
} | triage-needed | low | Critical |
2,811,408,710 | PowerToys | Crop And Lock - Thumbnail Shortcut | ### Description of the new feature / enhancement
Crop And Lock - Thumbnail shortcut
* please add option to zoom in at 1% increments
* please add option to make 'the thumbnail', transparent
* please add option to make 'the thumbnail', click-through. the user can click whatever is underneath the thumbnail
* please add option to make the thumbnail move away whenever the mouse is over 90% of the thumbnail. this will allow the user to use whatever is underneath the thumbnail and can still access the buttons to minimize / close the thumbnail
thank you
### Scenario when this would be used?
* for monitoring stock / crypto price while working on the computer. just need to see. no need to interact with the price
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,811,410,017 | yt-dlp | [Vimeo] Vimeo subtitles fail with error 403 (CAPTCHA page) due to use of vimeo.com instead of player.vimeo.com | ### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [x] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field
### Checklist
- [x] I'm reporting that yt-dlp is broken on a **supported** site
- [x] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [x] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [x] I've checked that all URLs and arguments with special characters are [properly quoted or escaped](https://github.com/yt-dlp/yt-dlp/wiki/FAQ#video-url-contains-an-ampersand--and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command)
- [x] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [x] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [ ] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required
### Region
Global (I am accessing from Australia)
### Provide a description that is worded well enough to be understood
### Short Version:
I believe Vimeo subtitles should be loaded from `player.vimeo.com` NOT `vimeo.com` (even though both often work) because the latter domain appears to have stricter Cloudflare rules that display a CAPTCHA page for some users (especially when on a VPN).
This breaks the downloading of VTT subtitles.
I don't seem to get a CAPTCHA page when downloading subtitles from `player.vimeo.com`.
### Further Details With Example:
When I attempt to download the following Vimeo video _WITH SUBTITLES_ the download fails due to a 403 Error on the VTT subtitles file. The 403 is being triggered by a Vimeo CAPTCHA page (presumably because I'm using a VPN) that requires a browser to interact with.
Sample Vimeo URL: https://player.vimeo.com/video/1049393408?h=2cb35698c0
Another video with same issue: https://player.vimeo.com/video/1048984535?h=a31d608c45
- I am NOT logged into Vimeo. These are Vimeo embed URLs with a hash in the URL that can be accessed by anybody that knows the URL. I'm not sure whether it being private makes any difference to the issue.
- The video and subtitles both display fine in the browser.
- The video also downloads perfectly well when subtitles are not requested.
- The 403 error appears when loading the VTT subtitle file from `vimeo.com` domain
- The VTT subtitle file downloads correctly if I manually download from `player.vimeo.com` domain
I can see that yt-dlp is looking for the subtitles at the following URL:
https://vimeo.com/texttrack/208674890.vtt?token=679603b0_0x7ccc9366954d27f115285bec40f878866c8a37d3
(Error 403)
When I check Chrome dev tools it is downloading the VTT file from:
https://player.vimeo.com/texttrack/208674890.vtt?token=6795ffb1_0xeddbfa0b80f86caa13c0f963d9be29fc5146c67c
(URL loads successfully)
I presume that the path to the VTT is being parsed from the JSON embedded in the HTML page (https://player.vimeo.com/video/1049393408?h=2cb35698c0) where the JSON looks like this:
```
"text_tracks": [{
"id": 208674890,
"lang": "en-x-autogen",
"url": "/texttrack/208674890.vtt?token=6795ffb1_0xeddbfa0b80f86caa13c0f963d9be29fc5146c67c",
"kind": "captions",
"label": "English (auto-generated)"
}],
```
If the HTML is coming from `player.vimeo.com` and browsers like Chrome also load the VTT files from `player.vimeo.com`, perhaps yt-dlp should also use this domain. Would there be any downsides to fetching the VTT subtitles from `player.vimeo.com`?
### Provide verbose output that clearly demonstrates the problem
- [x] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [x] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below
### Complete Verbose Output
```shell
yt-dlp -f "bestvideo*[height=720]+bestaudio*/best" --embed-subs --write-subs "https://player.vimeo.com/video/1049393408?h=2cb35698c0" --download-sections "*0-20" --verbose -U
[debug] Command-line config: ['-f', 'bestvideo*[height=720]+bestaudio*/best', '--embed-subs', '--write-subs', 'https://player.vimeo.com/video/1049393408?h=2cb35698c0', '--download-sections', '*0-20', '--verbose', '-U']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version [email protected] from yt-dlp/yt-dlp-nightly-builds [3b4531934] (win_exe)
[debug] Python 3.10.11 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1t 7 Feb 2023)
[debug] exe versions: ffmpeg 7.1-essentials_build-www.gyan.dev (setts), ffprobe 7.1-essentials_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.12.14, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.40.1, urllib3-2.3.0, websockets-14.2
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1839 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version: [email protected] from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date ([email protected] from yt-dlp/yt-dlp-nightly-builds)
[vimeo] Extracting URL: https://player.vimeo.com/video/1049393408?h=2cb35698c0
[vimeo] 1049393408: Downloading webpage
[vimeo] 1049393408: Downloading akfire_interconnect_quic m3u8 information
[vimeo] 1049393408: Downloading fastly_skyfire m3u8 information
[vimeo] 1049393408: Downloading akfire_interconnect_quic MPD information
WARNING: [vimeo] 1049393408: Failed to parse XML: not well-formed (invalid token): line 1, column 0
[vimeo] 1049393408: Downloading fastly_skyfire MPD information
WARNING: [vimeo] 1049393408: Failed to parse XML: not well-formed (invalid token): line 1, column 0
[info] 1049393408: Downloading subtitles: en-x-autogen
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, lang, vcodec, channels, acodec, size, br, asr, proto, vext, aext, hasaud, id
[info] 1049393408: Downloading 1 format(s): hls-fastly_skyfire-960+hls-fastly_skyfire-audio-high-English
[info] 1049393408: Downloading 1 time ranges: 0.0-20.0
[info] Writing video subtitles to: 2025-01-22 mid-week video [1049393408].en-x-autogen.vtt
[debug] Invoking http downloader on "https://vimeo.com/texttrack/208674890.vtt?token=679603b0_0x7ccc9366954d27f115285bec40f878866c8a37d3"
ERROR: Unable to download video subtitles for 'en-x-autogen': HTTP Error 403: Forbidden
Traceback (most recent call last):
File "yt_dlp\YoutubeDL.py", line 4364, in _write_subtitles
File "yt_dlp\YoutubeDL.py", line 3212, in dl
File "yt_dlp\downloader\common.py", line 464, in download
File "yt_dlp\downloader\http.py", line 367, in real_download
File "yt_dlp\downloader\http.py", line 118, in establish_connection
File "yt_dlp\YoutubeDL.py", line 4175, in urlopen
File "yt_dlp\networking\common.py", line 117, in send
File "yt_dlp\networking\_helper.py", line 208, in wrapper
File "yt_dlp\networking\common.py", line 340, in send
File "yt_dlp\networking\_requests.py", line 365, in _send
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "yt_dlp\YoutubeDL.py", line 1637, in wrapper
File "yt_dlp\YoutubeDL.py", line 1793, in __extract_info
File "yt_dlp\YoutubeDL.py", line 1852, in process_ie_result
File "yt_dlp\YoutubeDL.py", line 3024, in process_video_result
File "yt_dlp\YoutubeDL.py", line 177, in wrapper
File "yt_dlp\YoutubeDL.py", line 3280, in process_info
File "yt_dlp\YoutubeDL.py", line 4372, in _write_subtitles
yt_dlp.utils.DownloadError: Unable to download video subtitles for 'en-x-autogen': HTTP Error 403: Forbidden
``` | cant-reproduce,site-bug | low | Critical |
2,811,422,382 | godot | Godot 3 project to Godot 4 conversion failed but nothing is displayed to the user | ### Tested versions
Tested in 4.4.dev7 only.
### System information
Godot v4.4.dev7 - Windows 10 (build 19045) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated GeForce GTX 780M - Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz (8 threads)
### Issue description
I tried to convert [this project](https://github.com/adcomp/Godot3_2D_Island_OpenSimplexNoise) to Godot 4 and it failed whatever option picked (full project or project file only).
The project conversion window shows **nothing at all**.
Although, in log, there are these:
> Starting conversion.
ERROR: Class "IPUnix" does not exist in Godot 4, so it cannot be used in the conversion.
at: test_array_names (editor/project_converter_3_to_4.cpp:1172)
ERROR: Found function which is used in the converter, but it cannot be found in Godot 4. Rename this element or remove its entry if it's obsolete.
at: test_array_names (editor/project_converter_3_to_4.cpp:1222)
ERROR: Cannot start converting due to problems with data in arrays.
at: convert (editor/project_converter_3_to_4.cpp:334)
The error message regarding _IPUnix_ class is weird cause it is even not used in the project.
And this project is pretty small (one scene and one script), nothing fancy and just a few old stuff which have been modified like _export_ and _getset_ syntax, _lock/unlock_ functions of Image object no longer needed/available.
### Steps to reproduce
Download and convert the project given in the issue description.
No errors shown to the user.
Project list remain as it was before and the project doesn't appear in the list.
### Minimal reproduction project (MRP)
[this project](https://github.com/adcomp/Godot3_2D_Island_OpenSimplexNoise) | bug,topic:editor,needs testing | low | Critical |
Subsets and Splits