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,540,107,587 | opencv | undistortPoints function implementation is not working the near 180 degree points | https://github.com/opencv/opencv/blob/b2e118ea94f70f8a9f03aac6aaa260571f2010d9/modules/calib3d/src/fisheye.cpp#L439
when i use this function with fisheye image, there are some error near the 180 degrees. so i checked the codes of original source.
in opencv source code, theta_d means the distance from origin to xy plane. but according to the annotation, the theta_d means the incidence of points. this parts of code may occur error. we need to check the codes.
i think the incidence angle of this should be the sqrt(atan2(theta_d**2+1)/theta_d)) and need some other way exceptions for out of 180 degrees.
I am open to work on this error, please feel free to comment me back if any are interested in fixing this problem. | category: calib3d,needs investigation | low | Critical |
2,540,163,033 | stable-diffusion-webui | [Feature Request]: Allow order of operations on prompt parser | ### Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
### What would your feature do ?
Imagine the next prompt:
```txt
a cat AND a dog BREAK on a beach
```
Here this prompt can be parsed on 2 different ways:
1
```txt
a cat ━━━┓
┣━━┓
a dog ━━━┛ ┃
on a beach ━┻━━ OUTPUT
```
2
```txt
a cat ━━━━━━━━━━━┳━━ Output
a dog ━━━━━━━━┓ ┃
┣━━┛
on a beach ━━━┛
```
Both ways ends up with a different result. (drawing this ended up being more difficult than it looks)
My proposal is to do something similar to how math works, by a parenthesis-equivalent keywords, something like `BEGIN`/`END` so by doing that, now:
```txt
BEGIN a cat AND a dog END BREAK on a beach
```
and
```txt
a cat AND BEGIN a dog BREAK on a beach END
```
This is also relevant since other extensions create their own keywords and usually collide since there is no way to express order of operations. Having a native to the tool way of doing it might force the extension developers to respect them as well.
### Proposed workflow
No change on workflow, just a couple of keywords.
### Additional information
_No response_ | enhancement | low | Minor |
2,540,179,934 | angular | Wrong usage of HostBinding in example code | ### Which @angular/* package(s) are the source of the bug?
core
### Is this a regression?
No
### Description
getter method is missing in hostbinding examples here https://angular.dev/guide/components/host-elements
### Please provide a link to a minimal reproduction of the bug
https://angular.dev/guide/components/host-elements
### Please provide the exception or error you saw
_No response_
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular18
```
### Anything else?
_No response_ | P3,area: docs | low | Critical |
2,540,197,016 | neovim | API: one buffer text api to rule them all | ### Problem
(As usual, corrections/objections are welcome, I'm just writing things down...)
Currently we have lots of APIs to insert/replace text, but they all are slightly different:
```
nvim_buf_get_lines
nvim_buf_set_lines
nvim_buf_set_text
nvim_buf_get_text
nvim_buf_get_offset
nvim_del_current_line
nvim_put
```
And they are lacking features such as the ability to make the operation dot-repeatable. https://github.com/neovim/neovim/issues/19806#issuecomment-2365146298
(Note `nvim_paste` is intentionally not included in this.)
The current interface for any script/client that wants to dot-repeat text input is to use `nvim_paste`. However, `nvim_paste` doesn't have a way to "replace" text (unlike `nvim_buf_set_text`).
https://github.com/neovim/neovim/pull/30438 implements a reliable (internal) framework for setting up dot repeat. That opens the door for potentially enabling dot-repeat for things like `nvim_buf_set_text`.
### Expected behavior
Replace all of these functions with 2 APIs:
```typescript
nvim_buf_text_get(buf: int, opts: dict)
// If end_col!=start_col, this behaves like "put".
nvim_buf_text_set(buf: int, text: string, opts: dict)
// (Obviously some of these don't apply to every function.)
opts: {
repeat: bool // make the operation dot-repeatable
start_row: int // optional, use cursor position if not given
start_col: int // "
end_row: int // "
end_col: int // "
strict_indexing // do we need this?
type: string // "b"/"c"/"l". If linewise, then it can be
// fast like nvim_buf_set_lines?
after: bool // insert before/after cursor
follow: bool // place cursor after result.
crlf: bool
meta: bool // only return metadata, not text. To eliminate e.g.
// nvim_buf_line_count, nvim_buf_get_offset
}
```
| enhancement,api,ux | medium | Major |
2,540,211,531 | flutter | [camera] Camera 0.11+ API stops working Activity io.flutter.embedding.android.FlutterActivity has leaked IntentReceiver io.flutter.plugins.camerax.DeviceOrientationManager | ### What package does this bug report belong to?
camera
### What target platforms are you seeing this bug on?
Android
### Have you already upgraded your packages?
Yes
### Dependency versions
<details><summary>pubspec.lock</summary>
```lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
async:
dependency: transitive
description:
name: async
sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
url: "https://pub.dev"
source: hosted
version: "2.11.0"
boolean_selector:
dependency: transitive
description:
name: boolean_selector
sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
url: "https://pub.dev"
source: hosted
version: "2.1.1"
camera:
dependency: "direct main"
description:
name: camera
sha256: "26ff41045772153f222ffffecba711a206f670f5834d40ebf5eed3811692f167"
url: "https://pub.dev"
source: hosted
version: "0.11.0+2"
camera_android_camerax:
dependency: transitive
description:
name: camera_android_camerax
sha256: "7cd93578ad201dcc6bb5810451fb00d76a86bab9b68dceb68b8cbd7038ac5846"
url: "https://pub.dev"
source: hosted
version: "0.6.8+3"
camera_avfoundation:
dependency: transitive
description:
name: camera_avfoundation
sha256: "7c28969a975a7eb2349bc2cb2dfe3ad218a33dba9968ecfb181ce08c87486655"
url: "https://pub.dev"
source: hosted
version: "0.9.17+3"
camera_platform_interface:
dependency: transitive
description:
name: camera_platform_interface
sha256: b3ede1f171532e0d83111fe0980b46d17f1aa9788a07a2fbed07366bbdbb9061
url: "https://pub.dev"
source: hosted
version: "2.8.0"
camera_web:
dependency: transitive
description:
name: camera_web
sha256: "595f28c89d1fb62d77c73c633193755b781c6d2e0ebcd8dc25b763b514e6ba8f"
url: "https://pub.dev"
source: hosted
version: "0.3.5"
characters:
dependency: transitive
description:
name: characters
sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
url: "https://pub.dev"
source: hosted
version: "1.3.0"
clock:
dependency: transitive
description:
name: clock
sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
url: "https://pub.dev"
source: hosted
version: "1.1.1"
collection:
dependency: transitive
description:
name: collection
sha256: ee67cb0715911d28db6bf4af1026078bd6f0128b07a5f66fb2ed94ec6783c09a
url: "https://pub.dev"
source: hosted
version: "1.18.0"
cross_file:
dependency: transitive
description:
name: cross_file
sha256: "7caf6a750a0c04effbb52a676dce9a4a592e10ad35c34d6d2d0e4811160d5670"
url: "https://pub.dev"
source: hosted
version: "0.3.4+2"
csslib:
dependency: transitive
description:
name: csslib
sha256: "706b5707578e0c1b4b7550f64078f0a0f19dec3f50a178ffae7006b0a9ca58fb"
url: "https://pub.dev"
source: hosted
version: "1.0.0"
cupertino_icons:
dependency: "direct main"
description:
name: cupertino_icons
sha256: ba631d1c7f7bef6b729a622b7b752645a2d076dba9976925b8f25725a30e1ee6
url: "https://pub.dev"
source: hosted
version: "1.0.8"
fake_async:
dependency: transitive
description:
name: fake_async
sha256: "511392330127add0b769b75a987850d136345d9227c6b94c96a04cf4a391bf78"
url: "https://pub.dev"
source: hosted
version: "1.3.1"
flutter:
dependency: "direct main"
description: flutter
source: sdk
version: "0.0.0"
flutter_lints:
dependency: "direct dev"
description:
name: flutter_lints
sha256: "3f41d009ba7172d5ff9be5f6e6e6abb4300e263aab8866d2a0842ed2a70f8f0c"
url: "https://pub.dev"
source: hosted
version: "4.0.0"
flutter_plugin_android_lifecycle:
dependency: transitive
description:
name: flutter_plugin_android_lifecycle
sha256: "9ee02950848f61c4129af3d6ec84a1cfc0e47931abc746b03e7a3bc3e8ff6eda"
url: "https://pub.dev"
source: hosted
version: "2.0.22"
flutter_test:
dependency: "direct dev"
description: flutter
source: sdk
version: "0.0.0"
flutter_web_plugins:
dependency: transitive
description: flutter
source: sdk
version: "0.0.0"
html:
dependency: transitive
description:
name: html
sha256: "3a7812d5bcd2894edf53dfaf8cd640876cf6cef50a8f238745c8b8120ea74d3a"
url: "https://pub.dev"
source: hosted
version: "0.15.4"
leak_tracker:
dependency: transitive
description:
name: leak_tracker
sha256: "3f87a60e8c63aecc975dda1ceedbc8f24de75f09e4856ea27daf8958f2f0ce05"
url: "https://pub.dev"
source: hosted
version: "10.0.5"
leak_tracker_flutter_testing:
dependency: transitive
description:
name: leak_tracker_flutter_testing
sha256: "932549fb305594d82d7183ecd9fa93463e9914e1b67cacc34bc40906594a1806"
url: "https://pub.dev"
source: hosted
version: "3.0.5"
leak_tracker_testing:
dependency: transitive
description:
name: leak_tracker_testing
sha256: "6ba465d5d76e67ddf503e1161d1f4a6bc42306f9d66ca1e8f079a47290fb06d3"
url: "https://pub.dev"
source: hosted
version: "3.0.1"
lints:
dependency: transitive
description:
name: lints
sha256: "976c774dd944a42e83e2467f4cc670daef7eed6295b10b36ae8c85bcbf828235"
url: "https://pub.dev"
source: hosted
version: "4.0.0"
matcher:
dependency: transitive
description:
name: matcher
sha256: d2323aa2060500f906aa31a895b4030b6da3ebdcc5619d14ce1aada65cd161cb
url: "https://pub.dev"
source: hosted
version: "0.12.16+1"
material_color_utilities:
dependency: transitive
description:
name: material_color_utilities
sha256: f7142bb1154231d7ea5f96bc7bde4bda2a0945d2806bb11670e30b850d56bdec
url: "https://pub.dev"
source: hosted
version: "0.11.1"
meta:
dependency: transitive
description:
name: meta
sha256: bdb68674043280c3428e9ec998512fb681678676b3c54e773629ffe74419f8c7
url: "https://pub.dev"
source: hosted
version: "1.15.0"
path:
dependency: transitive
description:
name: path
sha256: "087ce49c3f0dc39180befefc60fdb4acd8f8620e5682fe2476afd0b3688bb4af"
url: "https://pub.dev"
source: hosted
version: "1.9.0"
plugin_platform_interface:
dependency: transitive
description:
name: plugin_platform_interface
sha256: "4820fbfdb9478b1ebae27888254d445073732dae3d6ea81f0b7e06d5dedc3f02"
url: "https://pub.dev"
source: hosted
version: "2.1.8"
sky_engine:
dependency: transitive
description: flutter
source: sdk
version: "0.0.99"
source_span:
dependency: transitive
description:
name: source_span
sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
url: "https://pub.dev"
source: hosted
version: "1.10.0"
stack_trace:
dependency: transitive
description:
name: stack_trace
sha256: "73713990125a6d93122541237550ee3352a2d84baad52d375a4cad2eb9b7ce0b"
url: "https://pub.dev"
source: hosted
version: "1.11.1"
stream_channel:
dependency: transitive
description:
name: stream_channel
sha256: ba2aa5d8cc609d96bbb2899c28934f9e1af5cddbd60a827822ea467161eb54e7
url: "https://pub.dev"
source: hosted
version: "2.1.2"
stream_transform:
dependency: transitive
description:
name: stream_transform
sha256: "14a00e794c7c11aa145a170587321aedce29769c08d7f58b1d141da75e3b1c6f"
url: "https://pub.dev"
source: hosted
version: "2.1.0"
string_scanner:
dependency: transitive
description:
name: string_scanner
sha256: "556692adab6cfa87322a115640c11f13cb77b3f076ddcc5d6ae3c20242bedcde"
url: "https://pub.dev"
source: hosted
version: "1.2.0"
term_glyph:
dependency: transitive
description:
name: term_glyph
sha256: a29248a84fbb7c79282b40b8c72a1209db169a2e0542bce341da992fe1bc7e84
url: "https://pub.dev"
source: hosted
version: "1.2.1"
test_api:
dependency: transitive
description:
name: test_api
sha256: "5b8a98dafc4d5c4c9c72d8b31ab2b23fc13422348d2997120294d3bac86b4ddb"
url: "https://pub.dev"
source: hosted
version: "0.7.2"
vector_math:
dependency: transitive
description:
name: vector_math
sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
url: "https://pub.dev"
source: hosted
version: "2.1.4"
video_player:
dependency: "direct main"
description:
name: video_player
sha256: e30df0d226c4ef82e2c150ebf6834b3522cf3f654d8e2f9419d376cdc071425d
url: "https://pub.dev"
source: hosted
version: "2.9.1"
video_player_android:
dependency: transitive
description:
name: video_player_android
sha256: "38d8fe136c427abdce68b5e8c3c08ea29d7a794b453c7a51b12ecfad4aad9437"
url: "https://pub.dev"
source: hosted
version: "2.7.3"
video_player_avfoundation:
dependency: transitive
description:
name: video_player_avfoundation
sha256: d1e9a824f2b324000dc8fb2dcb2a3285b6c1c7c487521c63306cc5b394f68a7c
url: "https://pub.dev"
source: hosted
version: "2.6.1"
video_player_platform_interface:
dependency: transitive
description:
name: video_player_platform_interface
sha256: "236454725fafcacf98f0f39af0d7c7ab2ce84762e3b63f2cbb3ef9a7e0550bc6"
url: "https://pub.dev"
source: hosted
version: "6.2.2"
video_player_web:
dependency: transitive
description:
name: video_player_web
sha256: "6dcdd298136523eaf7dfc31abaf0dfba9aa8a8dbc96670e87e9d42b6f2caf774"
url: "https://pub.dev"
source: hosted
version: "2.3.2"
vm_service:
dependency: transitive
description:
name: vm_service
sha256: "5c5f338a667b4c644744b661f309fb8080bb94b18a7e91ef1dbd343bed00ed6d"
url: "https://pub.dev"
source: hosted
version: "14.2.5"
web:
dependency: transitive
description:
name: web
sha256: d43c1d6b787bf0afad444700ae7f4db8827f701bc61c255ac8d328c6f4d52062
url: "https://pub.dev"
source: hosted
version: "1.0.0"
sdks:
dart: ">=3.5.3 <4.0.0"
flutter: ">=3.24.0"
```
</details>
### Steps to reproduce
Affected version camera: 0.11
Tested on camera 0.10.6 and no issue.
1. Open flutter page that use camera API using the cached flutter engine.
```
startActivity(
FlutterActivity
.withCachedEngine(MyApplication.FLUTTER_ENGINE_ID)
.build(this)
)
```
2. Close the flutter app
3. Reopen flutter app and recall camera API
4. Camera stops working, and error logs showing.
OR From Demo App
1. Clone the repo https://github.com/josephmangmang/Camera-Test-Module
2. cd camera_test_module
3. flutter pub get
4. cd ../CameraTest
5. gradle sync and run
6. Main UI -> Click **Open Camera withCachedEngine** & select any camera front or back
7. Press back button
8. Click again **Open Camera withCachedEngine** & select any camera front or back
9. Check logcat for error
https://github.com/user-attachments/assets/57bfaf5d-6a86-4c33-9525-6cafef1413cc
### Expected results
Camera API should be usable when using cached flutter engine.
### Actual results
Camera API not usable after the first app run.
### Code sample
<details open><summary>Code sample</summary>
I created example app to reproduce the issue [https://github.com/josephmangmang/Camera-Test-Module](https://github.com/josephmangmang/Camera-Test-Module)
</details>
### Screenshots or Videos
<details open>
<summary>Screenshots / Video demonstration</summary>
<img width="1669" alt="Screenshot 2024-09-21 at 7 58 05 PM" src="https://github.com/user-attachments/assets/53b279d3-fa5d-4909-9c5a-c4b96007bc4e">
</details>
### Logs
When using camera api for the first time after app launch and until closing the app
<details open><summary>Logs</summary>
```console
2024-09-21 19:44:12.056 9295-9321 flutter com.mt.cameratest I Method channel handler called with method: openCamera
2024-09-21 19:44:12.091 9295-9295 m.mt.camerates com.mt.cameratest W Accessing hidden method Landroid/view/accessibility/AccessibilityNodeInfo;->getSourceNodeId()J (greylist,test-api, reflection, allowed)
2024-09-21 19:44:12.091 9295-9295 m.mt.camerates com.mt.cameratest W Accessing hidden method Landroid/view/accessibility/AccessibilityRecord;->getSourceNodeId()J (greylist, reflection, allowed)
2024-09-21 19:44:12.091 9295-9295 m.mt.camerates com.mt.cameratest W Accessing hidden field Landroid/view/accessibility/AccessibilityNodeInfo;->mChildNodeIds:Landroid/util/LongArray; (greylist, reflection, allowed)
2024-09-21 19:44:12.091 9295-9295 m.mt.camerates com.mt.cameratest W Accessing hidden method Landroid/util/LongArray;->get(I)J (greylist, reflection, allowed)
2024-09-21 19:44:12.126 9295-9321 flutter com.mt.cameratest I Getting available cameras...
2024-09-21 19:44:12.142 9295-9322 HostConnection com.mt.cameratest D HostConnection::get() New Host Connection established 0xb4000077f51aa650, tid 9322
2024-09-21 19:44:12.143 9295-9322 HostConnection com.mt.cameratest D HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_vulkan ANDROID_EMU_deferred_vulkan_commands ANDROID_EMU_vulkan_null_optional_strings ANDROID_EMU_vulkan_create_resources_with_requirements ANDROID_EMU_YUV_Cache ANDROID_EMU_vulkan_ignored_handles ANDROID_EMU_has_shared_slots_host_memory_allocator ANDROID_EMU_vulkan_free_memory_sync ANDROID_EMU_vulkan_shader_float16_int8 ANDROID_EMU_vulkan_async_queue_submit ANDROID_EMU_sync_buffer_data ANDROID_EMU_vulkan_async_qsri ANDROID_EMU_read_color_buffer_dma GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object ANDROID_EMU_host_side_tracing ANDROID_EMU_gles_max_version_3_0
2024-09-21 19:44:12.144 9295-9322 EGL_emulation com.mt.cameratest D eglMakeCurrent: 0xb4000077e52101b0: ver 3 0 (tinfo 0xb4000077851e55e0) (first time)
2024-09-21 19:44:12.182 9295-9322 EGL_emulation com.mt.cameratest D eglCreateContext: 0xb4000077e52131d0: maj 3 min 0 rcv 3
2024-09-21 19:44:12.225 9295-9295 m.mt.camerates com.mt.cameratest W Accessing hidden method Landroid/app/ActivityThread;->currentActivityThread()Landroid/app/ActivityThread; (greylist, linking, allowed)
2024-09-21 19:44:12.225 9295-9295 m.mt.camerates com.mt.cameratest W Accessing hidden method Landroid/app/ActivityThread;->getActivity(Landroid/os/IBinder;)Landroid/app/Activity; (greylist, linking, allowed)
2024-09-21 19:44:12.225 9295-9351 ProfileInstaller com.mt.cameratest D Installing profile for com.mt.cameratest
2024-09-21 19:44:12.229 9295-9350 CameraManagerGlobal com.mt.cameratest I Connecting to camera service
2024-09-21 19:44:12.240 9295-9350 CameraRepository com.mt.cameratest D Added camera: 0
2024-09-21 19:44:12.246 9295-9350 Camera2CameraInfo com.mt.cameratest I Device Level: INFO_SUPPORTED_HARDWARE_LEVEL_3
2024-09-21 19:44:12.247 9295-9350 CameraRepository com.mt.cameratest D Added camera: 1
2024-09-21 19:44:12.248 9295-9350 Camera2CameraInfo com.mt.cameratest I Device Level: INFO_SUPPORTED_HARDWARE_LEVEL_FULL
2024-09-21 19:44:12.248 9295-9350 CameraValidator com.mt.cameratest D Verifying camera lens facing on emulator_arm64, lensFacingInteger: null
2024-09-21 19:44:12.312 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:12.364 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=270, isOppositeFacing=false, result=270
2024-09-21 19:44:12.365 9295-9321 flutter com.mt.cameratest I Available cameras: [CameraDescription(Camera 0, CameraLensDirection.back, 90), CameraDescription(Camera 1, CameraLensDirection.front, 270)]
2024-09-21 19:44:17.780 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.784 9295-9295 chatty com.mt.cameratest I uid=10168(com.mt.cameratest) identical 3 lines
2024-09-21 19:44:17.785 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.785 9295-9295 DynamicRangeResolver com.mt.cameratest D Resolved dynamic range for use case androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987 to no compatible HDR dynamic ranges.
DynamicRange@45b6a82{encoding=UNSPECIFIED, bitDepth=0}
->
DynamicRange@34001cd{encoding=SDR, bitDepth=8}
2024-09-21 19:44:17.790 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.790 9295-9295 DeferrableSurface com.mt.cameratest D Surface created[total_surfaces=1, used_surfaces=0](androidx.camera.core.processing.SurfaceEdge$SettableSurface@559acce}
2024-09-21 19:44:17.791 9295-9295 DeferrableSurface com.mt.cameratest D Surface created[total_surfaces=2, used_surfaces=0](androidx.camera.core.SurfaceRequest$2@ee7c7da}
2024-09-21 19:44:17.792 9295-9295 DeferrableSurface com.mt.cameratest D New surface in use[total_surfaces=2, used_surfaces=1](androidx.camera.core.SurfaceRequest$2@ee7c7da}
2024-09-21 19:44:17.792 9295-9295 DeferrableSurface com.mt.cameratest D use count+1, useCount=1 androidx.camera.core.SurfaceRequest$2@ee7c7da
2024-09-21 19:44:17.792 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.794 9295-9295 ImageCapture com.mt.cameratest D createPipeline(cameraId: 0, streamSpec: StreamSpec{resolution=640x480, dynamicRange=DynamicRange@34001cd{encoding=SDR, bitDepth=8}, expectedFrameRateRange=[0, 0], implementationOptions=androidx.camera.camera2.impl.Camera2ImplConfig@93485e7})
2024-09-21 19:44:17.797 9295-9295 DeferrableSurface com.mt.cameratest D Surface created[total_surfaces=3, used_surfaces=1](androidx.camera.core.impl.ImmediateSurface@3d39594}
2024-09-21 19:44:17.799 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181 ACTIVE
2024-09-21 19:44:17.799 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.799 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.800 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:17.800 9295-9295 DeferrableSurface com.mt.cameratest D Surface created[total_surfaces=4, used_surfaces=1](androidx.camera.core.impl.ImmediateSurface@d477832}
2024-09-21 19:44:17.800 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318 ACTIVE
2024-09-21 19:44:17.800 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:17.800 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181 ACTIVE
2024-09-21 19:44:17.800 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:17.801 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315 INACTIVE
2024-09-21 19:44:17.801 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:17.801 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:17.801 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use cases [androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318, androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315] now ATTACHED
2024-09-21 19:44:17.801 9295-9352 UseCaseAttachState com.mt.cameratest D All use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318, androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315] for camera: 0
2024-09-21 19:44:17.802 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318] for camera: 0
2024-09-21 19:44:17.803 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Resetting Capture Session
2024-09-21 19:44:17.803 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Releasing session in state INITIALIZED
2024-09-21 19:44:17.803 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Attempting to force open the camera.
2024-09-21 19:44:17.803 9295-9352 CameraStateRegistry com.mt.cameratest D tryOpenCamera(Camera@4cd9be0[id=0]) [Available Cameras: 1, Already Open: false (Previous state: null)] --> SUCCESS
2024-09-21 19:44:17.803 9295-9352 CameraStateRegistry com.mt.cameratest D Recalculating open cameras:
Camera State
-------------------------------------------------------------------
Camera@4cd9be0[id=0] OPENING
Camera@294d96a[id=1] UNKNOWN
-------------------------------------------------------------------
Open count: 1 (Max allowed: 1)
2024-09-21 19:44:17.804 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Opening camera.
2024-09-21 19:44:17.804 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Transitioning camera internal state: INITIALIZED --> OPENING
2024-09-21 19:44:17.804 9295-9352 CameraStateMachine com.mt.cameratest D New public camera state CameraState{type=OPENING, error=null} from OPENING and null
2024-09-21 19:44:17.804 9295-9352 CameraStateMachine com.mt.cameratest D Publishing new public camera state CameraState{type=OPENING, error=null}
2024-09-21 19:44:17.804 9295-9352 UseCaseAttachState com.mt.cameratest D All use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318, androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315] for camera: 0
2024-09-21 19:44:17.827 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318 ACTIVE
2024-09-21 19:44:17.827 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318] for camera: 0
2024-09-21 19:44:17.828 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181 ACTIVE
2024-09-21 19:44:17.828 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318] for camera: 0
2024-09-21 19:44:17.829 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use case androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315 INACTIVE
2024-09-21 19:44:17.829 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318] for camera: 0
2024-09-21 19:44:17.831 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} CameraDevice.onOpened()
2024-09-21 19:44:17.831 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Transitioning camera internal state: OPENING --> OPENED
2024-09-21 19:44:17.831 9295-9352 CameraStateRegistry com.mt.cameratest D Recalculating open cameras:
Camera State
-------------------------------------------------------------------
Camera@4cd9be0[id=0] OPEN
Camera@294d96a[id=1] UNKNOWN
-------------------------------------------------------------------
Open count: 1 (Max allowed: 1)
2024-09-21 19:44:17.831 9295-9352 CameraStateMachine com.mt.cameratest D New public camera state CameraState{type=OPEN, error=null} from OPEN and null
2024-09-21 19:44:17.831 9295-9352 CameraStateMachine com.mt.cameratest D Publishing new public camera state CameraState{type=OPEN, error=null}
2024-09-21 19:44:17.831 9295-9352 UseCaseAttachState com.mt.cameratest D All use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318, androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315] for camera: 0
2024-09-21 19:44:17.834 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318] for camera: 0
2024-09-21 19:44:17.834 9295-9352 SyncCaptureSessionBase com.mt.cameratest D [androidx.camera.camera2.internal.SynchronizedCaptureSessionBaseImpl@eb2cddb] getSurface...done
2024-09-21 19:44:17.834 9295-9352 CaptureSession com.mt.cameratest D Opening capture session.
2024-09-21 19:44:17.842 9295-9352 DeferrableSurface com.mt.cameratest D use count+1, useCount=2 androidx.camera.core.SurfaceRequest$2@ee7c7da
2024-09-21 19:44:17.842 9295-9352 DeferrableSurface com.mt.cameratest D New surface in use[total_surfaces=4, used_surfaces=2](androidx.camera.core.impl.ImmediateSurface@3d39594}
2024-09-21 19:44:17.842 9295-9352 DeferrableSurface com.mt.cameratest D use count+1, useCount=1 androidx.camera.core.impl.ImmediateSurface@3d39594
2024-09-21 19:44:17.842 9295-9352 DeferrableSurface com.mt.cameratest D New surface in use[total_surfaces=4, used_surfaces=3](androidx.camera.core.impl.ImmediateSurface@d477832}
2024-09-21 19:44:17.842 9295-9352 DeferrableSurface com.mt.cameratest D use count+1, useCount=1 androidx.camera.core.impl.ImmediateSurface@d477832
2024-09-21 19:44:17.847 9295-9352 CaptureSession com.mt.cameratest D Attempting to send capture request onConfigured
2024-09-21 19:44:17.847 9295-9352 CaptureSession com.mt.cameratest D Issuing request for session.
2024-09-21 19:44:17.848 9295-9352 Camera2Cap...estBuilder com.mt.cameratest D createCaptureRequest
2024-09-21 19:44:17.850 9295-9352 CaptureSession com.mt.cameratest D CameraCaptureSession.onConfigured() mState=OPENED
2024-09-21 19:44:17.850 9295-9352 CaptureSession com.mt.cameratest D CameraCaptureSession.onReady() OPENED
2024-09-21 19:44:17.851 9295-9314 Gralloc4 com.mt.cameratest W allocator 3.x is not supported
2024-09-21 19:44:17.869 9295-9295 CameraOrientationUtil com.mt.cameratest D getRelativeImageRotation: destRotationDegrees=0, sourceRotationDegrees=90, isOppositeFacing=true, result=90
2024-09-21 19:44:17.932 9295-9322 ImageReade...ceProducer com.mt.cameratest D ImageTextureEntry can't wait on the fence on Android < 33
2024-09-21 19:44:19.604 9295-9314 BufferQueueProducer com.mt.cameratest E [ImageReader-640x480f22m5-9295-3](id:244f00000003,api:4,p:365,c:9295) queueBuffer: BufferQueue has been abandoned
2024-09-21 19:44:19.604 9295-9314 BufferQueueProducer com.mt.cameratest E [ImageReader-640x480f22m5-9295-3](id:244f00000003,api:4,p:365,c:9295) dequeueBuffer: BufferQueue has been abandoned
2024-09-21 19:44:19.635 9295-9295 DeferrableSurface com.mt.cameratest D surface closed, useCount=2 closed=true androidx.camera.core.SurfaceRequest$2@ee7c7da
2024-09-21 19:44:19.635 9295-9295 DeferrableSurface com.mt.cameratest D surface closed, useCount=0 closed=true androidx.camera.core.processing.SurfaceEdge$SettableSurface@559acce
2024-09-21 19:44:19.636 9295-9295 DeferrableSurface com.mt.cameratest D Surface terminated[total_surfaces=3, used_surfaces=3](androidx.camera.core.processing.SurfaceEdge$SettableSurface@559acce}
2024-09-21 19:44:19.636 9295-9295 DeferrableSurface com.mt.cameratest D use count-1, useCount=1 closed=true androidx.camera.core.SurfaceRequest$2@ee7c7da
2024-09-21 19:44:19.637 9295-9295 ImageCapture com.mt.cameratest D clearPipeline
2024-09-21 19:44:19.637 9295-9295 DeferrableSurface com.mt.cameratest D surface closed, useCount=1 closed=true androidx.camera.core.impl.ImmediateSurface@3d39594
2024-09-21 19:44:19.637 9295-9316 BufferQueueProducer com.mt.cameratest E [ImageReader-640x480f22m5-9295-3](id:244f00000003,api:4,p:365,c:9295) queueBuffer: BufferQueue has been abandoned
2024-09-21 19:44:19.637 9295-9295 DeferrableSurface com.mt.cameratest D surface closed, useCount=1 closed=true androidx.camera.core.impl.ImmediateSurface@d477832
2024-09-21 19:44:19.638 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Use cases [androidx.camera.core.Preview-f94ddeb5-8d97-460a-b6ac-86c9463b5987146535318, androidx.camera.core.ImageCapture-1e3a1cd3-0752-452b-84f7-41153a1fdd4c185043181, androidx.camera.core.ImageAnalysis-e215b25d-24c3-4a42-9846-c77e238bc8a538523315] now DETACHED for camera
2024-09-21 19:44:19.638 9295-9352 UseCaseAttachState com.mt.cameratest D All use case: [] for camera: 0
2024-09-21 19:44:19.638 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Resetting Capture Session
2024-09-21 19:44:19.638 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Releasing session in state OPENED
2024-09-21 19:44:19.638 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:19.638 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:19.639 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Closing camera.
2024-09-21 19:44:19.639 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Transitioning camera internal state: OPENED --> CLOSING
2024-09-21 19:44:19.639 9295-9352 CameraStateRegistry com.mt.cameratest D Recalculating open cameras:
Camera State
-------------------------------------------------------------------
Camera@4cd9be0[id=0] CLOSING
Camera@294d96a[id=1] UNKNOWN
-------------------------------------------------------------------
Open count: 1 (Max allowed: 1)
2024-09-21 19:44:19.639 9295-9352 CameraStateMachine com.mt.cameratest D New public camera state CameraState{type=CLOSING, error=null} from CLOSING and null
2024-09-21 19:44:19.639 9295-9352 CameraStateMachine com.mt.cameratest D Publishing new public camera state CameraState{type=CLOSING, error=null}
2024-09-21 19:44:19.639 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Resetting Capture Session
2024-09-21 19:44:19.639 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Releasing session in state CLOSING
2024-09-21 19:44:19.639 9295-9352 CaptureSession com.mt.cameratest D onSessionFinished()
2024-09-21 19:44:19.671 9295-9314 BufferQueueProducer com.mt.cameratest E [ImageReader-640x480f22m5-9295-3](id:244f00000003,api:4,p:365,c:9295) queueBuffer: BufferQueue has been abandoned
2024-09-21 19:44:19.704 9295-9352 BufferQueueProducer com.mt.cameratest E [ImageReader-640x480f22m5-9295-3](id:244f00000003,api:4,p:365,c:9295) cancelBuffer: BufferQueue has been abandoned
2024-09-21 19:44:19.774 9295-9352 UseCaseAttachState com.mt.cameratest D Active and attached use case: [] for camera: 0
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D use count-1, useCount=0 closed=true androidx.camera.core.SurfaceRequest$2@ee7c7da
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D Surface no longer in use[total_surfaces=3, used_surfaces=2](androidx.camera.core.SurfaceRequest$2@ee7c7da}
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D Surface terminated[total_surfaces=2, used_surfaces=2](androidx.camera.core.SurfaceRequest$2@ee7c7da}
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D use count-1, useCount=0 closed=true androidx.camera.core.impl.ImmediateSurface@3d39594
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D Surface no longer in use[total_surfaces=2, used_surfaces=1](androidx.camera.core.impl.ImmediateSurface@3d39594}
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D Surface terminated[total_surfaces=1, used_surfaces=1](androidx.camera.core.impl.ImmediateSurface@3d39594}
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D use count-1, useCount=0 closed=true androidx.camera.core.impl.ImmediateSurface@d477832
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D Surface no longer in use[total_surfaces=1, used_surfaces=0](androidx.camera.core.impl.ImmediateSurface@d477832}
2024-09-21 19:44:19.774 9295-9352 DeferrableSurface com.mt.cameratest D Surface terminated[total_surfaces=0, used_surfaces=0](androidx.camera.core.impl.ImmediateSurface@d477832}
2024-09-21 19:44:19.774 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} CameraDevice.onClosed()
2024-09-21 19:44:19.774 9295-9352 Camera2CameraImpl com.mt.cameratest D {Camera@4cd9be0[id=0]} Transitioning camera internal state: CLOSING --> INITIALIZED
2024-09-21 19:44:19.775 9295-9352 CameraStateRegistry com.mt.cameratest D Recalculating open cameras:
Camera State
-------------------------------------------------------------------
Camera@4cd9be0[id=0] CLOSED
Camera@294d96a[id=1] UNKNOWN
-------------------------------------------------------------------
Open count: 0 (Max allowed: 1)
2024-09-21 19:44:19.775 9295-9352 CameraStateMachine com.mt.cameratest D New public camera state CameraState{type=CLOSED, error=null} from CLOSED and null
2024-09-21 19:44:19.775 9295-9352 CameraStateMachine com.mt.cameratest D Publishing new public camera state CameraState{type=CLOSED, error=null}
2024-09-21 19:44:20.076 9295-9295 ActivityThread com.mt.cameratest E Activity io.flutter.embedding.android.FlutterActivity has leaked IntentReceiver io.flutter.plugins.camerax.DeviceOrientationManager$1@2348a40 that was originally registered here. Are you missing a call to unregisterReceiver()?
android.app.IntentReceiverLeaked: Activity io.flutter.embedding.android.FlutterActivity has leaked IntentReceiver io.flutter.plugins.camerax.DeviceOrientationManager$1@2348a40 that was originally registered here. Are you missing a call to unregisterReceiver()?
at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:1594)
at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:1374)
at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1614)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1580)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1568)
at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:668)
at io.flutter.plugins.camerax.DeviceOrientationManager.start(DeviceOrientationManager.java:73)
at io.flutter.plugins.camerax.DeviceOrientationManagerHostApiImpl.startListeningForDeviceOrientationChange(DeviceOrientationManagerHostApiImpl.java:65)
at io.flutter.plugins.camerax.GeneratedCameraXLibrary$DeviceOrientationManagerHostApi.lambda$setup$0(GeneratedCameraXLibrary.java:1606)
at io.flutter.plugins.camerax.GeneratedCameraXLibrary$DeviceOrientationManagerHostApi$$ExternalSyntheticLambda0.onMessage(D8$$SyntheticClass:0)
at io.flutter.plugin.common.BasicMessageChannel$IncomingMessageHandler.onMessage(BasicMessageChannel.java:261)
at io.flutter.embedding.engine.dart.DartMessenger.invokeHandler(DartMessenger.java:292)
at io.flutter.embedding.engine.dart.DartMessenger.lambda$dispatchMessageToQueue$0$io-flutter-embedding-engine-dart-DartMessenger(DartMessenger.java:319)
at io.flutter.embedding.engine.dart.DartMessenger$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
```
</details>
After the crash and reusing the cached flutter engine and open the flutter app again then app access camera API.
<details open><summary>Logs</summary>
```console
2024-09-21 19:47:52.274 9295-9321 flutter com.mt.cameratest I Method channel handler called with method: openCamera
2024-09-21 19:47:52.340 9295-9321 flutter com.mt.cameratest I Getting available cameras...
2024-09-21 19:47:52.443 9295-9321 flutter com.mt.cameratest E [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(java.lang.NullPointerException, NullPointerException, Cause: null, Stacktrace: java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:220)
at io.flutter.plugins.camerax.ProcessCameraProviderHostApiImpl.getAvailableCameraInfos(ProcessCameraProviderHostApiImpl.java:92)
at io.flutter.plugins.camerax.GeneratedCameraXLibrary$ProcessCameraProviderHostApi.lambda$setup$1(GeneratedCameraXLibrary.java:1157)
at io.flutter.plugins.camerax.GeneratedCameraXLibrary$ProcessCameraProviderHostApi$$ExternalSyntheticLambda1.onMessage(D8$$SyntheticClass:0)
at io.flutter.plugin.common.BasicMessageChannel$IncomingMessageHandler.onMessage(BasicMessageChannel.java:261)
at io.flutter.embedding.engine.dart.DartMessenger.invokeHandler(DartMessenger.java:292)
at io.flutter.embedding.engine.dart.DartMessenger.lambda$dispatchMessageToQueue$0$io-flutter-embedding-engine-dart-DartMessenger(DartMessenger.java:319)
at io.flutter.embedding.engine.dart.DartMessenger$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
, null)
#0 ProcessCameraProviderHostApi.getAvailableCameraInfos (package:camera_android_camerax/src/camerax_library.g.dart:681:7)
<asynchronous suspension>
#1 ProcessCameraProviderHostApiImpl.getAvailableCameraInfosFromInstances (package:camera_android_camerax/src/process_camera_provider.dart:117:36)
<asynchronous suspension>
#2 AndroidCameraCameraX.availableCameras (package:camera_android_camerax/src/android_camera_camerax.dart:271:9)
<asynchronous suspension>
#3 _CameraExampleHomeState._getAvailableCamera (package:camera_test_module/camera_example.dart:970:18)
<asynchronous suspension>
2024-09-21 19:47:56.114 9295-9321 flutter com.mt.cameratest E [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(java.lang.NullPointerException, NullPointerException, Cause: null, Stacktrace: java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:220)
at io.flutter.plugins.camerax.ProcessCameraProviderHostApiImpl.unbindAll(ProcessCameraProviderHostApiImpl.java:173)
at io.flutter.plugins.camerax.GeneratedCameraXLibrary$ProcessCameraProviderHostApi.lambda$setup$5(GeneratedCameraXLibrary.java:1272)
at io.flutter.plugins.camerax.GeneratedCameraXLibrary$ProcessCameraProviderHostApi$$ExternalSyntheticLambda5.onMessage(D8$$SyntheticClass:0)
at io.flutter.plugin.common.BasicMessageChannel$IncomingMessageHandler.onMessage(BasicMessageChannel.java:261)
at io.flutter.embedding.engine.dart.DartMessenger.invokeHandler(DartMessenger.java:292)
at io.flutter.embedding.engine.dart.DartMessenger.lambda$dispatchMessageToQueue$0$io-flutter-embedding-engine-dart-DartMessenger(DartMessenger.java:319)
at io.flutter.embedding.engine.dart.DartMessenger$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
, null)
#0 ProcessCameraProviderHostApi.unbindAll (package:camera_android_camerax/src/camerax_library.g.dart:790:7)
<asynchronous suspension>
2024-09-21 19:47:56.158 9295-9321 flutter com.mt.cameratest E [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: type 'ProcessCameraProvider' is not a subtype of type 'VideoCapture?' in type cast
#0 InstanceManager.getInstanceWithWeakReference (package:camera_android_camerax/src/instance_manager.dart:121:64)
#1 VideoCaptureHostApiImpl.withOutputFromInstance (package:camera_android_camerax/src/video_capture.dart:85:10)
<asynchronous suspension>
#2 AndroidCameraCameraX.createCameraWithSettings (package:camera_android_camerax/src/android_camera_camerax.dart:386:20)
<asynchronous suspension>
#3 CameraController._initializeWithDescription (package:camera/src/camera_controller.dart:344:19)
<asynchronous suspension>
#4 _CameraExampleHomeState._initializeCameraController (package:camera_test_module/camera_example.dart:594:7)
<asynchronous suspension>
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
❯ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.3, on macOS 14.5 23F79 darwin-arm64, locale en-PH)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.93.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
• No issues found!
```
</details>
| platform-android,a: existing-apps,p: camera,has reproducible steps,P2,team-android,triaged-android,found in release: 3.24,found in release: 3.26 | low | Critical |
2,540,239,158 | neovim | API: clean up "meta info" functions for buf/win/tabpage | # Problem
Related: https://github.com/neovim/neovim/issues/30450
Currently there are lots of single-purpose APIs to get what may be called "editor metadata" about:
- a buffer (not its text contents, nor extmarks (which is a big topic), nor its scripting state such as `b:`/`w:`/etc.)
- a window (not highlight state or other "big topics")
- a tabpage
Besides just ergonomics (simpler interface + documentation), there are technical reasons why the above isn't ideal:
- The `nvim_buf_x` paradigm was intended to behave like "object methods", but each call on such an "object" would invoke a separate RPC request (`buf.line_count`, `buf.is_valid`). That's not a great tradeoff, because metadata is very cheap, thus it's better to put all metadata into one response instead of requiring multiple RPC calls.
- Calculating this metadata is cheap so there's no reason to require separate calls.
- Functions such as `nvim_buf_set_name` can trigger the swapfile ATTENTION dialog, yet there's currently no way to run it "noswapfile".
# Expected behavior
## For buffers:
- Deprecate the API `buf_x` meta functions in favor of the existing `getbufinfo()`.
- *Or* provide `nvim_buf_get(filter:table)` which returns a superset (except `b:`) of `getbufinfo()`.
- Introduce `nvim_buf_set(buf: int, info: dict, with: dict)`, which works like `nvim_open_win` on existing windows?
- ~~Doesn't look useful, only `name` would make sense.~~
- But `nvim_buf_set_name` has some side-effects which the caller may not want:
- can trigger the swapfile ATTENTION dialog, yet there's currently no way to run it "noswapfile".
- sets the alternate buffer
- The `with:dict` parameter would allow overriding and restoring various flags/options (internally uses `vim._with()`).
- Eliminates:
```
nvim_buf_is_loaded
nvim_buf_is_valid
nvim_buf_line_count
nvim_buf_get_name
nvim_buf_set_name
```
## For windows:
- Deprecate the API `win_x` meta functions in favor of the existing `getwininfo(filter:table)`.
- *Or* provide `nvim_win_get(filter:table)` which returns a superset (except `w:`) of `getwininfo()`.
- *Or* augment `nvim_win_get_config(filter:table)` to provide any missing meta fields.
- `nvim_win_set_config`, already exists, can we add a new optional `with: dict` param?
- Eliminates:
```
nvim_win_get_buf
nvim_win_get_cursor
nvim_win_get_height
nvim_win_get_number
nvim_win_get_position
nvim_win_get_width
nvim_win_is_valid
nvim_win_set_buf
nvim_win_set_height
nvim_win_set_width
```
- TODO: Not sure if we can eliminate:
```
nvim_win_set_cursor
nvim_win_text_height
```
## For tabpages:
- Deprecate the API `tabpage_x` meta functions in favor of the existing `gettabinfo(filter:table)`.
- *Or* provide `nvim_tabpage_get(filter:table)` which returns a superset (except `t:`) of `gettabinfo()`.
- Introduce `nvim_tabpage_set(tab: int, info: dict, with: dict)`
```
info {
name
curwin // current window
}
```
- layout? https://github.com/neovim/neovim/pull/24507
- Eliminates:
```
nvim_tabpage_list_wins
nvim_tabpage_get_win
nvim_tabpage_set_win
nvim_tabpage_get_number
nvim_tabpage_is_valid
```
| enhancement,api,ux,code-standards | low | Major |
2,540,248,684 | godot | Hot reload of @tool scripts stops working after first reload | ### Tested versions
- Reproduces in v4.3.stable.official [77dcf97d8]
- Fixed in v4.4.dev.custom_build [621cadcf6] (confirmed fixed in this commit; prior commit still has issue)
### System information
Godot v4.3.stable - macOS 14.6.1 - Vulkan (Forward+) - integrated Apple M3 Max - Apple M3 Max (16 Threads)
### Issue description
`@tool` scripts do not hot reload after the first hot reload when using an external editor. During the first hot reload the following error is generated:
```txt
modules/gdscript/gdscript.cpp:745 - Condition "!p_keep_state && has_instances" is true. Returning: ERR_ALREADY_IN_USE
```
Note this is not the same issue as #97238 which is 4.4 specific.
### Steps to reproduce
* Create a new project
* Add a Node3D
* Attach a script to that Node3D
* Make script a `@tool` script, and add a print to the `_ready()` function; save it
* Switch back to godot editor
* Save & reopen scene in editor (seems to be necessary on macos right now)
* Confirm print from `_ready()`
* Edit script to change print message; save script
* Switch back to godot editor
* Godot will display the `ERR_ALREADY_IN_USE` error
* Close and reopen scene and updated `_ready()` message will be printed
* Edit script, changing the print message again: save script
* Switch back to godot editor
* Godot will not print any new message
* close & reopens scene and the message from the previous edit will be shown
<img width="1204" alt="Screenshot 2024-09-21 at 8 12 06 AM" src="https://github.com/user-attachments/assets/caea1278-e071-4454-a9f9-41190e3f6f39">
### Minimal reproduction project (MRP)
[hot-reload-issue.zip](https://github.com/user-attachments/files/17084158/hot-reload-issue.zip)
| bug,topic:editor,regression | medium | Critical |
2,540,344,198 | PowerToys | Quick update selection | ### Description of the new feature / enhancement
In the "Hidden Icons" area where there is an icon for PowerToys, it would be nice to right-click on it and have as another option, either to select "check for updates," or if it can show that one is available, to select "update now." Additionally, how about a setting for automatically download and install updates?
### Scenario when this would be used?
Any time an update is needed or wanted.
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,540,353,462 | deno | Deno test outputs error locations with file:// url format | Version: Deno 1.46.2
When running `deno test`
On test fail, the output is
```
throw new AssertionError(message);
^
at assertEquals (https://deno.land/std@0.214.0/assert/assert_equals.ts:52:9)
at file:///home/sstep/wif/serv/test/serv.test.js:174:9
```
Because of `file://` format of the error location, it is not usable as a "jump to location" string in editors.
For example in vim, you would press `gF` to get to the location of error. But because it is in `file://` format it messes it up as a location pointer.
Perhaps it is better to show paths without file:// qualifier? | suggestion,testing | low | Critical |
2,540,355,292 | ant-design | Problem with some components with black primary colour | ### Reproduction link
[https://ant.design/theme-editor](https://ant.design/theme-editor)
### Steps to reproduce
Choose black as the primary colour.
### What is expected?
All components look normal, not only Button, Dapeticker, Checkbox, Radio...
### What is actually happening?
Some components look broken with black primary colour. For example:
Navigation, select, steps:
<img width="2551" alt="Screenshot 2024-09-21 at 18 06 28" src="https://github.com/user-attachments/assets/c86c8ef3-7d93-4404-8c00-8a05c34e8b53">
Cascader:
<img width="692" alt="Screenshot 2024-09-21 at 18 08 54" src="https://github.com/user-attachments/assets/2d360181-6ade-4a99-a2f3-32be78afb449">
Timepicker:
<img width="721" alt="Screenshot 2024-09-21 at 18 09 30" src="https://github.com/user-attachments/assets/de9cbd4d-bbc5-4bb4-8f26-b87edf8b2b85">
Transfer:
<img width="646" alt="Screenshot 2024-09-21 at 18 09 37" src="https://github.com/user-attachments/assets/09b862a6-5a66-4778-a63e-8b11333e1744">
Treeselect:
<img width="666" alt="Screenshot 2024-09-21 at 18 09 46" src="https://github.com/user-attachments/assets/83ad979f-1c37-4269-8d1f-040a7ecb1d6d">
Calendar:
<img width="1888" alt="Screenshot 2024-09-21 at 18 10 02" src="https://github.com/user-attachments/assets/6a7e1c98-e3e3-4ba4-9c75-b52ec6166eb2">
Alerts:
<img width="875" alt="Screenshot 2024-09-21 at 18 10 48" src="https://github.com/user-attachments/assets/a2843b2e-d15c-4294-b07b-ee7c716a5cd9">
| Environment | Info |
| --- | --- |
| antd | 5.20.6 |
| React | 18.3.1 |
| System | MacOS 15 |
| Browser | Edge 128.0.2739.79 |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | Inactive,unconfirmed | low | Critical |
2,540,360,498 | terminal | Sixel band with solid background color get transparent in some cases | ### Windows Terminal version
1.23.2611.0 (Canary)
### Windows build number
10.0.26100.1742 ARM64
### Steps to reproduce
This one is probably for @j4james
When displaying a sixel image with solid background (`␛P1;1q"…` or default `␛Pq"…`), bands are properly created filled with the solid background color before pseudo-pixels get decoded into them, only if the band is already in the viewport.
When reaching the end of the viewport, new bands added that require scrolling or extending the buffer are created with a transparent background instead of the solid background:
_(Solarized Light color scheme to make the background more visible, but happens with every color scheme)_
My test file has magenta as an unused color # 0, so the background is using black regardless of the VT palette, and then transparency for the bands scrolling the viewport or extending the buffer.
_Edit: Reading through #17887, I guess that's because I didn't set color # 256 and it defaulted to black_
Here's the test file: [test.zip](https://github.com/user-attachments/files/17084582/test.zip)
Is this the expected behavior to match old terminals and we need to explicitly draw all background pixels instead of relying on background fill, or is this a bug?
### Expected Behavior
Background should be reliably solid background color.
### Actual Behavior
In some cases, the background is transparent. | Area-VT,Issue-Bug,Product-Terminal,In-PR | low | Critical |
2,540,361,770 | transformers | ChameleonProcessor abstraction behaves unintuitively (ChameleonProcessor should also do VQ-GAE and BPE mapping and not ChameleonModel) | ### Feature request
# Moving VQ-GAE and BPE mapping to ChameleonProcessor
I am relatively new to HuggingFace and the Transformers library, but have many years of ML and software engineering experience, so I expect there are probably legacy reasons for this unintuitive behavior, but I thought I would share my thoughts and offer to contribute the changes if you are interested.
## Background
Chameleon operates on a sequence of tokens, so as a user you need to supply the sequence of input tokens to make a prediction. But **getting the sequence of tokens is a bit involved**. For text we use a text tokenizer, and for images we use a sequence of transformations. Images undergo multiple transformations: center cropping, resizing, normalizing etc. Then this centered, cropped, normalized, image is fed to a Vector Quantized Variational AutoEncoder (VQ-GAE) to generate image tokens which are then mapped to Byte Pair Encoding (BPE) tokens.
Luckily, the ChameleonProcessor provides us with an easy way to make the tokens, or does it?
Intuitively the ChameleonProcessor should give me the sequence of tokens I need to feed to Chameleon....
## What does it give me?
The ChameleonProcessor when called on a string and list of images creates a dict with:
1. key "input_ids": mapped to the token sequence for the text and 1026 tokens for every instance of "\<image\>" in the original text.
2. key "pixel_values": mapped to the tensors of the pixel values for the centered, cropped, normalized images.
3. key "attention_mask": not relevant to this discussion.
## What are these 1026 tokens for every "\<image\>"?
They are duplicated placeholder image tokens (1024 replications of the "8711" token) plus two sentinel tokens (beginning and end of image)
I.e. the **VQ-GAE and BPE mapping for the images and the substitution is left to later with the call to the Chameleon model**.
## What would I expect:
I would expect the ChameleonProcessor to finish its task, i.e. to also apply the VQ-GAE, and the BPE mapping and give me back the **actual input_ids that will be passed to the model**.
I would expect that the input_ids sequence **contains the actual image tokens from the and not a sequence of 1024 sentinel tokens to be swapped in later based on the pixel_values** during the call to the ChameleonModel.
Alternatively there could be some kind of middle step that combines the "input_ids" and "pixel_values" and gives the actual "input_ids", those that will be passed to the Chameleon model.
## Benefits
Mostly this would be more intuitive to users, they would get the actual input_ids and not have any mysterious changing of the tokens in their model call
It would also bring some latency reductions to some applications as the model call would not need to reprocess all the images every time, I.e. you don't need to do the VQ-GAE, BPE, mapping, token replacement on every call which may actually be worthwhile.
### Motivation
I am doing a project on crafting adversarial attacks for Chameleon and found this behaviour unintuitive and thought it would be useful to fix it upstream for the world.
### Your contribution
I can do the coding if you are interested. If you are open to it I can have a chat with some of your staff and send it in | Documentation,Feature request | low | Minor |
2,540,368,193 | deno | Force kill Deno.serve http server | I am testing automatic websocket reconnection, and I've found the best way to do it is to start a real HTTP server inside the test and then close it.
Unfortunately there is only a `.shutdown()` method, which waits 30s for active websocket connections to close on their own before ending the server. I tried passing a `signal` into it too (and aborting it), but it has the same behavior as `.shutdown()`.
To work around this issue, I created a set of connections:
```ts
private connections = new Set<WebSocket>();
```
which I then manage when the socket opens and closes:
```ts
const { response, socket } = Deno.upgradeWebSocket(req);
socket.onopen = () => {
this.connections.add(socket);
};
socket.onclose = () => {
this.connections.delete(socket);
};
```
finally, to close the server, I loop over the connections and call `.close()` on them, then I call `.shutdown()`:
```ts
async close(): Promise<void> {
this.connections.forEach((conn) => conn.close());
this.connections = new Set<WebSocket>();
await this.server.shutdown();
}
```
This workaround is working good for me, but ideally there would be a `server.kill()` or `server.shutdown(force = true)` method that would do basically the same thing sigint does to the server. | bug,ext/http | low | Minor |
2,540,384,420 | rust | `bind` may incorrectly create a dual-stack socket on some platforms |
`UdpSocket::bind` and `TcpListener::bind` can on some platforms incorrectly create a dual-stack socket. It seems very unlikely that these are intended to create dual-stack sockets as the API and documentation make no mention of it. There's also no alternate API that allow for the creation of IPv6 wildcard sockets. This means that if these API were intended to create dual-stack sockets, the standard library would be missing essential IPv6 functionality.
Additional there are good reasons to not have or add an API for dual-stack sockets in the standard library:
- Dual-stack sockets are not portable.
- They are unneccesary as you can use multiple sockets instead.
- They are limited in functionality as you cannot bind to a IPv4 / IPv6 pair.
Users not needing portability and wanting dual-stack sockets, may want to use a 3rd party crate (for example `socket2`) to create dual-stack sockets.
This bug have some rather bad consequences:
- This means that IPv4 may unexpectedly be accessible over the network which can be a security vulnerability. This is particularly bad if a user tests on a correctly behaving platform, but deploys on another.
- It's not possible to create portable IPv6 wildcard servers with `std`.
- It's not possible to create portable dual-stack wildcard servers with `std`.
This affects (at least):
- Linux
- macOS
Not affected:
- Windows
- OpenBSD (does not support dual-stack sockets)
| C-bug,T-libs | low | Critical |
2,540,386,070 | vscode | Feature request: setting to wrap absolute path Copy Path command with quotes | <!-- ⚠️⚠️ 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. -->
<!-- Describe the feature you'd like. -->
I use VSCode on Windows with git bash as the terminal. A problem I have is when I want to `cd` into a folder: I right click a folder, do Copy Path, focus the terminal and do `cd` and paste the folder. I end up with this:
```bash
$ cd C:\Github\forks\kit\packages\kit\test\apps\basics
bash: cd: C:Githubforkskitpackageskittestappsbasics: No such file or directory
```
The shell eats the `\` because they are not escaped and the path isn't quoted.
This feature request is for a setting to optionally wrap the path with single or double quotes:
`Explorer: Wrap absolute Copy Path file path with quotes`
`"No quotes (default)"`
`"Single"`
`"Double"`
Right now Copy Path gives `C:\Github\forks\kit\packages\kit\test\apps\basics` which would still be the default.
`Single` would give `'C:\Github\forks\kit\packages\kit\test\apps\basics'`
`Double` would give `"C:\Github\forks\kit\packages\kit\test\apps\basics"`
This feature would make it smoother to interact with absolute paths from the Copy Path command on Windows machines/shells.
| help wanted,feature-request,terminal-input | low | Minor |
2,540,389,744 | vscode | On commit: Unknown variable: --vscode-inlineChat-regionHighlight | I saw this when trying to commit a merge commit just now which forced me to use `--no-verify` to unblock myself.
```
src\vs\workbench\contrib\notebook\browser\media\notebookCellChat.css(294,1): Unknown variable: --vscode-inlineChat-regionHighlight
src\vs\workbench\contrib\notebook\browser\media\notebookCellChat.css(309,1): Unknown variable: --vscode-inlineChat-regionHighlight
src\vs\workbench\contrib\notebook\browser\media\notebookCellChat.css(316,1): Unknown variable: --vscode-inlineChat-regionHighlight
All valid variable names are in `build/lib/stylelint/vscode-known-variables.json`
To update that file, run `./scripts/test-documentation.sh|bat.`
``` | bug,debt,notebook | low | Minor |
2,540,390,490 | go | x/tools/go/gcexportdata: drop experimental bundle API | The [gcexportdata](https://pkg.go.dev/golang.org/x/tools/go/gcexportdata) package has two functions, WriteBundle and ReadBundle, that have always been marked as experimental and are not used within x/tools, nor, to my knowledge, anywhere else. The only [match in GitHub](https://github.com/search?q=gcexportdata.WriteBundle&type=code) was a single call from apidiff in the ~~obsolete~~ golang/exp repo (and forks thereof), which I have since updated.
```go
package gcexportdata
func ReadBundle(in io.Reader, fset *token.FileSet, imports map[string]*types.Package) ([]*types.Package, error)
func WriteBundle(out io.Writer, fset *token.FileSet, pkgs []*types.Package) error
```
We propose to drop bundle functionality by making both functions return an error unconditionally.
Related:
- https://github.com/golang/go/issues/69491 | Proposal,Proposal-Accepted,Tools | low | Critical |
2,540,415,895 | pytorch | Facing issue with custom kernel with torch compile | ### 🐛 Describe the bug
```shell
Reason: Illegal getattr invocation stride in strict mode
```
I have a kernel which requires strides.
but when I access the stride inside a torch.autograd.Function, I get graph breaks.
### Error logs
Graph Count: 8
Graph Break Count: 7
Op Count: 32
Break Reasons:
Break Reason 1:
Reason: Illegal getattr invocation stride in strict mode
User Stack:
<FrameSummary file /u/mayank98/scratch/kernel-hyperdrive/khd/scattermoe/torch_implementation.py, line 111 in forward>
<FrameSummary file /u/mayank98/scratch/kernel-hyperdrive/khd/scattermoe/triton_implementation/__init__.py, line 84 in _compute_experts>
<FrameSummary file /u/mayank98/miniconda3/envs/ai/lib/python3.11/site-packages/torch/nn/modules/module.py, line 1562 in _call_impl>
<FrameSummary file /u/mayank98/scratch/kernel-hyperdrive/khd/scattermoe/triton_implementation/__init__.py, line 23 in forward>
<FrameSummary file /u/mayank98/scratch/kernel-hyperdrive/khd/scattermoe/triton_implementation/ops.py, line 345 in scattered_experts>
<FrameSummary file /u/mayank98/scratch/kernel-hyperdrive/khd/scattermoe/triton_implementation/ops.py, line 290 in backward>
<FrameSummary file /u/mayank98/scratch/kernel-hyperdrive/khd/scattermoe/triton_implementation/ops.py, line 189 in group>
Break Reason 2:
### Minified repro
_No response_
### Versions
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 23357 100 23357 0 0 120k 0 --:--:-- --:--:-- --:--:-- 120k
Collecting environment information...
PyTorch version: 2.4.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Red Hat Enterprise Linux 9.4 (Plow) (x86_64)
GCC version: (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Clang version: Could not collect
CMake version: version 3.26.4
Libc version: glibc-2.34
Python version: 3.11.9 (main, Apr 19 2024, 16:48:06) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.14.0-427.22.1.el9_4.x86_64-x86_64-with-glibc2.34
Is CUDA available: True
CUDA runtime version: 12.4.99
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA H100 80GB HBM3
GPU 1: NVIDIA H100 80GB HBM3
GPU 2: NVIDIA H100 80GB HBM3
GPU 3: NVIDIA H100 80GB HBM3
GPU 4: NVIDIA H100 80GB HBM3
GPU 5: NVIDIA H100 80GB HBM3
GPU 6: NVIDIA H100 80GB HBM3
GPU 7: NVIDIA H100 80GB HBM3
Nvidia driver version: 555.42.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 57 bits virtual
Byte Order: Little Endian
CPU(s): 96
On-line CPU(s) list: 0-95
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) Platinum 8468
CPU family: 6
Model: 143
Thread(s) per core: 1
Core(s) per socket: 48
Socket(s): 2
Stepping: 8
CPU(s) scaling MHz: 99%
CPU max MHz: 3800.0000
CPU min MHz: 800.0000
BogoMIPS: 4200.00
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr ibt amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities
L1d cache: 4.5 MiB (96 instances)
L1i cache: 3 MiB (96 instances)
L2 cache: 192 MiB (96 instances)
L3 cache: 210 MiB (2 instances)
NUMA node(s): 2
NUMA node0 CPU(s): 0-47
NUMA node1 CPU(s): 48-95
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] pytorch-triton==3.1.0+5fe38ffd73
[pip3] torch==2.4.1
[pip3] triton==3.0.0
[conda] Could not collect
cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire | triaged,oncall: pt2,module: dynamo,dynamo-autograd-function | low | Critical |
2,540,426,844 | rust | Audit usages of `std::env::*_var` in the compiler | We have a couple instances of `env::*_var` which are now unsafe in edition 2024. They're not necessarily obviously safe, so I've left them with a `FIXME(edition_2024)` -- we should fix them eventually.
https://github.com/rust-lang/rust/blob/28364822410af31bba5c8adac19cbbfcb9b48717/compiler/rustc_llvm/build.rs#L54
https://github.com/rust-lang/rust/blob/28364822410af31bba5c8adac19cbbfcb9b48717/compiler/rustc_feature/src/tests.rs#L6 | C-cleanup,T-compiler | low | Minor |
2,540,444,217 | langchain | Protobuf errors when using langchain-chroma with protobuf >= 4 | ### 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
```python
import chromadb
````
### Error Message and Stack Trace (if applicable)
```
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/src/ai/langchain/cli.py", line 3, in <module>
from ai.langchain.chat import chat
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/src/ai/langchain/chat.py", line 14, in <module>
from ai.langchain.loaders import create_store
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/src/ai/langchain/loaders.py", line 11, in <module>
from ai.chroma import create_store_or_retrieve, delete_collections
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/src/ai/chroma/__init__.py", line 5, in <module>
import chromadb
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/chromadb/__init__.py", line 6, in <module>
from chromadb.auth.token_authn import TokenTransportHeader
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/chromadb/auth/token_authn/__init__.py", line 24, in <module>
from chromadb.telemetry.opentelemetry import (
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/chromadb/telemetry/opentelemetry/__init__.py", line 12, in <module>
from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/opentelemetry/exporter/otlp/proto/grpc/trace_exporter/__init__.py", line 22, in <module>
from opentelemetry.exporter.otlp.proto.grpc.exporter import (
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/opentelemetry/exporter/otlp/proto/grpc/exporter.py", line 39, in <module>
from opentelemetry.proto.common.v1.common_pb2 import (
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/opentelemetry/proto/common/v1/common_pb2.py", line 36, in <module>
_descriptor.FieldDescriptor(
File "/home/paolo/webapps/sparkfabrik/int/labs/ai/rag-platform/.venv/lib/python3.12/site-packages/google/protobuf/descriptor.py", line 553, in __new__
_message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
1. Downgrade the protobuf package to 3.20.x or lower.
2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates
make: *** [Makefile:29: data-reindex] Error 1
```
### Description
Installed dependencies:
```toml
[tool.poetry.dependencies]
python = ">=3.10,<3.13"
slack-bolt = "^1.20.1"
python-dotenv = "^1.0.1"
unstructured = {extras = ["epub", "md", "pdf", "xslx"], version = "^0.15.10"}
nltk = "^3.9.1"
langchain = "^0.3"
langchain-community = "^0.3"
langchain-core = "^0.3"
langchain-text-splitters = "^0.3"
langchain-anthropic = "^0.2"
langchain-chroma = "^0.1"
langchain-openai = "^0.2"
openpyxl = "^3.1.5"
beautifulsoup4 = "^4.12.3"
markdownify = "^0.13.1"
dynaconf = "^3.2.6"
```
### System Info
```shell
System Information
------------------
> OS: Linux
> OS Version: #1 SMP PREEMPT_DYNAMIC Tue, 10 Sep 2024 14:37:32 +0000
> Python Version: 3.12.6 (main, Sep 12 2024, 21:12:04) [GCC 12.2.0]
Package Information
-------------------
> langchain_core: 0.3.5
> langchain: 0.3.0
> langchain_community: 0.3.0
> langsmith: 0.1.125
> langchain_anthropic: 0.2.1
> langchain_chroma: 0.1.4
> langchain_cli: 0.0.31
> langchain_openai: 0.2.0
> langchain_text_splitters: 0.3.0
> langserve: 0.3.0
Optional packages not installed
-------------------------------
> langgraph
Other Dependencies
------------------
> aiohttp: 3.10.5
> anthropic: 0.34.2
> async-timeout: Installed. No version info available.
> chromadb: 0.5.7
> dataclasses-json: 0.6.7
> defusedxml: 0.7.1
> fastapi: 0.115.0
> gitpython: 3.1.43
> gritql: 0.1.5
> httpx: 0.27.2
> jsonpatch: 1.33
> langserve[all]: Installed. No version info available.
> numpy: 1.26.4
> openai: 1.47.0
> orjson: 3.10.7
> packaging: 24.1
> pydantic: 2.9.2
> pydantic-settings: 2.5.2
> PyYAML: 6.0.2
> requests: 2.32.3
> SQLAlchemy: 2.0.35
> sse-starlette: 1.8.2
> tenacity: 8.5.0
> tiktoken: 0.7.0
> tomlkit: 0.12.5
> typer[all]: Installed. No version info available.
> typing-extensions: 4.12.2
> uvicorn: 0.23.2
``` | 🤖:bug,stale,investigate | low | Critical |
2,540,450,180 | deno | Web cache API expirenation is not work? | Version: Deno 1.46.3
It appears that the Web Cache API expiration date cannot be set.
Example
```ts
export const cache = await caches.open("cache");
const cached = await cache.match(req.url);
if (cached) {
console.log(`cache hit ${req.url}`);
return cached;
}
const newResponse = new Response("text", {
headers: { ...res.headers, "Expires": new Date(Date.now() + 10 * 1000).toUTCString(), },
});
await cache.put(req.url, newResponse.clone());
return newResponse;
```
The cache does not disappear over time and hits forever.
Would cli and deploy work differently?
https://deno.com/blog/deploy-cache-api#:~:text=reference%20documentation.-,Cache%20Policy,-By%20default%2C%20cached
| needs investigation | low | Minor |
2,540,462,150 | kubernetes | Pods Not Scaling Up with HPA Despite CPU Utilization Exceeding Target | ### What happened?
I'm using the HPA to scale my pods based on CPU usage. I've set the target CPU utilization at 50%, with a stabilization window of 0. However, my pods are not scaling up, even though the current CPU usage consistently exceeds 50%. This issue persists for over 30 minutes without any scaling activity.
### What did you expect to happen?
The HPA will trigger scale up immediately
### How can we reproduce it (as minimally and precisely as possible)?
Create an OKE cluster and follow this [guide](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/)
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"b6943c3c67cd1e3b8a1269566e755e899ed25ce2", GitTreeState:"clean", BuildDate:"2023-06-23T15:16:54Z", GoVersion:"go1.20.4 4493 X:boringcrypto", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.12", GitCommit:"19d5e4ee03daf5e8fb55a88b1a52d94332435e7e", GitTreeState:"clean", BuildDate:"2023-07-26T10:00:24Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}
</details>
### Cloud provider
<details>
Oracle OKE
</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/autoscaling,needs-triage | low | Minor |
2,540,479,300 | flutter | multicast_dns client is not discovering service on the network on Android devices | ### Steps to reproduce
1. Run the sample flutter code give below on a real Android Device
2. Run the python code on a computer (it will Register a sample service on the network)
3. Make sure computer running python code and the android device are on same network
### Expected results
The service on the network should be discovered and its ip should be displayed
### Actual results
- lookup function is not returning anything on a physical android device : tested on Samsung (Android 12) and OnePlus(Android 14)),
- works on iOS simulator and MacOS, haven't tried it on physical iOS device
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
import 'package:multicast_dns/multicast_dns.dart';
import 'dart:developer' as developer;
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
theme: ThemeData(
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
),
home: const MyHomePage(),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, });
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
Set<String> _hosts = <String>{};
final String name = 'sample._http._tcp.local';
Future<void> _incrementCounter() async {
//TODO: use this on android
// final MDnsClient client = MDnsClient(rawDatagramSocketFactory:
// (dynamic host, int port,
// {bool? reuseAddress, bool? reusePort, int? ttl}) {
// return RawDatagramSocket.bind(host, port,
// reuseAddress: true, reusePort: false, ttl: ttl!);
// });
//TODO: use this on iOS
MDnsClient client = MDnsClient();
await client.start();
developer.log('started');
client.lookup<IPAddressResourceRecord>(ResourceRecordQuery.addressIPv4(name)).
listen((record){
developer.log('found something $record');
setState(() {
_hosts.add(record.address.address);
});
}
).onDone((){
client.stop();
developer.log('stopped');
});
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
const Text(
'InternetAddress of the sample service on the network ',
),
Text(
'$_hosts',
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
child: const Icon(Icons.add),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}
```
```python
#pip install zeroconf
from zeroconf import ServiceInfo, Zeroconf
import socket
def main():
# Get your local IP address
s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
s.connect(("8.8.8.8", 80))
local_ip = s.getsockname()[0]
s.close()
info = ServiceInfo(
"_http._tcp.local.",
"sample._http._tcp.local.",
addresses=[socket.inet_aton(local_ip)],
port=8000,
properties={"path": "/"},
)
zeroconf = Zeroconf()
zeroconf.register_service(info)
try:
input("Press enter to exit...\n\n")
finally:
zeroconf.unregister_service(info)
zeroconf.close()
if __name__ == "__main__":
main()
```
</details>
### Screenshots or Video
_No response_
### Logs
<details open><summary>Logs</summary>
```console
Launching lib/main.dart on SM M215F in debug mode...
✓ Built build/app/outputs/flutter-apk/app-debug.apk
I/ViewRootImpl@9e069d2[MainActivity](17642): [DP] cancelDraw null isViewVisible: true
D/InsetsSourceConsumer(17642): ensureControlAlpha: for ITYPE_NAVIGATION_BAR on com.example.mdns_search/com.example.mdns_search.MainActivity
D/InsetsSourceConsumer(17642): ensureControlAlpha: for ITYPE_STATUS_BAR on com.example.mdns_search/com.example.mdns_search.MainActivity
I/ViewRootImpl@9e069d2[MainActivity](17642): [DP] cancelDraw null isViewVisible: true
[log] started
[log] stopped
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.24.2, on macOS 14.6.1 23G93 darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.93.1)
[✓] Connected device (5 available)
[✓] Network resources
• No issues found!
```
</details>
| platform-android,package,p: multicast_dns,has reproducible steps,P2,team-android,triaged-android,found in release: 3.24,found in release: 3.26 | low | Critical |
2,540,496,457 | godot | Noticable mouse jitter, but only when mouse mode is `Input.MOUSE_MODE_CAPTURED` | ### Tested versions
- Reproducible in: v4.4.dev2.mono.official.97ef3c837, v4.4.dev.custom_build.97ef3c837, v4.3.stable.arch_linux, v4.0.stable.official [92bee43ad], v3.6.stable.official [de2f0f147], v.3.3.stable.official, v.3.2.3.stable.official, v.3.2.2.stable.official
- Not reproducible in: v.3.0.stable.official, v.3.1.stable.official, v.3.2.stable.official, v.3.2.1.stable.official
As for me, this bug in 3.3.stable.official is noticeable more than in 3.2.3.stable.official.
Also I can say nothing about 3.2.2.rc1. It feels between 3.2.1 when there is definitely no such a bug, and from 3.2.3+ where it can be clearly seen.
### System information
Godot v4.4.dev2.mono - Arch Linux #1 SMP PREEMPT_DYNAMIC Thu, 12 Sep 2024 17:21:02 +0000 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU - AMD Ryzen 7 7735HS with Radeon Graphics (16 Threads). 144Hz monitor
### Issue description
It's pretty difficult to explain what's wrong, but it looks like something is wrong. Camera movements are too sharp. For example when you move mouse by 1px, camera immediately changes its rotation by larger amount. It's really noticeable and looks very ugly. As for me it's even better to play my own game when mouse is visible (it's FPS) than with this bug. I'm not really sure, but that may be visible only on high refresh rate screens (like 144hz that I have).
Looks like #54818, but sensitivity doesn't change in this case. Also may be a regression of #45592, because there something also was wrong only when mouse mode is `..._CAPTURED`.
I already tried making my own camera smoothing to fix it and it smoothed camera movement, but didn't fix this issue at all. Only fix is to change mouse mode. Also, enabling physics interpolation seems to make no difference.
### Steps to reproduce
1. Set mouse mode to `Input.MOUSE_MODE_CAPTURED`.
2. Rotate camera with normal speed. Not that high when you see nothing and not that low when everything is almost static.
3 (optional). Set mouse mode to `Input.MOUSE_MODE_VISIBLE` to compare how much smoother that is.
4 (optional). Move camera without rotating to compare how much smoother that is.
Also to see it better, try to visually lock on an object and rotate in such way, that this object will always be in center of screen and just move in circle around it.
Also more noticeable when camera is moving at relatively high speed.
### Minimal reproduction project (MRP)
The smallest reproducible project when you already have Godot Engine is the editor itself. Hold right mouse button and move your mouse to rotate camera (in 3D tab) and move using one of WASD keys, also you can press `Shift` to speed up to make bug more noticeable. But in empty project it's pretty difficult to see the difference, so I made this MRP (you can actually rotate camera if you run it, move using WASD keys, and speed up while holding `Shift`):
[bugjitter3d.zip](https://github.com/user-attachments/files/17085520/bugjitter3d.zip)
If you see some weird glitches, because you opened this project in earlier version of Godot (not 4.4), just run it. If you are getting errors about `screen_relative`, replace it to `relative` in GDScript code.
For Godot 3, just create CSGBox3D or simply rotate camera even without it (this bug still should be seen). | bug,needs testing,topic:input | low | Critical |
2,540,498,304 | node | Could not report code coverage for file in sourcemap | ### Version
v22.9.0
### Platform
```text
N/A
```
### Subsystem
test_runner
### What steps will reproduce the bug?
Create `index.mjs`:
```mjs
export {}
//# sourceMappingURL=index.mjs.map
```
Create `index.mjs.map`:
```mjs
{"version":3,"file":"index.mjs","sourceRoot":"","sources":["index.mjs"],"names":[],"mappings":"AAEA"}
```
Run:
```bash
node --experimental-test-coverage --test index.mjs
```
### How often does it reproduce? Is there a required condition?
Every time.
### What is the expected behavior? Why is that the expected behavior?
Coverage should be reported, or an error explaining why it wasn't is displayed.
### What do you see instead?
```
ℹ Warning: Could not report code coverage. TypeError: Cannot read properties of undefined (reading 'startOffset')
```
### Additional information
CC @nodejs/test_runner | confirmed-bug,coverage,source maps,test_runner | low | Critical |
2,540,501,414 | vscode | Auto-reload local workspace extensions when a file in the extension directory gets saved | <!-- ⚠️⚠️ 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. -->
<!-- Describe the feature you'd like. -->
I am making ample use of the VS Code local workspace extensions feature shipped in v1.89:
https://code.visualstudio.com/updates/v1_89#_local-workspace-extensions
Whenever I make a chance to the extension's source, I have to use the Developer: Reload Window command to make it update.
I think the Reload Extensions button that is in the Extensions pane whenever I install or uninstall extension would also result in the same effect, but that button's underlying action is not exposed as a command that could be found via the command palette AFAIK.
I would like to propose a built-in file save monitor (only when saving a text editor in VS Code not a general file system watcher) that would detect whether the changed file belongs to a directory or a subdirectory of any local workspace extension (`extensionPath` in the `vscode.extensions` API) and reload the extension whenever such a file was changed.
I believe something like this could be also crudely done as an extension itself `vscode.commands.executeCommand` running the `workbench.action.restartExtensionHost` command based on `vscode.workspace.onDidSaveTextDocument` with the downside that it could only reload all extensions this way, not any particular one, so I think a built-in solution would be preferred. | feature-request,extensions | low | Minor |
2,540,517,347 | rust | Tracking Issue for mergeable rustdoc cross-crate info | <!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.
Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.
Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->
This is a tracking issue for the RFC "Mergeable rustdoc cross-crate info" (rust-lang/rfcs#3662).
### About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->
- [x] Implement the RFC (#129337)
- [ ] Add documentation (to Rustdoc Book) -- cc @EtomicBomb
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])
[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide
### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->
- [ ] Consider removing `--merge=shared` and only allow it by not providing a `--merge` flag. This would allow removing the implementation of shared CCI later, once Cargo uses mergeable CCI. https://github.com/rust-lang/rfcs/pull/3662#discussion_r1735147546
### Implementation history
<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
- #129337
- #128252
- #128161 | T-rustdoc,B-unstable,B-RFC-implemented,C-tracking-issue | low | Critical |
2,540,520,851 | godot | Tileset Terrain peering to void cells is unreliable | ### Tested versions
Using 4.3 stable
### System information
Godot v4.3.stable - macOS 14.6.1 - GLES3 (Compatibility) - Apple M2 Pro - Apple M2 Pro (12 Threads)
### Issue description
When using terrains, I often find that when it has to peer with a void/empty cell, the results are unpredictable / poor.
In the examples below, I will be using https://seliel-the-shaper.itch.io/spring-forest.
Here, you can see it has decided that the water is peered with the "dirt" terrain when it meets the void edge of the map.
As you can see in this, the Deep Water is peered with the Dirt terrain:
Now.. Dirt is the first terrain in the set, so I can kinda see why it might "fall back" to that for a void cell?
To me, it feels like it would be more sensible to preserve the "primary" tile for that terrain; in this case full water.
### Steps to reproduce
Seem to be fairly reliable once you have two+ terrains. The edge seems to always be the "first" terrain?
### Minimal reproduction project (MRP)
I cant really produce an MRP right now with this tilset as its copyright...
There is also a chance it might be a "Meat Based Problem" and I'm using Godot incorrectly... | needs testing,topic:2d | low | Minor |
2,540,534,148 | rust | LTO coordinator panics by unwrapping Option::None | ### Code
Discovered this error while fuzzing for https://github.com/rust-lang/rust/issues/81280
I used `cargo watch -- cargo build --profile incremental` for building [this binary crate](https://github.com/HULKs/hulk/tree/6b34bb12bd902dfc737c30d428f883a18e1dbebd/tools/twix), while `touch`-ing random files at random intervals to trigger rebuilds.
Fish script:
```fish
while true
touch (find src | shuf -n1)
sleep 0.(random 1 999)
end
```
### Meta
`rustc --version --verbose`:
```
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7
```
### Error output
```
thread 'coordinator' panicked at compiler/rustc_codegen_llvm/src/back/lto.rs:836:36:
called `Option::unwrap()` on a `None` value
```
<!--
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>
```
called `Option::unwrap()` on a `None` value
stack backtrace:
0: 0x7f5bbd68a3e5 - std::backtrace_rs::backtrace::libunwind::trace::h649ab3318d3445c5
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
1: 0x7f5bbd68a3e5 - std::backtrace_rs::backtrace::trace_unsynchronized::hf4bb60c3387150c3
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2: 0x7f5bbd68a3e5 - std::sys::backtrace::_print_fmt::hd9186c800e44bd00
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:65:5
3: 0x7f5bbd68a3e5 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h1b9dad2a88e955ff
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:40:26
4: 0x7f5bbd6d9eeb - core::fmt::rt::Argument::fmt::h351a7824f737a6a0
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/rt.rs:173:76
5: 0x7f5bbd6d9eeb - core::fmt::write::h4b5a1270214bc4a7
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/mod.rs:1182:21
6: 0x7f5bbd67ef6f - std::io::Write::write_fmt::hd04af345a50c312d
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/io/mod.rs:1827:15
7: 0x7f5bbd68cbd1 - std::sys::backtrace::BacktraceLock::print::h68d41b51481bce5c
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:43:9
8: 0x7f5bbd68cbd1 - std::panicking::default_hook::{{closure}}::h96ab15e9936be7ed
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:269:22
9: 0x7f5bbd68c8ac - std::panicking::default_hook::h3cacb9c27561ad33
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:296:9
10: 0x7f5bb9c93420 - std[1f2242ed6435445e]::panicking::update_hook::<alloc[7b1462a1eb55c293]::boxed::Box<rustc_driver_impl[8683aa37472b7dde]::install_ice_hook::{closure#0}>>::{closure#0}
11: 0x7f5bbd68d59f - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::hce7569f4ca5d1b64
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/boxed.rs:2084:9
12: 0x7f5bbd68d59f - std::panicking::rust_panic_with_hook::hfe205f6954b2c97b
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:808:13
13: 0x7f5bbd68d193 - std::panicking::begin_panic_handler::{{closure}}::h6cb44b3a50f28c44
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:667:13
14: 0x7f5bbd68a8a9 - std::sys::backtrace::__rust_end_short_backtrace::hf1c1f2a92799bb0e
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:168:18
15: 0x7f5bbd68ce54 - rust_begin_unwind
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:665:5
16: 0x7f5bbd6d64a3 - core::panicking::panic_fmt::h3d8fc78294164da7
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panicking.rs:74:14
17: 0x7f5bbd6d652c - core::panicking::panic::hec978767ec2d35ff
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panicking.rs:148:5
18: 0x7f5bbd6d6299 - core::option::unwrap_failed::hba6b08832f9ce30b
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/option.rs:2020:5
19: 0x7f5bbbf72a6b - rustc_codegen_llvm[5ff2375b9bf6d639]::back::lto::thin_lto
20: 0x7f5bbbf6d00b - <rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend as rustc_codegen_ssa[382a85cbfbe8c2f6]::traits::write::WriteBackendMethods>::run_thin_lto
21: 0x7f5bbc1113ce - rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::start_executing_work::<rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend>::{closure#5}
22: 0x7f5bbc10f876 - std[1f2242ed6435445e]::sys::backtrace::__rust_begin_short_backtrace::<<rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend as rustc_codegen_ssa[382a85cbfbe8c2f6]::traits::backend::ExtraBackendMethods>::spawn_named_thread<rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::start_executing_work<rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend>::{closure#5}, core[3cad2706d8bdcdc4]::result::Result<rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::CompiledModules, ()>>::{closure#0}, core[3cad2706d8bdcdc4]::result::Result<rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::CompiledModules, ()>>
23: 0x7f5bbc10f6ad - <<std[1f2242ed6435445e]::thread::Builder>::spawn_unchecked_<<rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend as rustc_codegen_ssa[382a85cbfbe8c2f6]::traits::backend::ExtraBackendMethods>::spawn_named_thread<rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::start_executing_work<rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend>::{closure#5}, core[3cad2706d8bdcdc4]::result::Result<rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::CompiledModules, ()>>::{closure#0}, core[3cad2706d8bdcdc4]::result::Result<rustc_codegen_ssa[382a85cbfbe8c2f6]::back::write::CompiledModules, ()>>::{closure#1} as core[3cad2706d8bdcdc4]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
24: 0x7f5bbd6975fb - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::ha1963004222e7822
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/boxed.rs:2070:9
25: 0x7f5bbd6975fb - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h1086ced1f7c494c2
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/boxed.rs:2070:9
26: 0x7f5bbd6975fb - std::sys::pal::unix::thread::Thread::new::thread_start::ha8af9c992ef0b208
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/pal/unix/thread.rs:108:17
27: 0x7f5bbd466897 - start_thread
28: 0x7f5bbd4eda5c - __GI___clone3
29: 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: rustc 1.81.0 (eeb90cda1 2024-09-04) running on x86_64-unknown-linux-gnu
note: compiler flags: --crate-type bin -C opt-level=3 -C embed-bitcode=no -C incremental=[REDACTED] -C strip=debuginfo
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
end of query stack
thread 'rustc' panicked at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/compiler/rustc_codegen_ssa/src/back/write.rs:2057:17:
/rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/compiler/rustc_codegen_ssa/src/back/write.rs:2057:17: panic during codegen/LLVM phase
stack backtrace:
0: 0x7f5bbd68a3e5 - std::backtrace_rs::backtrace::libunwind::trace::h649ab3318d3445c5
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
1: 0x7f5bbd68a3e5 - std::backtrace_rs::backtrace::trace_unsynchronized::hf4bb60c3387150c3
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2: 0x7f5bbd68a3e5 - std::sys::backtrace::_print_fmt::hd9186c800e44bd00
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:65:5
3: 0x7f5bbd68a3e5 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h1b9dad2a88e955ff
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:40:26
4: 0x7f5bbd6d9eeb - core::fmt::rt::Argument::fmt::h351a7824f737a6a0
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/rt.rs:173:76
5: 0x7f5bbd6d9eeb - core::fmt::write::h4b5a1270214bc4a7
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/mod.rs:1182:21
6: 0x7f5bbd67ef6f - std::io::Write::write_fmt::hd04af345a50c312d
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/io/mod.rs:1827:15
7: 0x7f5bbd68cbd1 - std::sys::backtrace::BacktraceLock::print::h68d41b51481bce5c
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/sys/backtrace.rs:43:9
8: 0x7f5bbd68cbd1 - std::panicking::default_hook::{{closure}}::h96ab15e9936be7ed
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:269:22
9: 0x7f5bbd68c8ac - std::panicking::default_hook::h3cacb9c27561ad33
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:296:9
10: 0x7f5bb9c93420 - std[1f2242ed6435445e]::panicking::update_hook::<alloc[7b1462a1eb55c293]::boxed::Box<rustc_driver_impl[8683aa37472b7dde]::install_ice_hook::{closure#0}>>::{closure#0}
11: 0x7f5bbd68d59f - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::hce7569f4ca5d1b64
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/boxed.rs:2084:9
12: 0x7f5bbd68d59f - std::panicking::rust_panic_with_hook::hfe205f6954b2c97b
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:808:13
13: 0x7f5bba236ae2 - std[1f2242ed6435445e]::panicking::begin_panic::<alloc[7b1462a1eb55c293]::string::String>::{closure#0}
14: 0x7f5bba22f626 - std[1f2242ed6435445e]::sys::backtrace::__rust_end_short_backtrace::<std[1f2242ed6435445e]::panicking::begin_panic<alloc[7b1462a1eb55c293]::string::String>::{closure#0}, !>
15: 0x7f5bba221201 - std[1f2242ed6435445e]::panicking::begin_panic::<alloc[7b1462a1eb55c293]::string::String>
16: 0x7f5bba2b98cd - rustc_middle[ba2289ab3ae064d4]::util::bug::opt_span_bug_fmt::<rustc_span[28a649581f99a5bd]::span_encoding::Span>::{closure#0}
17: 0x7f5bba29f49a - rustc_middle[ba2289ab3ae064d4]::ty::context::tls::with_opt::<rustc_middle[ba2289ab3ae064d4]::util::bug::opt_span_bug_fmt<rustc_span[28a649581f99a5bd]::span_encoding::Span>::{closure#0}, !>::{closure#0}
18: 0x7f5bba29f31b - rustc_middle[ba2289ab3ae064d4]::ty::context::tls::with_context_opt::<rustc_middle[ba2289ab3ae064d4]::ty::context::tls::with_opt<rustc_middle[ba2289ab3ae064d4]::util::bug::opt_span_bug_fmt<rustc_span[28a649581f99a5bd]::span_encoding::Span>::{closure#0}, !>::{closure#0}, !>
19: 0x7f5bb7c3a600 - rustc_middle[ba2289ab3ae064d4]::util::bug::bug_fmt
20: 0x7f5bbc1081d0 - <rustc_codegen_llvm[5ff2375b9bf6d639]::LlvmCodegenBackend as rustc_codegen_ssa[382a85cbfbe8c2f6]::traits::backend::CodegenBackend>::join_codegen
21: 0x7f5bbc1030c3 - <rustc_interface[53a414ae04dc6ffb]::queries::Linker>::link
22: 0x7f5bbbf2d55c - rustc_interface[53a414ae04dc6ffb]::interface::run_compiler::<core[3cad2706d8bdcdc4]::result::Result<(), rustc_span[28a649581f99a5bd]::ErrorGuaranteed>, rustc_driver_impl[8683aa37472b7dde]::run_compiler::{closure#0}>::{closure#1}
23: 0x7f5bbbe7395b - std[1f2242ed6435445e]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[53a414ae04dc6ffb]::util::run_in_thread_with_globals<rustc_interface[53a414ae04dc6ffb]::interface::run_compiler<core[3cad2706d8bdcdc4]::result::Result<(), rustc_span[28a649581f99a5bd]::ErrorGuaranteed>, rustc_driver_impl[8683aa37472b7dde]::run_compiler::{closure#0}>::{closure#1}, core[3cad2706d8bdcdc4]::result::Result<(), rustc_span[28a649581f99a5bd]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[3cad2706d8bdcd
```
</p>
</details>
| I-ICE,T-compiler,C-bug | low | Critical |
2,540,561,986 | godot | Memory leak and crash when creating custom shapes for ShapeCast | ### Tested versions
Reproducible in 4.3 stable and 4.2.2 stable
### System information
Godot v4.3.stable - macOS 14.6.1 - GLES3 (Compatibility) - Apple M1 Pro - Apple M1 Pro (8 Threads)
### Issue description
Attempting to create a Convex or Concave PolygonShape2D makes Godot freeze, until a memory error appears when reaching 86 GB of memory used for Godot, which keeps going up if the app is not forced to quit.
This doesn't occur when selecting any of the premade shapes.
The only error I found on the logs that may be related are the following:
```
ERROR: 1 RID allocations of type 'P12GodotShape2D' were leaked at exit.
USER WARNING: 1 RID of type "CanvasItem" was leaked.
at: _free_rids (servers/rendering/renderer_canvas_cull.cpp:2483)
USER WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: cleanup (core/object/object.cpp:2284)
USER ERROR: 1 resources still in use at exit (run with --verbose for details).
at: clear (core/io/resource.cpp:604)
```
### Steps to reproduce
1. Create a ShapeCast2D
2. For the Shape field, click a Convex or Concave PolygonShape2D
I tested this on an empty project and was able to reproduce just as in my other projects
### Minimal reproduction project (MRP)
N/A | bug,topic:physics,needs testing | low | Critical |
2,540,572,822 | godot | 4.3 Crashes when on preferred platform = wayland + forward plus renderer + Hyprland | ### Tested versions
Reproducable in: Godot v4.3.stable.nixpkgs
### System information
Godot v4.3.stable (77dcf97d8) - NixOS #1-NixOS SMP PREEMPT_DYNAMIC Sun Sep 15 14:57:56 UTC 2024 - Wayland - Vulkan (Forward+) - AMD Radeon 780M (radeonsi, gfx1103_r1, LLVM 18.1.8, DRM 3.58, 6.11.0) - AMD Ryzen 7 7840U w/ Radeon 780M Graphics (16 Threads)
### Issue description
When opening a Forward+ renderer project in Godot Editor 4.3.stable on Hyprland with the editor set to prefer wayland, the editor crashes immediately without showing a window. This doesn't happen on any other render mode, or in X11.
Here's a text file containing the output of
```bash
DEBUG_WAYLAND=1 godot4 --editor --verbose . &> error.txt
```
[error.txt](https://github.com/user-attachments/files/17087831/error.txt)
The most relevant part of the error seems to be
```
Using present mode: Mailbox
ERROR: Wayland client error code 12.
at: _poll_events_thread (platform/linuxbsd/wayland/wayland_thread.cpp:2747)
```
https://github.com/godotengine/godot/blob/6699ae7897658e44efc3cfb2cba91c11a8f5aa6a/platform/linuxbsd/wayland/wayland_thread.cpp#L2747
### Steps to reproduce
My home manager config (contains my install of Hyprland + Godot)
https://github.com/RegularTetragon/home-manager-vael
Commit 92f9245
My NixOS config (contains general drivers, should be unrelated)
https://github.com/RegularTetragon/nixos-config
Commit 925f827
Login to Hyprland
Create a new project in compatibility mode
Editor -> Editor Settings -> Platforms -> Linuxbsd -> Prefer Wayland = true
Restart the editor and open the project again
Change the project from Compatibility to Forward+
Restart the editor and open the project again
Project crashes immediately
### Minimal reproduction project (MRP)
[test-2.zip](https://github.com/user-attachments/files/17087833/test-2.zip)
| bug,platform:linuxbsd,topic:rendering,crash | low | Critical |
2,540,623,392 | rust | Does LLVM's quirk of counting in bits matter to us? | ### Location
In a lot of different places we document an `isize::MAX` limit on object sizes, for example, see this: https://doc.rust-lang.org/std/slice/fn.from_raw_parts.html
### Summary
So, hypothetically, we "only" can have an object countable by LLVM within 64 bits:
https://github.com/rust-lang/rust/blob/55043f067dcf7067e7c6ebccf3639af94ff57bda/compiler/rustc_abi/src/lib.rs#L340-L350
However, hypothetically, we "should" be able to use an object that is `isize::MAX` bytes. These two facts contradict each other, since that suggests we should be able to have an object that is greater than 2^61 bytes. It is hard to validate whether or not LLVM miscompiles this, though, as most computers do not deal in greater than around 56 bits of address space.
Anyone working in HPC is encouraged to let us know?
Honestly, it's not even clear what we mean by "object" here. Allocation, probably? | A-LLVM,T-compiler,A-docs | low | Minor |
2,540,625,936 | godot | Editor freezes, when Control node edit (show/hide) | ### Tested versions
tested on 4.3 stable / 4.4 dev2
### System information
Windows 10
### Issue description
Editor freeze, when i hide this nodes
in console spam -
`Object was deleted while awaiting a callback.`
P.S. finally i can stable reproduce this bug. general issue - sometimes editor freezes, when UI "layout" changes in containers (i.e. show/hide)
### Steps to reproduce
open project, then hide first "PanelContainer" then second
### Minimal reproduction project (MRP)
[srl.zip](https://github.com/user-attachments/files/17088175/srl.zip)
| bug,topic:editor,topic:gui | low | Critical |
2,540,661,698 | pytorch | Profiling Torch.compile (with_stack=True) leads to frozen program with massive memory. | ### 🐛 Describe the bug
I am using gemma-2b with [vllm](https://github.com/vllm-project/vllm). If I torch.compile(fullgraph=False, backend='inductor') and then profile model.generate in vllm using:
```
with torch.profiler.profile(
activities=[torch.profiler.ProfilerActivity.CPU, torch.profiler.ProfilerActivity.CUDA],
with_stack=True,
experimental_config=torch._C._profiler._ExperimentalConfig(verbose=True),
) as prof:
```
the profiler runs forever and shows huge memory load. If I profile with
```
with torch.profiler.profile(
activities=[torch.profiler.ProfilerActivity.CPU, torch.profiler.ProfilerActivity.CUDA],
with_modules=True,
experimental_config=torch._C._profiler._ExperimentalConfig(verbose=True),
) as prof:
```
the job finishes in ~40 seconds.
### Error logs
_No response_
### Minified repro
_No response_
### Versions
torch==2.4.0+cu118
torchmetrics>=1.4.2
vllm @ https://github.com/vllm-project/vllm/releases/download/v0.5.4/vllm-0.5.4+cu118-cp310-cp310-manylinux1_x86_64.whl
vllm-flash-attn @ https://github.com/vllm-project/flash-attention/releases/download/v2.6.1/vllm_flash_attn-2.6.1+cu118-cp310-cp310-manylinux1_x86_64.whl
cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise @ezyang @chauhang @penguinwu | triaged,oncall: profiler,oncall: pt2 | low | Critical |
2,540,672,594 | react | forceUpdate not work in child component GuardGraph | ```
export default function GuardSetting (props:any) {
const [, forceUpdate] = useReducer(x => x + 1, 0);
return (
<Paper sx={{ width: '100%', pt:'1em', }} >
<SettingHeader name={'Launch Guard'}/>
<ReactFlowProvider>
<GuardGraph {...props} forceUpdate={forceUpdate}/>
</ReactFlowProvider>
</Paper>
);
}
```
Is there any more elegant way to refresh GuardGraph without using window.location.reload()?
Thx.
| Status: Unconfirmed,Resolution: Stale | medium | Minor |
2,540,726,263 | kubernetes | WithRoutine loses stack information | https://github.com/kubernetes/kubernetes/blame/v1.31.1/staging/src/k8s.io/apiserver/pkg/server/routine/routine.go#L73-L82 catches a panic in one goroutine and relays the `recover`ed value to another but loses the stack information. The relayed value gives no indication of its origin. | sig/api-machinery,triage/accepted | low | Major |
2,540,742,262 | fastapi | Optional form field not working with test client | ### Discussed in https://github.com/fastapi/fastapi/discussions/12227
<div type='discussions-op-text'>
<sup>Originally posted by **MartinAchtnerAA** September 19, 2024</sup>
### First Check
- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google "How to X in FastAPI" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).
### Commit to Help
- [X] I commit to help with one of those options 👆
### Example Code
```python
from typing import Annotated, Literal, Optional
from fastapi import FastAPI, Form
from fastapi.testclient import TestClient
app = FastAPI()
@app.post("/")
async def read_main(
attribute : Annotated[Optional[Literal["abc", "def"]], Form()]
):
print(attribute)
client = TestClient(app)
data = {}
data["attribute"] = None
response = client.post("/", data=data)
print(response.content)
assert response.status_code == 200
```
### Description
In FastAPI 0.113 .0 the above code passes.
Since version 0.114.0 the response is a 422 status code with error message '{"detail":[{"type":"literal_error","loc":["body","attribute"],"msg":"Input should be \'abc\' or \'def\'","input":"","ctx":{"expected":"\'abc\' or \'def\'"}}]}'
### Operating System
macOS
### Operating System Details
_No response_
### FastAPI Version
0.114.0
### Pydantic Version
2.9.1
### Python Version
3.12.3
### Additional Context
_No response_</div> | question | low | Critical |
2,540,752,732 | flutter | [in_app_purchase] [iOS] Can not load the storekit configure | ### Steps to reproduce
1. Create storekit configuration and add product with certain id
2. Edit scheme and add storekit into scheme
3. Call function queryProductDetails with certain id and not return product
### Expected results
Call function queryProductDetails and return the product which setup in the Storekit configuration file
### Actual results
Call function queryProductDetails and throw storekit_getproductrequest_platform_error
### Code sample
<details open><summary>Code sample</summary>
```dart
[Paste your code here]
```
</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
[Paste your output here]
```
</details>
| c: crash,platform-ios,p: in_app_purchase,package,P2,team-ios,triaged-ios | low | Critical |
2,540,754,161 | vscode | AbstractContextKeyService has been disposed | ```javascript
Error: AbstractContextKeyService has been disposed
at p.contextMatchesRules in src/vs/platform/contextkey/browser/contextKeyService.ts:319:10
at i.createActionGroups in src/vs/platform/actions/common/menuService.ts:285:33
at d.getActions in src/vs/platform/actions/common/menuService.ts:453:25
at h._getValue in src/vs/editor/browser/widget/diffEditor/features/gutterFeature.ts:40:97
at d.r [as value] in src/vs/base/common/observableInternal/utils.ts:132:25
at I.B in src/vs/base/common/event.ts:1242:13
at I.fire in src/vs/base/common/event.ts:1273:9
at I.resume in src/vs/base/common/event.ts:1421:12
at <anonymous> in src/vs/base/common/event.ts:1460:10
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40&bH=62815915-3e6b-41fb-0ad2-d3bc5b736598) | error-telemetry,diff-editor | low | Critical |
2,540,754,231 | vscode | Soft Assertion Failed | ```javascript
Error: Soft Assertion Failed
at k in src/vs/base/common/assert.ts:43:21
at new l in out/vs/workbench/workbench.desktop.main.js:710:66180
at <anonymous> in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:109:6
at Array.map (<anonymous>)
at b._runFn in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:107:69
at b.j in src/vs/base/common/observableInternal/autorun.ts:196:10
at b.endUpdate in src/vs/base/common/observableInternal/autorun.ts:237:10
at c.finish in src/vs/base/common/observableInternal/base.ts:372:13
at b in src/vs/base/common/observableInternal/base.ts:306:6
at d.value in out/vs/workbench/workbench.desktop.main.js:710:69329
at l.B in src/vs/base/common/event.ts:1242:13
at l.C in src/vs/base/common/event.ts:1253:9
at l.fire in src/vs/base/common/event.ts:1277:9
at d.value in src/vs/editor/browser/widget/codeEditor/codeEditorWidget.ts:1721:38
at l.B in src/vs/base/common/event.ts:1242:13
at l.fire in src/vs/base/common/event.ts:1273:9
at v.s in src/vs/editor/common/viewModelEventDispatcher.ts:64:18
at v.endEmitViewEvents in src/vs/editor/common/viewModelEventDispatcher.ts:109:8
at <anonymous> in src/vs/editor/common/viewModel/viewModelImpl.ts:412:27
at listener in src/vs/editor/common/model/textModel.ts:236:38
at l.B in src/vs/base/common/event.ts:1242:13
at l.fire in src/vs/base/common/event.ts:1273:9
at oe.endDeferredEmit in src/vs/editor/common/model/textModel.ts:2512:23
at K.pushEditOperations in src/vs/editor/common/model/textModel.ts:1278:23
at w.updateModel in src/vs/editor/common/services/modelService.ts:384:9
at P.updateTextEditorModel in src/vs/workbench/common/editor/textEditorModel.ts:207:22
at P.Gb in src/vs/workbench/services/textfile/common/textFileEditorModel.ts:572:9
at P.Eb in src/vs/workbench/services/textfile/common/textFileEditorModel.ts:534:9
at P.Db in src/vs/workbench/services/textfile/common/textFileEditorModel.ts:464:16
at async P.resolve in src/vs/workbench/services/textfile/common/textFileEditorModel.ts:302:3
at async n.W in src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts:421:4
at async n.U in src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts:327:3
at async Object.factory in src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts:166:6
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40&bH=83165f02-78c5-2db6-bf7b-6d13cb1a92f6) | error-telemetry,diff-editor | low | Critical |
2,540,834,474 | ollama | How to use embedding models from huggingface hub? | Hi thanks for the lib! I want to use some embedding models (arch is bert) from hf hub. I have tried gguf, but the converter says bert arch cannot be converted to that. I have also tried directly have a modelfile to import safetensors, but it says `Error: unsupported content type: unknown` | feature request | low | Critical |
2,540,892,041 | excalidraw | Unable to search the Help modal | **Problem**
I noticed that after implementing the "Find on Canvas" feature, it has become impossible to search for a specific keyboard shortcut in the "Help" modal using the browser's "Find in Page" shortcut.
This issue seems to have arisen because the event appears to be intercepted by the custom implementation.
**Expected**
"Find on canvas" should be triggered only while you're focusing the canvas, right? | bug | low | Minor |
2,540,967,493 | node | parallel/test-worker-message-port-infinite-message-loop is flaky | ### Test
test-worker-message-port-infinite-message-loop
### Platform
Linux x64
### Console output
```console
---
duration_ms: 104.844
exitcode: 1
severity: fail
stack: |-
node:internal/event_target:1090
process.nextTick(() => { throw err; });
^
AssertionError [ERR_ASSERTION]: hit 10001 loop iterations
at MessagePort.<anonymous> (/home/iojs/build/workspace/node/test/parallel/test-worker-message-port-infinite-message-loop.js:22:3)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
Node.js v23.0.0-pre
...
```
### Build links
- https://ci.nodejs.org/job/node-test-commit-linux/60803/nodes=rhel8-x64/testReport/junit/(root)/parallel/test_worker_message_port_infinite_message_loop/
### Additional information
_No response_ | flaky-test,linux | low | Critical |
2,540,971,119 | neovim | undo region, multibuffer (many buffers stitched together as one virtual buffer) | ### Problem
The ability to select a region of the file (probably via visual selection would be most popular), and then undo only operations that affected that region.
That is, make it possible to do some changes in some file region, move to another part of the file, make other changes, and then undo just the changes in the first part.
A classical use case is adding debug. prints in different areas of a file. Currently, one has to manually revert any debugging changes made in each region once the problem is determined to be somewhere else.
I realize this is "out there" but I find myself missing this feature frequently enough to at least ask.
### Expected behavior
Having some variant of `u` and/or `U` which would apply only to the currently selected region. The key binding is the least of the problem here. Undo would be linear (reverse order of changes) for all operations that affected the region. For operations that also had impact outside the region, it is a question whether to include them or not; I tend towards "yes" but that might need to be configured or controlled somehow. | enhancement,complexity:high,gsoc,editor-state,editor | low | Critical |
2,540,994,554 | fastapi | OpenAPI servers not being returned according how the docs say they should be | ### Discussed in https://github.com/fastapi/fastapi/discussions/12226
<div type='discussions-op-text'>
<sup>Originally posted by **mzealey** September 19, 2024</sup>
### First Check
- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google "How to X in FastAPI" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).
### Commit to Help
- [X] I commit to help with one of those options 👆
### Example Code
```python
from fastapi import FastAPI
app = FastAPI()
# you can add a test endpoint here or not - same bug either way
```
### Description
```
$ curl localhost:8$ curl localhost:8000/openapi.json
{"openapi":"3.1.0","info":{"title":"FastAPI","version":"0.1.0"},"paths":{}}
```
According to the documentation of the `servers` parameter in FastAPI:
> If the servers list is not provided, or is an empty list, the default value would be a dict with a url value of /.
(assuming that `root_path_in_servers = True` (the default))
Clearly this is not happening.
### Operating System
Linux
### Operating System Details
_No response_
### FastAPI Version
0.110.3 (but according to github code seems to be in latest also)
### Pydantic Version
2.5.3
### Python Version
Python 3.10.12
### Additional Context
_No response_</div> | question | low | Critical |
2,541,016,265 | ui | [bug]: documentation wrong regarding adding next-themes | ### Describe the bug
The enabling dark-mode section in the documentation [here](https://ui.shadcn.com/docs/dark-mode/next) shows the way to enable dark-mode by installing next-themes.
and it says "create a new file with the name ThemeProvider and add the 'use client' directive there".
Now there's no need for that because ThemeProvider from next-themes is already a client component.
Doing the method described in the docs causes the error:
```
app-index.js:33 Warning: Extra attributes from the server: class,style
at html
at RootLayout (Server)
at RedirectErrorBoundary... etc
```
Read the section of this in docs of next-themes [here](https://github.com/pacocoursey/next-themes?tab=readme-ov-file#with-app)
They say:
> Note that ThemeProvider is a client component, not a server component.
### Affected component/components
everything
### How to reproduce
Do the exact same steps described in the docs [here](https://ui.shadcn.com/docs/dark-mode/next).
side note: stackbilitz may not show the error
### Codesandbox/StackBlitz link
https://stackblitz.com/edit/next-themes-shadcnui?file=app%2Flayout.tsx
### Logs
```bash
app-index.js:33 Warning: Extra attributes from the server: class,style
at html
at RootLayout (Server)
at RedirectErrorBoundary (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…@18.3.1/node_modules/next/dist/client/components/redirect-boundary.js:74:9)
at RedirectBoundary (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…18.3.1/node_modules/next/dist/client/components/redirect-boundary.js:82:11)
at NotFoundErrorBoundary (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…18.3.1/node_modules/next/dist/client/components/not-found-boundary.js:76:9)
at NotFoundBoundary (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…8.3.1/node_modules/next/dist/client/components/not-found-boundary.js:84:11)
at DevRootNotFoundBoundary (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…e_modules/next/dist/client/components/dev-root-not-found-boundary.js:33:11)
at ReactDevOverlay (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…/next/dist/client/components/react-dev-overlay/app/ReactDevOverlay.js:87:9)
at HotReload (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…dist/client/components/react-dev-overlay/app/hot-reloader-client.js:321:11)
at Router (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…react@18.3.1/node_modules/next/dist/client/components/app-router.js:207:11)
at ErrorBoundaryHandler (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…ct@18.3.1/node_modules/next/dist/client/components/error-boundary.js:113:9)
at ErrorBoundary (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…t@18.3.1/node_modules/next/dist/client/components/error-boundary.js:160:11)
at AppRouter (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…react@18.3.1/node_modules/next/dist/client/components/app-router.js:585:13)
at ServerRoot (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…act@18.3.1__react@18.3.1/node_modules/next/dist/client/app-index.js:112:27)
at Root (webpack-internal:///(app-pages-browser)/./node_modules/.pnpm/next@14.2.13_r…act@18.3.1__react@18.3.1/node_modules/next/dist/client/app-index.js:117:11)
```
```
### System Info
tested on Google chrome, firefox, Brave browser.
### Before submitting
- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues | bug | low | Critical |
2,541,025,544 | godot | Clarify that secure websocket connections need valid certiifcates on Web | ### Tested versions
4.3
4.3.dev2
4.3.custom_build.nothreads
### System information
Any OS, wasm32
### Issue description
When there are SSL issues while connecting a websocket, Godot doesn't provide any useful output to the user. The current output is `WebSocket connection to <url> failed:`.
**Solution:** There should be a note of this in the documentation, and/or a friendlier error message.
<details>
<summary>Old Description (Resolved)</summary>
Trying to use websockets always results in the error `WebSocket connection to <url> failed:`.
It works perfectly fine on any other platform's native builds.
Surprisingly, the **server is accepting a connection**, but the client never connects, resulting in an error on the server side as soon as the connection drops.
### Steps to reproduce
- Open Devtools
- ~~Go to swarkin.github.io/wsclicker/~~ Not available anymore, the issue has been identified in this discussion.
- Notice error in console `WebSocket connection to 'wss://srv.kackadu.de:25569/' failed:` with no information
Line where the connection is started: https://github.com/Swarkin/wsclicker/blob/main/client/client.gd#L35
### Minimal reproduction project (MRP)
I do not have the time to make a MRP but this is the project that has the issue: https://github.com/Swarkin/wsclicker
It is split into server and client folders and has an export configuration that is used for exporting. (Note: Exporting in release mode for web does not work and instead falls back to a debug build.)
</details> | discussion,platform:web,documentation,needs testing,topic:network | low | Critical |
2,541,061,343 | pytorch | an illegal memory access was encountered global exception | ### 🐛 Describe the bug
/tmp/tmpvmyol3082.jpg v1.4 2.0
Error CUDA error: an illegal memory access was encountered
global exception: local variable 'output' referenced before assignment
### Versions
/tmp/tmpvmyol3082.jpg v1.4 2.0
Error CUDA error: an illegal memory access was encountered
global exception: local variable 'output' referenced before assignment
pls solve this | needs reproduction,triaged | low | Critical |
2,541,061,538 | godot | Evaluate selection (Ctrl+Shift+E) does not parse underscores | ### Tested versions
v4.3.1.rc.custom_build [d40fc50f0]
4.4 on latest master
### System information
Godot v4.3.1.rc (d40fc50f0) - Manjaro Linux #1 SMP PREEMPT_DYNAMIC Wed Aug 7 16:19:28 UTC 2024 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7900 XT (RADV NAVI31) - AMD Ryzen 9 7900X 12-Core Processor (24 Threads)
### Issue description
In the script editor, selecting an expression and pressing the shortcut for Evaluate Selection does just what the name suggests, e.g. selecting `10+24` will transform the selection into `34`. However, for larger numbers, or any number where you put underscores for readability, e.g. `500+10_000`, all characters starting from the underscore are ignored, which results in `510` instead of `10500`.
### Steps to reproduce
* Type an expression in the script editor, with one number containing an underscore.
* Press the Evaluate Selection shortcut (or select it from the context menu).
* The result will not consider any characters after the underscore and will simply remove them.
### Minimal reproduction project (MRP)
N/A | enhancement,topic:core,usability | low | Minor |
2,541,079,767 | ollama | InternVL 2.0 models | The models are listed here:
https://huggingface.co/collections/OpenGVLab/internvl-20-667d3961ab5eb12c7ed1463e
1B: https://huggingface.co/OpenGVLab/InternVL2-1B
2B: https://huggingface.co/OpenGVLab/InternVL2-2B
4B: https://huggingface.co/OpenGVLab/InternVL2-4B
8B: https://huggingface.co/OpenGVLab/InternVL2-8B
26B: https://huggingface.co/OpenGVLab/InternVL2-26B
40B: https://huggingface.co/OpenGVLab/InternVL2-40B
76B: https://huggingface.co/OpenGVLab/InternVL2-Llama3-76B | model request | low | Minor |
2,541,106,204 | rust | Tracking Issue for secure random data generation in `std` | Feature gate: `#![feature(random)]`
This is a tracking issue for secure random data generation support in `std`.
Central to this feature are the `Random` and `RandomSource` traits inside `core::random`. The `Random` trait defines a method to create a new random value of the implementing type from random bytes generated by a `RandomSource`. `std` also exposes the platform's secure random number generator via the `DefaultRandomSource` type which can be conveniently access via the `random::random` function.
### Public API
```rust
// core::random
pub trait RandomSource {
fn fill_bytes(&mut self, bytes: &mut [u8]);
}
pub trait Random {
fn random(source: &mut (impl RandomSource + ?Sized)) -> Self;
}
impl Random for bool { ... }
impl Random for /* all integer types */ { ... }
// std::random (additionally)
pub struct DefaultRandomSource;
impl RandomSource for DefaultRandomSource { ... }
pub fn random<T: Random>() -> T { ... }
```
### Steps / History
- [x] ACP: https://github.com/rust-lang/libs-team/issues/393
- [x] Implementation: #129201
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR
### Unresolved Questions
- Naming: the ACP used `gen_bytes` and `DefaultRng`, the implementation PR uses `fill_bytes` and `DefaultRandomSource` (see arguments [pro `gen_bytes`](https://github.com/rust-lang/rust/pull/129120#issuecomment-2291690304) and [pro `fill_bytes`](https://github.com/rust-lang/rust/pull/129120#issue-2467909370))
- Concerns listed at https://github.com/rust-lang/libs-team/issues/393#issuecomment-2563932047 should be addressed
[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
| T-libs-api,C-tracking-issue | medium | Critical |
2,541,112,572 | rust | Tracking issue for removing unnecessary `ty::Const::{normalize,eval}` calls from the type system | We want to remove calls to `ty::Const::{normalize,eval,eval_to_*}` because they won't work correctly with future reformulations of GCE, and because they're unnecessary with non-GCE consts. This issue tracks doing that so I won't forget. Boxy can probably write more motivation here idk
Boxy rationale:
> with `min_generic_const_args` and `associated_const_equality` featuers normalization of type system constants will be behaving much more like types. They'll return nested goals, access in scope whjere clauses such as `T: Trait<ASSOC = 10>` in order to normalize instead of simply "evaluating".
>
> This means that the only correct way to normalize a `ty::Const` will be to use the "normal" normalization routines such as `normalize_erasing_regions` or `infcx/ocx/fcx.normalize`. With that in mind all of the `eval_x` and `normalize` methods on `ty::Const` become massive footguns as they are never correct to use.
- [x] Remove eval calls from codegen (#130644)
- [ ] Replace calls to `eval_bits` with `try_to_bits`, which I forgot in codegen lol
- [x] Normalize writeback results (#130645)
- [x] Replace calls to `eval` from `mir_build` and `pattern_analysis` in now that writeback results are normalized (#130715)
- [x] Add `structurally_resolve_const` for use in `FnCtxt`/`hir_typeck` (#130714)
- [x] Replace calls to `eval_*` with `structurally_resolve` + `try_to_*` in hir typeck
- [ ] Audit remaining calls to `eva;/normalize` post-borrowck, replacing them with their `try_to_*` variants + possibly normalizing depending on the source of the const.
More:
* #130712
cc @BoxyUwU | A-const-generics,T-types | low | Major |
2,541,119,237 | vscode | Ghost text flickers before suggestions show | Repro:
1. At this line https://github.com/microsoft/vscode/blob/90a07a11c27b2dcbf14cb0b01902b4f8aa32887d/src/vs/editor/browser/services/hoverService/hoverWidget.ts#L52
2. Press enter
3. Press `r`, 🐛 ghost text appears briefly then suggestions show up and invalidate it
If there's completion providers in progress, we should wait to show ghost text so we don't flicker the suggestion and cause noise. | polish,inline-completions | low | Minor |
2,541,120,423 | vscode | Do not present ghost text when code is deleted or undone | This is my main annoyance with ghost text, when I delete text I frequently end up accidentally triggering ghost text again, then undo and it fills again. Here are some cases when trying to put them together just now, but there is a case where I've accidentally triggered the ghost text ~3x times before I intentionally overrode my muscle memory and pressed escape to dismiss the ghost text.
## I want to delete the line and indent
1. Select line (end, shift+home)
2. Backspace
3. Tab, 🐛 ghost text is filled, not indenting
1. At this line https://github.com/microsoft/vscode/blob/90a07a11c27b2dcbf14cb0b01902b4f8aa32887d/src/vs/editor/browser/services/hoverService/hoverWidget.ts#L52
2. Press enter
3. Press r, `eturn` ghost text appears
4. Press backspace, 🐛 `return` ghost text appears before being invalidated by a new request
This particular case where we keep old suggestions around means that the editor is less deterministic and slower to use. If I press backspace and tab, it will either complete the ghost text or indent, depending on how quickly I type 😱
## Ghost text remains when de-indenting
1. In a markdown file
2. Tab to indent after a list item, ghost text shows
3. Shift+tab or backspace, 🐛 ghost text remains
| papercut :drop_of_blood:,inline-completions | low | Major |
2,541,123,751 | PowerToys | Workspace Shortcut Icon Lost After Temp Folder Cleanup | ### Microsoft PowerToys version
0.84.1
### Installation method
GitHub
### Running as admin
No
### Area(s) with issue?
Workspaces
### Steps to reproduce
Open PowerToys and configure a Workspace.
Save the Workspace settings.
Check the desktop; a shortcut for the Workspace is created.
Observe that the icon for the shortcut is stored at %USERPROFILE%\AppData\Local\Temp\{unique-ID}.ico.
Clear the Temp folder.
Notice that the icon for the Workspace shortcut is missing or broken.
### ✔️ Expected Behavior
The Workspace shortcut icon should be stored in a permanent location, ensuring that it remains intact even after the Temp folder is cleaned.
### ❌ Actual Behavior
The Workspace shortcut icon is stored in the Temp folder, which causes it to be deleted when the Temp folder is cleaned, resulting in a missing or broken icon on the desktop shortcut.
### Other Software
_No response_ | Issue-Bug,Help Wanted,Needs-Triage,Product-Workspaces | low | Critical |
2,541,134,011 | godot | Vulkan Initialization Failure - Missing libspeechd.so.2 | ### Tested versions
Godot_v4.3-rc3_linux.x86_64
### System information
Arch linux
Intel® Core™ i5-3470S × 4
8 gb ddr3 ram
graphics:NV106
### Issue description
I'm experiencing an issue when launching Godot on my Linux system. The error indicates that the libspeechd.so.2 shared object file is missing, which prevents Vulkan from initializing properly
### Steps to reproduce
```
libspeechd.so.2: cannot open shared object file: No such file or directory
ERROR: Condition "err != VK_SUCCESS" is true. Returning: ERR_CANT_CREATE
at: _initialize_devices (drivers/vulkan/rendering_context_driver_vulkan.cpp:495)
ERROR: Condition "err != OK" is true. Returning: err
at: initialize (drivers/vulkan/rendering_context_driver_vulkan.cpp:600)
ERROR: Could not initialize vulkan
at: DisplayServerWayland (platform/linuxbsd/wayland/display_server_wayland.cpp:1361)
ERROR: Can't create the Wayland display server.
at: create_func (platform/linuxbsd/wayland/display_server_wayland.cpp:1311)
ERROR: Unable to create DisplayServer, all display drivers failed.
Use "--headless" command line argument to run the engine in headless mode if this is desired (e.g. for continuous integration).
at: setup2 (main/main.cpp:2765)
```
### Minimal reproduction project (MRP)
There is no godot project | platform:linuxbsd,topic:rendering,needs testing | low | Critical |
2,541,151,126 | tauri | [bug] Tauriv2 Windows 10 borderless window has a black line at the top | ### Describe the bug
When using a borderless window on Windows 10 with Tauriv2, there's a black line appearing at the top of the window. This line seems to be part of the window's rendering, even though it should be completely borderless.
### Reproduction
_No response_
### Expected behavior
_No response_
### Full `tauri info` output
```text
✔ OS: Windows 10.0.22631 x86_64 (X64)
✔ WebView2: 128.0.2739.79
✔ MSVC: Visual Studio Community 2022
✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
✔ node: 20.17.0
✔ npm: 10.8.2
[-] Packages
✔ tauri 🦀: 2.0.0-rc.15
✔ tauri-build 🦀: 2.0.0-rc.12
✔ wry 🦀: 0.43.1
✔ tao 🦀: 0.30.1
✖ @tauri-apps/api: not installed!
✔ @tauri-apps/cli: 2.0.0-rc.16
[-] Plugins
✔ tauri-plugin-shell 🦀: 2.0.0-rc.3
✖ @tauri-apps/plugin-shell: not installed!
[-] App
✔ build-type: bundle
✖ CSP: unset
✔ frontendDist: ../src
```
### Stack trace
_No response_
### Additional context
_No response_ | type: bug,platform: Windows,status: needs triage | low | Critical |
2,541,157,231 | go | x/tools/gopls: rename package decl fails in CLI | The rename package feature appears not to be working either in the CLI nor in Emacs+eglot:
```
xtools$ cat a/a.go
package a
xtools$ gopls rename -diff ./a/a.go:#9 b
--- /Users/adonovan/w/xtools/a/a.go.orig
+++ /Users/adonovan/w/xtools/a/a.go
@@ -1 +1 @@
-package a
+package b
gopls: getFile: file:///Users/adonovan/w/xtools/a: read /Users/adonovan/w/xtools/a: is a directory
xtools$ echo $?
2
```
It is working from VS Code though.
Also, it is [undocumented](https://github.com/golang/tools/blob/master/gopls/doc/features/transformation.md#refactorrename-rename). I've split this out as https://github.com/golang/go/issues/69624. | Documentation,gopls,Refactoring | low | Major |
2,541,168,890 | terminal | Preview `1.22.2362.0` breaks Terminal.Gui apps | ### Windows Terminal version
1.22.2362.0
### Windows build number
10.0.26120.0
### Other Software
Terminal.Gui - any version
### Steps to reproduce
- Run `UICatalog` from the [Terminal.Gui](https://github.com/gui-cs/Terminal.Gui) solution.
- Start any Scenario
- Exit that Scenario
Each of these is like running a Termina.Gui app afresh.
The same thing can be reproduced by just running ` .\UICatalog\bin\Debug\net8.0\UICatalog.exe` and exiting repeatedly.
### Expected Behavior
### Actual Behavior
Note the bottom of the terminal is corrupt with prior content and the new instance of the app is not getting the correct terminal dimensions (too small). | Product-Conpty,Area-Server,Issue-Bug,Product-Terminal,Priority-3 | low | Critical |
2,541,179,587 | rust | Tracking Issue for `peek_index` | <!--
Thank you for creating a tracking issue!
Tracking issues are for tracking a feature from implementation to stabilization.
Make sure to include the relevant RFC for the feature if it has one.
If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->
- ACP https://github.com/rust-lang/libs-team/issues/435#issuecomment-2356672385
- PR https://github.com/rust-lang/rust/pull/130682
Feature gate: `#![feature(peek_index)]`
This is a tracking issue for the new `peek_index` function on the Enumerate iterator.
<!--
Include a short description of the feature.
-->
### Public API
<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->
```rust
let e = vec![1, 2, 3].into_iter().enumerate();
assert_eq!(e.peek_index(), 0);
e.next();
assert_eq!(e.peek_index(), 1);
```
### Steps / History
- Created ACP issue.
- Opened pull request following the ACP approval.
<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->
<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.
If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:
A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->
### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.
It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->
- None yet.
[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
| T-libs-api,C-tracking-issue | low | Minor |
2,541,197,840 | godot | Select property button in TileSet Paint Editor is not toggleable | ### Tested versions
Reproducible in: 4.3.1.dev [ff9bc04223] and 4.3 stable release
### System information
Godot v4.3.1.rc (ff9bc0422) - macOS 15.0.0 - Vulkan (Forward+) - integrated Apple M1 Max - Apple M1 Max (10 Threads)
### Issue description
In TileSet editor, the "Select a property editor" button is not toggleable. Clicking the button second time won't close the popup. It is a minor issue since the popup can be closed when clicking empty space.
Also, selecting the same property type won't close the popup.
### Steps to reproduce
1. Add a TileMap or TileMapLayer node in a new scene
2. Create a new TileSet
3. Focus on the TileSet editor
4. Create an atlas with icon.svg
5. Click to switch to Paint mode
6. Click the button "Select a property editor"
7. Click the button second time
Expect it to close when the popup is visible. Currently, I can click empty space to close the popup.
https://github.com/user-attachments/assets/0c47eef3-f1b2-4725-a14a-c35a51d1a5db
### Minimal reproduction project (MRP)
N/A | bug,topic:editor,usability,topic:gui | low | Minor |
2,541,205,882 | rust | Stabilisation of ARM AES intrinsics missing from 1.72 release notes | ### Location
Both:
- https://blog.rust-lang.org/2023/08/24/Rust-1.72.0.html
- https://github.com/rust-lang/rust/releases/tag/1.72.0
### Summary
If you go to https://doc.rust-lang.org/core/arch/aarch64/fn.vaesdq_u8.html that reports it was stabilised in 1.72. However, it is not mentioned in:
- https://blog.rust-lang.org/2023/08/24/Rust-1.72.0.html
- https://github.com/rust-lang/rust/releases/tag/1.72.0
Naturally I'm not expecting these to be altered post-hoc, but I feel there might be a process improvement here for ensuring [stdarch](https://github.com/rust-lang/stdarch) changes are reflected in the release notes? | O-Arm,T-libs-api,A-docs,T-release | low | Minor |
2,541,233,773 | pytorch | [RFC] Composable parallel documentation | ### 📚 The doc issue
User requested it here:
https://github.com/pytorch/PiPPy/issues/1026#issuecomment-2365469797
Opening this issue as a task checker.
@wconstab @H-Huang @tianyu-l
### Suggest a potential alternative/fix
Before that, you can refer to the `parallelize_llama` implementation in torchtitan:
https://github.com/pytorch/torchtitan/blob/main/torchtitan/parallelisms/parallelize_llama.py
cc @XilunWu @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o | oncall: distributed | low | Minor |
2,541,235,897 | godot | Crashes occur randomly in 2D editor on Mac OS (godot 4.3) | ### Tested versions
v4.3.stable.official [77dcf97d8]
### System information
Godot v4.3.stable - macOS 15.0.0 - Vulkan (Mobile) - integrated Apple M2 - Apple M2 (8 Threads)
### Issue description
When i'm editing my _TileMapLayer_ my game the software crashes sometimes _(it happened **2 times** in 30 minutes ~)_
### Steps to reproduce
Editing the tile map layer without saving for a while may crash the software on MacOs 15
### Minimal reproduction project (MRP)
[utm.zip](http://github.com/user-attachments/files/17091034/upthemountain.zip)
```[tasklist]
### Tasks
```
| bug,needs testing,crash,topic:2d | low | Critical |
2,541,248,368 | pytorch | Linear Sum Assignment | ### 🚀 The feature, motivation and pitch
It would be great if a PyTorch linear sum assignment solver function could be implemented. I am working on an edge detection algorithm for deep learning and have needed to use SciPy's scipy.optimize.linear_sum_assignment() function for computing the lowest cost 1-to-1 matching between an edge prediction and an edge target. The linear sum assignment solver (LAP) was supposed to be used for simultaneous edge learning and alignment (see SEAL by Zhiding Yu et al.) and for computing maximum F-measure at optimal dataset scale; however, I've had to scrap most of my work due to the long computation times. Computation times have proven to take much longer when tensor resolutions are large; however, large resolutions are preferred since preserving edge information is easier with more data. Not sure how much speed-up can be obtained for this polynomial time problem but I wanted to request the feature.
### Alternatives
_No response_
### Additional context
Here is a basic example of 1-to-1 edge matching using the SciPy linear sum assignment solver, which computes the lowest cost optimal matching between prediction and target binary maps:
```
import torch
from scipy.optimize import linear_sum_assignment
# Dummy pred and target
pred = torch.randint(0, 2, size=(640, 640))
target = torch.randint(0, 2, size=(640, 640))
# Extract edge indices
V = torch.argwhere(pred == 1).float()
W = torch.argwhere(target == 1).float()
# Compute euclidean distance cost matrix, reduce the costs, and recover the optimal indices
eucl_dist_cost_matrix = torch.cdist(V, W)
row_ind, col_ind = linear_sum_assignment(eucl_dist_cost_matrix)
matched_V = V[row_ind]
# Recover the optimal prediction
optimal_pred = torch.zeros_like(pred)
optimal_pred[matched_V[:, 0], matched_V[:, 1]] = 1
```
cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @vincentqb @janeyx99 @crcrpar | module: nn,module: optimizer,triaged | low | Minor |
2,541,266,388 | ant-design | Antd Datepicker format value before minDate | ### Reproduction link
[](https://stackblitz.com/edit/react-bn65y6?file=demo.tsx)
### Steps to reproduce
Set a DatePicker like this :
```
<DatePicker
minDate={dayjs('011900', 'MMYYYY')} // <-- You set the minDate to be January 1900
format={[
'MMMM YYYY', // <-- You want the date formatted like "January 1995"
'MMYYYY', // <-- You want the user to be able to write "011995" (but not something before January 1900)
'DDMMYYYY', // <-- You want the user to be able to write "01011995"
]}
/>
```
Then try typping "01011995" (do not copy/paste)
Just after finishing typing "010119" the value is wrongly formated as "January 0119" (so we're unable to finish typing "95")
### What is expected?
It should not transform "010119" to "January 0119" so the user can finish typing a "valid" date like "01011995".
### What is actually happening?
"010119" is wrongly formated to "January 0119" and we're unable to finish writing our date
| Environment | Info |
| --- | --- |
| antd | 5.20.6 |
| React | 18.3.1 |
| System | Windows 10 |
| Browser | Chrome |
---
I know it's a very specific bug but many thanks for the help
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | Inactive,unconfirmed | low | Critical |
2,541,267,091 | PowerToys | Keyboard manager from alt +A to ctrl left + A isn't working | ### Microsoft PowerToys version
0.84.1
### Installation method
PowerToys auto-update
### Running as admin
Yes
### Area(s) with issue?
Keyboard Manager
### Steps to reproduce
[settings_133715099785283014.json](https://github.com/user-attachments/files/17091362/settings_133715099785283014.json)
Attached backup file renamed from ptb to json.
When trying to use alt+a to select all and alt+c to copy ... it's not working.
Note it was working before,
This is running on version 23H2 OS build 22631.4169
### ✔️ Expected Behavior
The copy. past to work
### ❌ Actual Behavior
alt isn't mapped
### Other Software
_No response_ | Issue-Bug,Needs-Triage,Status-Reproducible | low | Minor |
2,541,283,071 | PowerToys | Keyboard Manager: Remapping a shortcut using "right Ctrl"/⇨ with CAN/CSA Z243.200 fails (detected as "VK 223") | ### Microsoft PowerToys version
0.84.1
### Installation method
GitHub, PowerToys auto-update
### Running as admin
No
### Area(s) with issue?
Keyboard Manager
### Steps to reproduce
In Keyboard Manager:
1. Ensure that the layout is Canadian multilingual standard
2. Click Remap a shortcut
3. At the bottom, select Add a shortcut remapping
4. Click the pencil shortcut (left)
5. Toggle "Authorize simultaneous presses" on
6. Depress the bottom right key (located where the right Ctrl usually is)
7. Press any key, for example <kbd>L</kbd>
8. Release the key depressed in #6
### ✔️ Expected Behavior
A shortcut using the bottom right key as a modifier (<kbd>Ctrl</kbd>/<kbd>⇨</kbd> + <kbd>L</kbd>)
### ❌ Actual Behavior
An unusable sequence of 2 keypresses, with the first key named "VK 223" (<kbd>VK 223</kbd>, <kbd>L</kbd>)
After activating OK, Keyboard Manager complains that a shortcut must start with a modifier key.
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,541,283,211 | vscode | Big scroll jump (in random direction) on first mouse scroll after searching |
Type: <b>Bug</b>
This is something that recently started happening in python notebooks. Whenever I search for text on the page, it jumps to the text like normal, then when I scroll the mouse wheel it will make a big jump in a seemingly random directly, often in the opposite direction to the scroll. After this happens, scrolling works like normal.
Steps to reproduce:
- load a python notebook
- ctrl-f and search for some text
- scroll in any direction (just a single scroll notch)
I've tried disabling extensions, disabled smooth scrolling & fast scrolling, turned accessibility support to off (from auto). Nothing seems to help, I think it's just a bug.
VS Code version: Code 1.93.1 (38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40, 2024-09-11T17:20:05.685Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 9 5950X 16-Core Processor (32 x 3400)|
|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)|31.92GB (8.75GB free)|
|Process Argv|--crash-reporter-id 72a8acd0-9e73-4b7d-8190-3381a0bd1bc0|
|Screen Reader|no|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu-22.04|
|OS|Linux x64 5.10.16.3-microsoft-standard-WSL2|
|CPUs|AMD Ryzen 9 5950X 16-Core Processor (32 x 0)|
|Memory (System)|24.99GB (23.25GB free)|
|VM|0%|
</details><details><summary>Extensions (5)</summary>
Extension|Author (truncated)|Version
---|---|---
remote-wsl|ms-|0.88.3
debugpy|ms-|2024.10.0
python|ms-|2024.14.1
vscode-pylance|ms-|2024.9.2
jupyter|ms-|2024.8.1
(2 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
0ee40948:31013168
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31134774
wkspc-onlycs-t:31132770
wkspc-ranged-t:31125599
ei213698:31121563
cc771715:31140165
```
</details>
<!-- generated by issue reporter --> | bug,notebook-find | low | Critical |
2,541,293,577 | vscode | Marks don't show in minimap for HTML <script> JavaScript | <!-- ⚠️⚠️ 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.91.1
- OS Version: macOS 14.3.1
Steps to Reproduce:
1. Take the following HTML file:
```
<!DOCTYPE html>
<html>
<head>
<title>Basic HTML with JavaScript</title>
<script type="text/javascript">
// MARK: This is my mark
function showAlert() {
alert("Hello, World!");
}
</script>
</head>
<body onload="showAlert()">
<h1>Welcome to My Website</h1>
<p>This is a basic HTML file with embedded JavaScript.</p>
</body>
</html>
```
The `MARK` in the `<script>` portion of the HTML will not show in the minimap. | bug,editor-minimap | low | Critical |
2,541,293,631 | flutter | SelectableText crashes the app if custom contextMenuBuilder is used, Null check operator used on a null value | ### Steps to reproduce
1. Run the code sample
2. Press the button, it will open an overlay
3. Tap the text, it will crash
It happens on both Flutter `3.24.3` and `3.22.3`. Works fine on `3.19.6`
### Expected results
Should show the custom context menu instead of crashing
### Actual results
Crashes the app
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
void main() => runApp(const CustomContextMenuBuilderIssue());
class CustomContextMenuBuilderIssue extends StatefulWidget {
const CustomContextMenuBuilderIssue({super.key});
@override
State<CustomContextMenuBuilderIssue> createState() => _CustomContextMenuBuilderIssueState();
}
class _CustomContextMenuBuilderIssueState extends State<CustomContextMenuBuilderIssue> {
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
appBar: AppBar(title: const Text('Custom contextMenuBuilder')),
body: const Center(child: TheButton()),
),
);
}
}
class TheButton extends StatefulWidget {
const TheButton({super.key});
@override
State<TheButton> createState() => _TheButtonState();
}
class _TheButtonState extends State<TheButton> with TickerProviderStateMixin {
late final _animationController =
AnimationController(duration: const Duration(milliseconds: 300), vsync: this);
bool _openInProgress = false;
OverlayEntry? _popup;
late ThemeData _theme;
String _value = '0.0';
@override
void didChangeDependencies() {
super.didChangeDependencies();
_theme = Theme.of(context);
}
@override
Widget build(BuildContext context) {
_value = 'Tap me to crash';
return FilledButton.tonal(onPressed: _showPopup, child: const Text('Press me'));
}
void _showPopup() async {
if (_openInProgress) return;
_openInProgress = true;
_popup ??= OverlayEntry(builder: _popupBuilder);
Overlay.of(context).insert(_popup!);
await _animationController.forward(from: 0);
setState(() {});
}
Widget _popupBuilder(BuildContext context) {
return PositionedDirectional(
bottom: 0,
start: 0,
end: 0,
child: SizedBox(
height: 322.0,
child: Material(
color: _theme.colorScheme.secondaryContainer,
type: MaterialType.card,
child: ThePopUp(initialValue: _value),
),
),
);
}
}
typedef PopupOnChanged = void Function(double? amount);
class ThePopUp extends StatefulWidget {
const ThePopUp({super.key, required this.initialValue});
final String initialValue;
@override
State<ThePopUp> createState() => _ThePopUpState();
}
class _ThePopUpState extends State<ThePopUp> {
@override
Widget build(BuildContext context) {
return ConstrainedBox(
constraints: const BoxConstraints(maxWidth: 400),
child: ValueDisplay(value: widget.initialValue),
);
}
}
class ValueDisplay extends StatelessWidget {
const ValueDisplay({super.key, required this.value});
final String? value;
@override
Widget build(BuildContext context) {
final theme = Theme.of(context);
return SizedBox(
height: 40,
child: FittedBox(
fit: BoxFit.scaleDown,
child: SelectableText(
value.toString(),
textAlign: TextAlign.center,
maxLines: 1,
style: theme.textTheme.titleLarge,
contextMenuBuilder: _contextMenuBuilder,
),
),
);
}
void _pasteFromClipboard() async {
ContextMenuController.removeAny();
print('Fake paste');
}
Widget _contextMenuBuilder(BuildContext context, EditableTextState state) {
final List<ContextMenuButtonItem> buttonItems = state.contextMenuButtonItems;
final int pasteButtonIndex =
buttonItems.indexWhere((buttonItem) => buttonItem.type == ContextMenuButtonType.paste);
if (pasteButtonIndex >= 0) {
final pasteButton = buttonItems[pasteButtonIndex];
buttonItems[pasteButtonIndex] = pasteButton.copyWith(onPressed: _pasteFromClipboard);
} else {
final pasteButton = ContextMenuButtonItem(
onPressed: _pasteFromClipboard,
type: ContextMenuButtonType.paste,
);
if (buttonItems.length > 1) {
buttonItems[1] = pasteButton;
} else {
buttonItems.add(pasteButton);
}
}
return AdaptiveTextSelectionToolbar.buttonItems(
anchors: state.contextMenuAnchors,
buttonItems: buttonItems,
);
}
}
```
</details>
### Screenshots or Video
_No response_
### Logs
<details open><summary>Logs</summary>
```console
======== Exception caught by widgets library =======================================================
The following _TypeError was thrown building Overlay-[LabeledGlobalKey<OverlayState>#de574](state: OverlayState#b0685(entries: [OverlayEntry#809eb(opaque: true; maintainState: false), OverlayEntry#de194(opaque: false; maintainState: true), OverlayEntry#e7ffa(opaque: false; maintainState: false)])):
Null check operator used on a null value
The relevant error-causing widget was:
MaterialApp MaterialApp:file:///issue_reproducibles/lib/flutter/custom_context_menu_builder_issue.dart:15:12
When the exception was thrown, this was the stack:
#0 _OverlayEntryWidgetState.initState (package:flutter/src/widgets/overlay.dart:364:44)
#1 StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5748:55)
#2 ComponentElement.mount (package:flutter/src/widgets/framework.dart:5593:5)
#3 Element.inflateWidget (package:flutter/src/widgets/framework.dart:4468:16)
#4 MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:7035:36)
#5 Element.updateChild (package:flutter/src/widgets/framework.dart:3963:18)
#6 Element.updateChildren (package:flutter/src/widgets/framework.dart:4150:32)
#7 MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:7060:17)
#8 Element.updateChild (package:flutter/src/widgets/framework.dart:3941:15)
#9 ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5642:16)
#10 StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5780:11)
#11 Element.rebuild (package:flutter/src/widgets/framework.dart:5333:7)
#12 BuildScope._tryRebuild (package:flutter/src/widgets/framework.dart:2693:15)
#13 BuildScope._flushDirtyElements (package:flutter/src/widgets/framework.dart:2752:11)
#14 BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:3048:18)
#15 WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:1162:21)
#16 RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:468:5)
#17 SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1397:15)
#18 SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1318:9)
#19 SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:1176:5)
#20 _invoke (dart:ui/hooks.dart:312:13)
#21 PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:419:5)
#22 _drawFrame (dart:ui/hooks.dart:283:31)
====================================================================================================
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[√] Flutter (Channel stable, 3.24.3, on Microsoft Windows [Version 10.0.22631.4169], locale en-US)
• Flutter version 3.24.3 on channel stable at D:\Apps\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 2663184aa7 (11 days ago), 2024-09-11 16:27:48 -0500
• Engine revision 36335019a8
• Dart version 3.5.3
• DevTools version 2.37.3
```
</details>
| c: regression,framework,a: error message,has reproducible steps,P2,f: selection,workaround available,team-text-input,triaged-text-input,found in release: 3.24,found in release: 3.26 | low | Critical |
2,541,308,639 | godot | Setting shader parameter to const array causes error when material is freed | ### Tested versions
- Reproducible in: v4.3.stable.steam [77dcf97d8], v4.4.dev2.official [97ef3c837], v4.0.stable.official [92bee43ad]
- Not reproducible in: v2.1.stable.official, v3.0.stable.official, v3.5.1.stable.official [6fed1ffa3]
### System information
Godot v4.3.stable (77dcf97d8) - Windows 10.0.22631 - Vulkan (Mobile) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 31.0.101.5186) - 13th Gen Intel(R) Core(TM) i7-1360P (16 Threads)
### Issue description
If a shader parameter on a material is set to an array that is declared as const, the engine erroneously attempts to clear the array when the material is freed. This results in an error in the debugger tab, "clear: Array is in read-only state". In the MRP, I achieved this with the following code:
```gdscript
const TEST_CONST = []
func _ready() -> void:
var new_node = Node2D.new()
new_node.material = ShaderMaterial.new()
new_node.material.set_shader_parameter("test", TEST_CONST)
new_node.queue_free()
```
### Steps to reproduce
Run the minimal reproduction project and check the debugger tab.
### Minimal reproduction project (MRP)
[clearbug.zip](https://github.com/user-attachments/files/17091629/clearbug.zip)
| bug,topic:gdscript,needs testing,topic:shaders | low | Critical |
2,541,324,511 | deno | Convert package-lock.json or yarn.lock to deno.lock | ### Discussed in https://github.com/denoland/deno/discussions/25814
<div type='discussions-op-text'>
<sup>Originally posted by **alexgleason** September 23, 2024</sup>
I have a node project with a lot of dependencies that I will finally move to Deno for 2.0.
But Deno creates a new deno.lock from my package.json, essentially upgrading 180 packages at once.
I have a yarn.lock. I can convert between yarn.lock and package-lock.json. Can I convert either to deno.lock?</div> | suggestion,node compat | low | Minor |
2,541,365,511 | kubernetes | eviction manager fails to prioritize Hostpath Volume Pods for Eviction Under DiskPressure | ### What happened?
I have a GKE Cluster with a node that is running a bunch of innocent pods and a hostpath volume consuming pod. The pod eats up most of the disk space and puts Node under DiskPressure. Due to the DiskPressure NodeCondition, the eviction manager kicks in and ranks pods for eviction. However, the innocent pods are evicted before the culprit pod.
I have the repro script below which contains 15 innocent pods and 1 disk-eater pod. Here's the kubelet log when eviction manager ranks the pod for eviction:
```
I0923 00:46:49.313933 1787 eviction_manager.go:366] "Eviction manager: attempting to reclaim" resourceName="ephemeral-storage"
I0923 00:46:59.970765 1787 eviction_manager.go:377] "Eviction manager: must evict pod(s) to reclaim" resourceName="ephemeral-storage"
I0923 00:46:59.976721 1787 eviction_manager.go:395] "Eviction manager: pods ranked for eviction" pods=["default/hostnames-665b954fb4-v75xd","default/hostnames-665b954fb4-7gqt5","default/hostnames-665b954fb4-2xxdn","default/hostnames-665b954fb4-84gbj","default/hostnames-665b954fb4-v9442","default/hostnames-665b954fb4-nldw2","default/hostnames-665b954fb4-jqz7x","default/hostnames-665b954fb4-gwwrb","default/hostnames-665b954fb4-qmksn","default/hostnames-665b954fb4-p58gl","default/hostnames-665b954fb4-gxhlp","default/hostnames-665b954fb4-zds24","default/hostnames-665b954fb4-kkqpp","default/hostnames-665b954fb4-2tccd","default/hostnames-665b954fb4-pf2t4","kube-system/event-exporter-gke-78fb679b7b-dmb7t","default/disk-eater","gmp-system/collector-d2pgl","gmp-system/gmp-operator-76d464d74c-7p6bb","kube-system/konnectivity-agent-6584f57d94-gk4tn","kube-system/kube-dns-57cbb7b587-27mbb","gke-managed-cim/kube-state-metrics-0","kube-system/metrics-server-v1.30.3-7887b8869c-r6nqv","kube-system/konnectivity-agent-autoscaler-677598db7-6dkkl","kube-system/kube-dns-autoscaler-6f896b6968-x4bz2","kube-system/l7-default-backend-6697bb6dfd-fw88z","kube-system/gke-metrics-agent-f6vkb","kube-system/fluentbit-gke-4k7zj","kube-system/pdcsi-node-7dvb7","kube-system/kube-proxy-gke-cluster-2-default-pool-5e2b65c0-nvg6"]
```
It ranks 15 innocent pods for eviction first, then one system pod and then the disk eater pod.
### What did you expect to happen?
1. I think the safest thing to do in this case is kill the pod that is consuming hostpath volume. Since the lifecycle of hostpath volume is not tied up to the pod, kubelet cannot free up the space but it can at least kill the pod to stop the node becoming out of disk space.
2. Another issue is around telemetry signals. It is difficult to figure out that the disk pressure is due to hostPath volume consumption. Per-container metrics show low disk usage but node metrics show high disk usage. Unless you have the knowledge of how disk metrics are captured in k8s, it is difficult to come to conclusion that the disk pressure is due to hostPath. It would be good to have a signal that the DiskPressure is due to a hostPath volume usage.
### How can we reproduce it (as minimally and precisely as possible)?
1. Create a k8s cluster with a node that has disk space of 100Gi.
2. Deploy a bunch of innocent pods :
```
kubectl create deployment hostnames --image=nginx --replicas=15
```
3. Deploy a hostpath volume eater pod.
```
apiVersion: v1
kind: Pod
metadata:
name: disk-eater
spec:
containers:
- name: disk-eater
image: busybox
command: ["sh", "-c", "dd if=/dev/zero of=/data/file-$i bs=1G count=1024;"]
volumeMounts:
- name: host-volume
mountPath: /data
volumes:
- name: host-volume
hostPath:
path: /home/kubernetes/data
type: DirectoryOrCreate
```
### Anything else we need to know?
/sig node
### Kubernetes version
<details>
```console
1.30
```
</details>
### Cloud provider
<details>
GKE
</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>
| priority/backlog,sig/node,kind/feature,triage/accepted | low | Major |
2,541,367,989 | pytorch | Implement kaiming_uniform_ for sparse tensors. | ### 🚀 The feature, motivation and pitch
If you're trying to modify a linear layer to use sparse weights, initialization using `kaiming_uniform_` currently cannot be done without manually writing all the code yourself.
For this reason, having a sparse backend for `torch.nn.init.kaiming_uniform_` would be useful.
Example code:
``` python
in_features = 10
out_features = 10
nnz = in_features * out_features
crow_indices = torch.Tensor(size=(in_features,))
col_indices = torch.Tensor(size=(nnz,))
values = torch.Tensor(size=(nnz,))
weight = torch.sparse_csr_tensor(crow_indices, col_indices, values,
size=(out_features, in_features),
dtype=torch.float32)
init.kaiming_uniform_(weight)
```
### Alternatives
_No response_
### Additional context
_No response_
cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki | module: sparse,module: nn,triaged,module: initialization | low | Minor |
2,541,385,704 | rust | error[E0275]: overflow evaluating the requirement `<RefTFamily<T> as LifetimizedOutputFamily>::Output<'a> == _` | I was trying to implement a generic `SelfBorrowingClosure` based on <https://users.rust-lang.org/t/why-closure-cannot-return-a-reference-to-data-moved-into-closure/72655/6> but got a problem compiling the following piece of code:
```rust
pub trait LifetimizedOutputFamily {
type Output<'a>
where
Self::Output<'a>: 'a;
}
pub struct RefTFamily<T>(core::marker::PhantomData<*const T>);
impl<T> LifetimizedOutputFamily for RefTFamily<T>
{
type Output<'a> = &'a T
where
T: 'a;
}
pub struct SelfBorrowingClosure<State, F, OutputFam>
where
OutputFam: LifetimizedOutputFamily,
F: Fn(&'_ State) -> <OutputFam as LifetimizedOutputFamily>::Output<'_>,
{
pub state: State,
pub call: F,
pub output_family: core::marker::PhantomData<*const OutputFam>,
}
impl<State, F, OutputFam> SelfBorrowingClosure<State, F, OutputFam>
where
OutputFam: LifetimizedOutputFamily,
F: Fn(&'_ State) -> <OutputFam as LifetimizedOutputFamily>::Output<'_>,
{
pub fn new(state: State, call: F) -> Self {
Self {
state,
call,
output_family: core::marker::PhantomData,
}
}
pub fn call(&self) -> <OutputFam as LifetimizedOutputFamily>::Output<'_> {
(self.call)(&self.state)
}
}
```
Minimal Reproducible Example (MRE):
```rust
pub trait LifetimizedOutputFamily {
type Output<'a>
where
Self::Output<'a>: 'a;
}
pub struct RefTFamily<T>(core::marker::PhantomData<*const T>);
impl<T> LifetimizedOutputFamily for RefTFamily<T>
{
type Output<'a> = &'a T
where
T: 'a;
}
```
Error:
```
error[E0275]: overflow evaluating the requirement `<RefTFamily<T> as LifetimizedOutputFamily>::Output<'a> == _`
--> src\lib.rs:11:5
|
11 | type Output<'a> = &'a T
| ^^^^^^^^^^^^^^^
```
| T-compiler,C-bug,T-types,A-GATs | low | Critical |
2,541,386,246 | ui | [bug]: Components alias other than `@/` breaks non-default `utils` alias | ### Describe the bug
I have created a reproduction repository here https://github.com/andrewbrey/repro-shadcn-alias to demonstrate.
Basically, if you're `components.json` **components** alias starts with anything other than `@`, then your other aliases aren't correctly applied, which breaks non-default alias values. The observed behavior is that the starting character is used, but otherwise the applied alias for the other keys is the default value.
For example (and note that this is what is shown in the reproduction repository linked above), if I set my **components** alias to `~/components`, and my **utils** alias to `~/lib/custom_utils` then when I `shadcn add button`, the `Button` component that is added will use `~/lib/utils` as the import path of my utils functions, and _not the correct value_ of `~/lib/custom_utils`.
I believe this is the cause of https://github.com/shadcn-ui/ui/issues/4803.
### Affected component/components
All components
### How to reproduce
See reproduction repository https://github.com/andrewbrey/repro-shadcn-alias for example/demo.
### Codesandbox/StackBlitz link
_No response_
### Logs
_No response_
### System Info
```bash
N/A
```
### Before submitting
- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues | bug | low | Critical |
2,541,390,964 | deno | test --doc: support for notebook-style documents | Version: deno 1.46.3, but this applies both for the limited checking in Deno 1 and executing them in Deno 2.
Here's an example of a Markdown document that it would be nice to check:
````
Here are some imports:
```ts
import { assertEquals } from "@std/assert";
```
Here is a function that will be used later:
```ts
function square(x: number) {
return x * x;
}
```
Here is an example of how to call it:
```ts
assertEquals(square(2), 4);
```
````
What happens now:
```
% deno test --doc docs/example.md
Check file:///Users/skybrian/Projects/deno/repeat-test/docs/example.md$3-6.ts
Check file:///Users/skybrian/Projects/deno/repeat-test/docs/example.md$9-14.ts
Check file:///Users/skybrian/Projects/deno/repeat-test/docs/example.md$17-20.ts
error: TS2304 [ERROR]: Cannot find name 'assertEquals'.
assertEquals(square(2), 4);
~~~~~~~~~~~~
at file:///Users/skybrian/Projects/deno/repeat-test/docs/example.md$17-20.ts:1:1
TS2304 [ERROR]: Cannot find name 'square'.
assertEquals(square(2), 4);
~~~~~~
at file:///Users/skybrian/Projects/deno/repeat-test/docs/example.md$17-20.ts:1:14
Found 2 errors.
```
I think this could be made to work by removing everything except the code in the code blocks (replacing them with the same number of newlines so that the line numbers match) and then checking and/or executing the entire file.
This would allow us to write Markdown docs in a similar format as a Jupyter notebook, with text interspersed with code.
I made a similar suggestion in #25745 that's more limited (it only handles imports). With this one, it would be possible to avoid repeating both imports and local definitions when reusing them in a new code block. However, the writer would need to be careful not to use the same variable name twice. | suggestion,testing | low | Critical |
2,541,397,430 | rust | Large types cause linker failure | So I'm one of the maintainers of Leptos, and we're experimenting with a new static type system for our next release. The issue we're having is that for people porting existing websites/apps to the beta, experience a linker issue with link.exe, lld, mold, and ld. Our theory is that once the types reach a certain size, it will crash the linker.
In this version we're encoding the HTML tree into the type system by constructing `View<>` types that contain a tuple of it's descendants.
You can see what that looks like in the below code, which does not crash.
```toml
#Cargo.toml
[package]
name = "linker_issue"
version = "0.1.0"
edition = "2021"
[dependencies]
leptos = { git = "https://github.com/leptos-rs/leptos", features = ["ssr"] }
```
```rust
// main.rs
use leptos::html::{div, p, HtmlElement};
use leptos::prelude::*;
fn main() {
let view: HtmlElement<_, _, _, Dom> = div().child((
div().child((div(),)),
p().child((div(), div())),
div().child((div(), div(), div())),
p().child((div(), div(), div(), div())),
div().child((div(), div(), div(), div())),
p().child((div(), p(), div(), div())),
div().child((div(), div(), p(), div())),
p().child((div(), p(), div(), p())),
));
println!("type: {:?}", std::any::type_name_of_val(&view));
println!("\n\nsize: {:?}", std::mem::size_of_val(&view));
let html = view.to_html();
println!("\n\noutput: {html}");
}
```
So far we haven't nailed down a reasonable reproduction I can post, but I can reproduce the issue while trying to build one of our user's private projects. Running `cargo leptos build`, which runs `cargo build --no-default-features --features=ssr`, generates this error. I've put it in a gist because it is huge: https://gist.github.com/benwis/fe3a8010243c0f6b338f6aef0b0e7ad2
I'm not quite sure how to debug this, we'd love to use this system as it offers a number of benefits, but if it's going to break compilation at larger app sizes we'll have to defer. Any thoughts? | A-linkage,A-debuginfo,I-ICE,T-compiler,C-bug,E-needs-investigation | medium | Critical |
2,541,421,622 | ant-design | Table组件设置virtual模式后在2k分辨率屏幕下会显示滚动条 | ### Reproduction link
[](https://stackblitz.com/edit/antd-reproduce-5x-w2h2zc?file=demo.tsx)
### Steps to reproduce
在2k屏幕下系统设置125%的缩放（该缩放系数系统默认推荐），Table配置virtual和bordered即可复现，当在1080屏幕或更改浏览器缩放比例为80%时即可恢复正常
### What is expected?
表格在内容未溢出的情况下不显示滚动条与边框。
### What is actually happening?
表格在内容未溢出的情况下出现了滚动条和不显示右侧边框
| Environment | Info |
| --- | --- |
| antd | 5.21.0 |
| React | 18 |
| System | Windows 11 |
| Browser | chrome |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | Inactive,unconfirmed | low | Minor |
2,541,427,371 | deno | Offer the possibility to order properties in the CSS formatter | [g-plane/malva](https://github.com/g-plane/malva) support a [`declarationOrder`](https://malva.netlify.app/config/declaration-order.html) option which would be nice if let available to end users.
I know `deno fmt` tries to limit the number of options by design, but I feel like this one would bring a lot of value for users using deno in web projects.
The current config of the CSS fmt is unironically a bit too lax for stylesheet collaboration, where everyone can add their new rules wherever they had their cursor last which can lead to chaotic stylesheet after many patches.
Allowing a way to enforce a stricter formatting would make the life of reviewers easier (no need to reject a PR due to formatting), contributors (with instant fmt feedback) and maintainers (cleaner and healthier codebase) | suggestion,deno fmt | low | Minor |
2,541,436,526 | neovim | UpdateRemotePlugins does not work | ### Problem
previously everything worked fine. I uninstalled Python 3.9, etc. and manually removed most stuffs.
Then I extracted nvim and installed Python 3.8.5.
Now :UpdateRemotePlugins does not change rplugin.vim for either Shougo/deoplete.nvim or gelguy/wilder.nvim. (I'm using Plug.)
the command results in "python3 host registered plugins []" and rplugin.vim is always,
```
" perl plugins
" node plugins
" python3 plugins
" ruby plugins
```
Thank you in advance.
### Steps to reproduce
1. use Plug to install deoplete and wilder. I don't know how to use them without any package managers.
2. restart nvim.
3. manually run :UpdateRemotePlugins. rplugin.vim is empty
4. repeat steps 2 and 3. rplugin.vim is still empty
thus the plugins cannot load.
### Expected behavior
for deoplete on Linux, rplugin.vim consists,
```
call remote#host#RegisterPlugin('python3', '/home/users/.../.local/share/nvim/plugged/deoplete.nvim/rplugin/python3/deoplete', [
\ {'sync': v:false, 'name': '_deoplete_init', 'type': 'function', 'opts': {}},
\ ])
```
### Nvim version (nvim -v)
0.10.1
### Vim (not Nvim) behaves the same?
N/A
### Operating system/version
Windows 10
### Terminal name/version
N/A
### $TERM environment variable
N/A
### Installation
portable | bug,remote-plugin | low | Minor |
2,541,525,242 | godot | SpringArm3D shape is not visible | ### Tested versions
4.3 - 4.4.dev2
### System information
Android 11 - 4.4.dev2 - Compatibility Renderer
### Issue description
SpringArm3D shape is not visible.
https://github.com/user-attachments/assets/7307946b-79cb-40d0-923a-30cf9bb65eec
### Steps to reproduce
- added note3d
- added SpringArm3D
- added SpringArm3D shape
### Minimal reproduction project (MRP)
[test.zip](https://github.com/user-attachments/files/17092616/test.zip)
| bug,confirmed,topic:3d | low | Minor |
2,541,557,398 | ui | [bug]: CKEditor 5 options cause the dialog to close unexpectedly, and the link and media features don't work due to overlay issues. | ### Describe the bug
CYSheet.js File
```
import {
Sheet,
SheetClose,
SheetContent,
SheetDescription,
SheetFooter,
SheetHeader,
SheetTitle,
SheetTrigger,
} from '@/components/ui/sheet';
function CYSheet({
open,
setOpen,
title = 'Add Title',
description,
showHeader = true,
render,
className,
headerClassName = '',
side = 'right',
}) {
return (
<Sheet open={open} onOpenChange={setOpen}>
<SheetContent
side={side}
className={`w-full max-w-md p-0 flex flex-col gap-0 ${className ? className : 'sm:max-w-md'}`}
>
<SheetHeader
className={`${!showHeader && 'hidden'} space-y-0 text-left ${headerClassName ? headerClassName : 'p-4'}`}
>
<SheetTitle>{title}</SheetTitle>
<SheetDescription className={`${!description && 'hidden'}`}>{description}</SheetDescription>
</SheetHeader>
{render}
</SheetContent>
</Sheet>
);
}
export default CYSheet;
```
I am using here
```
<CYSheet
title="Update Round"
description="Please select the round type from below:"
open={updateRoundModal}
setOpen={setUpdateRoundModal}
render={
<UpdateRound mutateOpportunity={mutateOpportunity} setUpdateRoundModal={setUpdateRoundModal} round={round} />
}
className="sm:max-w-6xl"
headerClassName="bg-zinc-50 p-4 border-b"
/>
```
on Update Round, I have used Ckedtor 5
### Affected component/components
Dialog, Sheet
### How to reproduce
To reproduce the issue:
Open a dialog that contains CKEditor 5.
Interact with CKEditor options, such as link or media.
Observe that the dialog closes unexpectedly without clicking the close button.
The link and media overlays don’t function properly, preventing their use.
### Codesandbox/StackBlitz link
_No response_
### Logs
_No response_
### System Info
```bash
Linux, Chrome
```
### Before submitting
- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues | bug | low | Critical |
2,541,565,835 | deno | Error when running a module that uses the `global` global | Version: Deno 2.0.0-rc.3
**Describe the bug**
Error when run module @gradio/client with deno 2
**Reproduce**
```javascript
import {
Client,
} from "https://cdn.jsdelivr.net/npm/@gradio/client/dist/index.min.js";
const client = await Client.connect(
"http://localhost:7860/",
);
```
when create client gradio, i get this error:
```
global is not defined
```
**Discuss**
i look in to gradio client source [here](https://github.com/gradio-app/gradio/blob/98cbcaef827de7267462ccba180c7b2ffb1e825d/client/js/src/client.ts#L149)
and found they init client like this:
```javascript
private async init(): Promise<void> {
if (
(typeof window === "undefined" || !("WebSocket" in window)) &&
!global.WebSocket
) {
const ws = await import("ws");
global.WebSocket = ws.WebSocket as unknown as typeof WebSocket;
}
// more ....
```
So i guess that problem is Deno 2 drop support of global variable as describe [here](https://docs.deno.com/runtime/reference/migrate_deprecations/#window)
So the question is: if I use Deno 2, how can I use a package that relies on global variables, like gradio/client?
**Expected behavior**
@gradio/client work normally without errorn when init
| question | low | Critical |
2,541,607,557 | storybook | [Bug]: Primary block shares state (from @storybook/preview-api useState hook) with the first story on the Docs page | ### Describe the bug
I have a modal component I'm documenting via Storybook that is shown via a click of a button. I used the `useState` hook of `@storybook/preview-api` to set the `open` state of the modal when the button is clicked. It's working in that the modal is shown, however, the state appears to be shared between the primary block and the first story so two modals are actually rendered when any of the two canvases' button is clicked. The first modal is from the primary block, and the second is from the first story, where the second modal overlaps the first. But when the args are updated via the primary block's control panel, it doesn't apply to the first story, so what happens is the modal with the updated content is hidden behind the modal with the original content. I know it's confusing so here's a video of the issue:
https://github.com/user-attachments/assets/c2f3aaea-dcb0-4a93-958c-52e73ba2eaab
### Reproduction link
https://stackblitz.com/edit/github-y4gwez?file=src%2Fstories%2FModal.stories.tsx
### Reproduction steps
1. Go to the link above.
2. On the primary doc block's control panel, update the description arg to have more content.
3. Click the `OPEN MODAL` button of the primary doc block. Notice that there are two modals rendered stacked together where the top modal doesn't have the updated content.
### System
```bash
Storybook Environment Info:
System:
OS: Linux 5.0 undefined
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Shell: 1.0 - /bin/jsh
Binaries:
Node: 18.20.3 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.2.3 - /usr/local/bin/npm <----- active
pnpm: 8.15.6 - /usr/local/bin/pnpm
npmPackages:
@storybook/addon-essentials: 8.3.0 => 8.3.0
@storybook/addon-interactions: 8.3.0 => 8.3.0
@storybook/addon-links: 8.3.0 => 8.3.0
@storybook/addon-onboarding: 8.3.0 => 8.3.0
@storybook/blocks: 8.3.0 => 8.3.0
@storybook/nextjs: 8.3.0 => 8.3.0
@storybook/preview-api: ^8.3.0 => 8.3.0
@storybook/react: 8.3.0 => 8.3.0
@storybook/test: 8.3.0 => 8.3.0
storybook: 8.3.0 => 8.3.0
```
### Additional context
_No response_ | bug,needs triage | low | Critical |
2,541,656,119 | kubernetes | watchlist request will be closed abnormally when cacheInterval contains a large amount of watchEvents | ### What happened?
I'm conducting an investigation into watchList benchmark in 1.30 Kubernetes cluster. I found that using `watchList` request to make the reflector become synced takes longer than using `list` request.
Then, I found that the apiserver always prints `Forcing %s watcher close due to unresponsiveness: key.... ` log. I realized that if `cacheInterval ` containes lots of watchEvents, then cacheWatcher.Process will not be invoked until all watchEvents in `cacheInterval` have been sent. As a result, the `input` channel in `cacheWatcher` may become full, leading to the abnormal closure of the watchlist request.
Therefore, are there any solutions to address this issue? Perhaps we need a new watchList request handler to process watchList requests instead of reusing the original watch request handler's logic.
If there isn't a similar issue in this problem, we can use the current issue to track it. :)
### What did you expect to happen?
Using watchList request to make the reflector become synced takes approximately the same amount of time as using list request.
### How can we reproduce it (as minimally and precisely as possible)?
1. create 5K Pods
2. use watchlist request to make reflector become synced. At the same time, start many client to update pods
3. watchlist request will be close and apiserver prints `Forcing %s watcher close due to unresponsiveness: key.... ` log
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
```console
$ kubectl version
# paste output here
```
</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/api-machinery,triage/accepted | low | Major |
2,541,667,564 | ant-design | ProTable column property ellipsis clean all style in return of render | ### Reproduction link
[](https://stackblitz.com/edit/antd-reproduce-5x-ubk46u)
### Steps to reproduce
add `ellipsis: true` in one of `let columns = [`, the link type of field is cleared.
### What is expected?
do not clear the style of <a>.
### What is actually happening?
style of <a> is cleared.
| Environment | Info |
| --- | --- |
| antd | 5.21.0 |
| React | 18 |
| System | macos |
| Browser | firefox |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | Inactive,unconfirmed | low | Minor |
2,541,719,924 | flutter | Add Advanced Marker support to `google_maps_flutter` | ### Document Link
https://flutter.dev/go/google-maps-advanced-markers
### What problem are you solving?
Add support for Google Maps' advanced markers to `google_maps_flutter` package.
Related issue: https://github.com/flutter/flutter/issues/130472 | p: maps,package,c: proposal,team-ecosystem,P2,design doc,triaged-ecosystem,:scroll: | low | Major |
2,541,774,270 | material-ui | [docs-infra] Codeblock issues | ### Steps to reproduce
1. Copy button obscures code on smaller screen sizes. ([page](https://mui.com/material-ui/getting-started/installation/)) (Fixed by #44861)
<img width="379" alt="Screenshot 2024-09-23 at 09 08 32" src="https://github.com/user-attachments/assets/c2051c58-df9d-434e-9255-c72d582e4445">
2. Code highlight block doesn't take the full width of the code ([page](https://mui.com/material-ui/))
<img width="1030" alt="Screenshot 2024-09-23 at 09 13 03" src="https://github.com/user-attachments/assets/f3a1eaa8-519d-49ee-b11f-7cad4a9427f8">
3. Missing right padding in code block ([page](https://mui.com/material-ui/))
<img width="388" alt="Screenshot 2024-09-23 at 09 14 15" src="https://github.com/user-attachments/assets/6c4028c2-9663-4eb0-bc00-10650a193349">
### Current behavior
_No response_
### Expected behavior
_No response_
### Context
_No response_
### Your environment
<details>
<summary><code>npx @mui/envinfo</code></summary>
```
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
```
</details>
**Search keywords**: codeblock | bug 🐛,scope: docs-infra | low | Minor |
2,541,819,492 | electron | [Bug]: Infinite loop when adding an iframe to the DOM using devtools when devtools protocol is active | ### 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
32.1.1
### What operating system(s) are you using?
Windows
### Operating System Version
Windows 11 Enterprise 22H2
### What arch are you using?
x64
### Last Known Working Electron version
_No response_
### Expected Behavior
When having activated the devtools protocol, an iframe that's injected to the DOM using devtools by running:
```
const ifr = document.createElement('iframe');
document.body.appendChild(ifr);
```
should successfully inject it once without sideeffects.
### Actual Behavior
When having activated the devtools protocol, an iframe that's injected to the DOM using devtools by running:
```
const ifr = document.createElement('iframe');
document.body.appendChild(ifr);
```
is creating an infinite loop, causing the eventloop to be completely blocked in the related renderer process.
### Testcase Gist URL
https://gist.github.com/41184d95ea650b5337f5dcba4afa7317
### Additional Information
- The problem happens both when on a local file (index.html) or an external page loaded with loadURL.
- If the injection happens within a setTimeout, this problem does not occur.
- If the injection happens in a script tag in the html file, this problem does not occur.
- If injection happens from sending a protocol command like `Runtime.evaluate` this problem does not occur.
- If injection happens from sending a protocol command like `Runtime.compileScript` and then `Runtime.runScript` this problem does not occur.
The issue seems to be limited to it being executed within devtools. However this is also able to be reproduced with webdriverio when injecting the script with executeAsync. | bug :beetle:,platform/all,status/confirmed,has-repro-gist,32-x-y,33-x-y | low | Critical |
2,541,870,026 | deno | deno compile error [ERR_TYPES_NOT_FOUND] | deno 2.0.0-rc.4 (release candidate, release, aarch64-apple-darwin)
v8 12.9.202.13-rusty
typescript 5.6.2
```
{
"name": "test_deno",
"version": "1.0.0",
"main": "index.js",
"description": "",
"devDependencies": {
"eslint-plugin-vue": "^9.28.0"
}
}
```
```
import plugin from "eslint-plugin-vue";
```
```
➜ test_deno deno compile main.ts
error: Failed resolving types. [ERR_TYPES_NOT_FOUND] Could not find types for 'file:///Users/XXXX/test_deno/node_modules/eslint-plugin-vue/index.js' imported from 'file:///Users/zhouqili/test_deno/main.ts'
at file:///Users/XXXX/test_deno/main.ts:1:20
```
| compile,types | low | Critical |
2,541,980,451 | transformers | support schedule sampling | ### Feature request
To solve the exposure bias problem, can schedule sampling be supported?
https://arxiv.org/abs/1906.07651
https://github.com/deep-spin/scheduled-sampling-transformers
### Motivation
For the same data, the training loss is very low but the inference result is not good.
### Your contribution
no | trainer,Feature request | low | Minor |
2,541,981,532 | ui | [bug]: Invalid DOM property `xlink:href`. Did you mean `xlinkHref`? | ### Describe the bug
Using shadcn with astro and create button component as per your documentations. below is the generate code
```tsx
import { Slot } from "@radix-ui/react-slot";
import { cva, type VariantProps } from "class-variance-authority";
import * as React from "react";
import { cn } from "@/libs";
const buttonVariants = cva(
"inline-flex items-center justify-center whitespace-nowrap rounded-md text-sm font-medium transition-colors focus-visible:outline-none focus-visible:ring-1 focus-visible:ring-zinc-950 disabled:pointer-events-none disabled:opacity-50 dark:focus-visible:ring-zinc-300",
{
variants: {
variant: {
default:
"bg-zinc-900 text-zinc-50 shadow hover:bg-zinc-900/90 dark:bg-zinc-50 dark:text-zinc-900 dark:hover:bg-zinc-50/90",
destructive:
"bg-red-500 text-zinc-50 shadow-sm hover:bg-red-500/90 dark:bg-red-900 dark:text-zinc-50 dark:hover:bg-red-900/90",
outline:
"border border-zinc-200 bg-white shadow-sm hover:bg-zinc-100 hover:text-zinc-900 dark:border-zinc-800 dark:bg-zinc-950 dark:hover:bg-zinc-800 dark:hover:text-zinc-50",
secondary:
"bg-zinc-100 text-zinc-900 shadow-sm hover:bg-zinc-100/80 dark:bg-zinc-800 dark:text-zinc-50 dark:hover:bg-zinc-800/80",
ghost: "hover:bg-zinc-100 hover:text-zinc-900 dark:hover:bg-zinc-800 dark:hover:text-zinc-50",
link: "text-zinc-900 underline-offset-4 hover:underline dark:text-zinc-50"
},
size: {
default: "h-9 px-4 py-2",
sm: "h-8 rounded-md px-3 text-xs",
lg: "h-10 rounded-md px-8",
icon: "h-9 w-9"
}
},
defaultVariants: {
variant: "default",
size: "default"
}
}
);
export interface ButtonProps
extends React.ButtonHTMLAttributes<HTMLButtonElement>,
VariantProps<typeof buttonVariants> {
asChild?: boolean;
}
const Button = React.forwardRef<HTMLButtonElement, ButtonProps>(
({ className, variant, size, asChild = false, ...props }, ref) => {
const Comp = asChild ? Slot : "button";
return <Comp className={cn(buttonVariants({ variant, size, className }))} ref={ref} {...props} />;
}
);
Button.displayName = "Button";
export { Button, buttonVariants };
```
although it runs okay and button appears but in terminal it gives warning as below
```log
Warning: Invalid DOM property `xlink:href`. Did you mean `xlinkHref`?
at use
at svg
at span
at button
at eval (/home/project/location//src/components/ui/button.tsx:39:6)
```
and line # 39 is `VariantProps<typeof buttonVariants> { `
unable to understand where is this line and why it is throwing warning?
below is package.json
```json
"dependencies": {
"@astrojs/check": "0.9.3",
"@astrojs/netlify": "6.0.0-beta.0",
"@astrojs/node": "9.0.0-beta.2",
"@astrojs/react": "3.6.2",
"@astrojs/tailwind": "5.1.1",
"@headlessui/react": "1.7.18",
"@heroicons/react": "2.1.1",
"@hookform/resolvers": "3.3.4",
"@iconify-json/mdi": "1.1.66",
"@radix-ui/react-alert-dialog": "1.0.5",
"@radix-ui/react-aspect-ratio": "1.0.3",
"@radix-ui/react-checkbox": "1.0.4",
"@radix-ui/react-dialog": "1.0.5",
"@radix-ui/react-dropdown-menu": "^2.1.1",
"@radix-ui/react-icons": "1.3.0",
"@radix-ui/react-label": "2.0.2",
"@radix-ui/react-popover": "^1.1.1",
"@radix-ui/react-radio-group": "1.1.3",
"@radix-ui/react-select": "2.0.0",
"@radix-ui/react-slot": "1.0.2",
"@radix-ui/react-toast": "^1.2.1",
"@react-hook/media-query": "1.1.1",
"astro": "5.0.0-beta.1",
"astro-i18next": "1.0.0-beta.21",
"astro-icon": "^1.1.1",
"axios": "^1.7.5",
"class-variance-authority": "0.7.0",
"clsx": "2.1.0",
"cmdk": "1.0.0",
"embla-carousel-react": "8.1.3",
"file-type": "19.0.0",
"i18next": "^23.10.1",
"jwt-decode": "^4.0.0",
"lucide-react": "0.396.0",
"mongoose": "^8.6.3",
"nanostores": "0.10.3",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-drag-drop-files": "2.3.10",
"react-hook-form": "^7.50.0",
"react-hot-toast": "2.4.1",
"react-i18next": "14.1.0",
"react-icon": "1.0.0",
"react-icons": "5.0.1",
"react-share": "5.1.0",
"shadcn": "^2.0.7",
"tailwind-merge": "2.2.0",
"tailwindcss": "3.4.0",
"tailwindcss-animate": "1.0.7",
"typescript": "5.3.3",
}
```
### Affected component/components
Button
### How to reproduce
1. install shadcn in Astro component
2. generate button component
3. now when run the project `npm run dev`
### Codesandbox/StackBlitz link
_No response_
### Logs
_No response_
### System Info
```bash
> Ubuntu 24.04
```
### Before submitting
- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues | bug | low | Critical |
2,542,000,397 | vscode | SCM Graph - add "share" and "vscode.dev" actions to the history item context menu | <!-- ⚠️⚠️ 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. -->
<!-- Describe the feature you'd like. -->
| feature-request,scm | low | Minor |
2,542,018,708 | rust | Error when unsizing types with thin pointers that turn fat | ### Code
```rust
use std::fmt::Debug;
struct ListItem<T: ?Sized> {
next: Option<Box<Self>>,
item: T,
}
fn main() {
let _ = Box::new(ListItem {
next: None,
item: [42, 24],
}) as Box<ListItem<dyn Debug>>;
}
```
### Current output
```text
error[E0605]: non-primitive cast: `Box<ListItem<[i32; 2]>>` as `Box<ListItem<dyn Debug>>`
--> src/main.rs:9:13
|
9 | let _ = Box::new(ListItem {
| _____________^
10 | | next: None,
11 | | item: [42, 24],
12 | | }) as Box<ListItem<dyn Debug>>;
| |__________________________________^ an `as` expression can only be used to convert between primitive types or to coerce to a specific trait object
For more information about this error, try `rustc --explain E0605`.
error: could not compile `playground` (bin "playground") due to 1 previous error
```
### Desired output
```text
error[E????]: type `Box<ListItem<[i32; 2]>>` cannot be unsized to `Box<ListItem<dyn Debug>>`
--> src/main.rs:9:13
|
9 | let _ = Box::new(ListItem {
| _____________^
10 | | next: None,
11 | | item: [42, 24],
12 | | }) as Box<ListItem<dyn Debug>>;
| |__________________________________^
note: the struct `ListItem<[i32; 2]>` would change size if unsized to `ListItem<dyn Debug>`
3 │ struct ListItem<T: ?Sized> {
4 │ next: Option<Box<Self>>,
| ^^^^^^^^^^^^^^^^^^^^^^^ this field's type would change from a thin pointer to a fat pointer
5 │ item: T,
6 │ }
For more information about this error, try `rustc --explain E????`.
error: could not compile `playground` (bin "playground") due to 1 previous error
```
### Rationale and extra context
_No response_
### Other cases
```rust
// Removing the `next` field makes the code compile:
use std::fmt::Debug;
struct ListItem<T: ?Sized> {
// next: Option<Box<Self>>,
item: T,
}
fn main() {
let _ = Box::new(ListItem {
// next: None,
item: [42, 24],
}) as Box<ListItem<dyn Debug>>;
}
```
### Rust Version
```text
rustc 1.83.0-nightly (6c6d21008 2024-09-22)
binary: rustc
commit-hash: 6c6d210089e4589afee37271862b9f88ba1d7755
commit-date: 2024-09-22
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```
### Anything else?
If more information/explanation is needed, I can provide it, just ask. | A-diagnostics,T-compiler | low | Critical |
2,542,043,990 | TypeScript | IsolatedDeclarations: emitted declarations inconsistent between `transpileDeclaration` API and TypeScript Playground | ### Acknowledgement
- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.
### Example
> NOTE: Enabled `isolatedDeclaration` and `noCheck`
[Playground Link](https://www.typescriptlang.org/play/?target=99&isolatedDeclarations=true&noCheck=true#code/JYWwDg9gTgLgBAbzgYQiEBTAdvAvnAMyjTgHIABANwFcMB6KanUDAWgGNoNSAoHjAB6RYcTlgDO8YONTps8ALxwAFFggATDAC44AOQ0YAlDrWa40lGkw44CgHw84cUxgB0LgCoBPMBlsKlABEAeQBZfU1vX3FXZDDQgFFdDyA)
```ts
// input
import { Comment } from '@vue/runtime-core'
// ^^^^^^^ https://github.com/vuejs/core/blob/a177092754642af2f98c33a4feffe8f198c3c950/packages/runtime-core/src/vnode.ts#L70
export const comment: Comment
// .d.ts output
export declare const comment: Comment;
```
This example is correct because the `tsc` checker analyzer `Comment` is a const variable defined in `@vue/runtime-core`. So the `Comment` who referenced by `comment` is actually referenced [lib.dom.d.ts](https://github.com/microsoft/TypeScript/blob/88809467e8761e71483e2f4948ef411d8e447188/src/lib/dom.generated.d.ts#L5811-L5822)'s `Comment`. But the output of this example in `transpileDeclaration` APi will same as the following example.
### Another example
> NOTE: Enabled `isolatedDeclaration` and `noCheck`
[Playground Link](https://www.typescriptlang.org/play/?target=99&isolatedDeclarations=true&noCheck=true#code/JYWwDg9gTgLgBAbzgYQiEBTAdvAvnAMyjTgHIATCDAZwFosIZaMAPYamUgKFcljgDGELB0FpMOAFwpx2eEA)
```ts
// input
import { Comment } from 'does-not-exist'
export const comment: Comment
// .d.ts output
import { Comment } from 'does-not-exist';
export declare const comment: Comment;
```
This example is also correct because the `tsc` checker can't analyze what `Comment` is, so the `Comment` was kept in the output as it has been referenced by `comment`.
But If I want to use [lib.dom.d.ts](https://github.com/microsoft/TypeScript/blob/88809467e8761e71483e2f4948ef411d8e447188/src/lib/dom.generated.d.ts#L5811-L5822)'s `Comment` rather than imported it will be incorrect.
### Expect Behaviour
In `IsolatedDeclarations`, Ideally, we shouldn't analyze imports, but if we stop analyzing, this will generate incorrect output.
So I suggest `tsc` should throw an error about the above cases when `IsolatedDeclarations` is enabled. This is also beneficial for third-party `IsolatedDeclarations` implementations.
BTW this issue I found when I fix the output mismatch between `oxc-isolated-declarations` and `tsc` | Needs Investigation | low | Critical |
2,542,092,106 | node | Stream not destroyed when piped in Duplex.from() writable | ### Version
v22.9.0
### Platform
```text
Darwin MBPM.local 24.0.0 Darwin Kernel Version 24.0.0: Mon Aug 12 20:52:31 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6030 arm64
```
### Subsystem
stream
### What steps will reproduce the bug?
```js
const { Duplex, Readable, pipeline } = require('node:stream')
pipeline(
Readable.from(
(async function* () {
try {
console.log('Readable stream started')
let i = 32
while (i-- > 0) {
yield Buffer.from('Hello, world!')
console.log('Readable stream resumed')
}
console.log('Readable stream ended')
} catch (err) {
console.log('Readable stream errored', err)
} finally {
console.log('Readable stream destroyed')
}
})(),
{ objectMode: false, autoDestroy: true, highWaterMark: 1 }
),
Duplex.from(async function (asyncGenerator) {
asyncGenerator.return()
}),
(err) => {
if (err) {
console.error('Pipeline failed', err)
} else {
console.log('Pipeline succeeded')
}
}
)
```
### How often does it reproduce? Is there a required condition?
Any code used as `Duplex.from(async function () {})` that does not fully consume the input will prevent the input stream to be properly disposed:
```js
Duplex.from(async function (asyncGenerator) {
for await (const chunk of asyncGenerator) {
console.log('Writable stream received', chunk)
break
}
})
```
```js
Duplex.from(async function (asyncGenerator) {
asyncGenerator.retrun()
})
```
```js
Duplex.from(async function (asyncGenerator) {
// do nothing
})
```
### What is the expected behavior? Why is that the expected behavior?
The readable's destroy steps should be called.
### What do you see instead?
The readable is not destroyed.
### Additional information
_No response_ | confirmed-bug,stream | low | Critical |
2,542,114,422 | tauri | [bug] [ios] [v2] Export method does not work | ### Describe the bug
Running ` npm run tauri ios build -- --export-method app-store-connect` does not export the app for AppStore. I need to change ExportOptions.plist directly to get it to build correctly.
- Automatic signing is set for all targets.
### Reproduction
` npm run tauri ios build -- --export-method app-store-connect` then try to submit to the AppStore via the Transporter App. "Asset validation failed (90161)
Invalid Provisioning Profile. The provisioning profile included in the yyy bundle [Payload/yyy.app] is invalid. [Missing code-signing certificate]. A distribution provisioning profile should be used when uploading apps to App Store Connect. (ID: xxx)"
### Expected behavior
`--export-method app-store-connect` to work correctly.
### Full `tauri info` output
```text
> tauri info
[✔] Environment
- OS: Mac OS 14.7.0 arm64 (X64)
✔ Xcode Command Line Tools: installed
✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-aarch64-apple-darwin (default)
- node: 20.17.0
- npm: 10.8.2
[-] Packages
- tauri 🦀: 2.0.0-rc.15
- tauri-build 🦀: 2.0.0-rc.12
- wry 🦀: 0.43.1
- tao 🦀: 0.30.0
- @tauri-apps/api : 2.0.0-rc.5
- @tauri-apps/cli : 2.0.0-rc.16
[-] Plugins
- tauri-plugin-window-state 🦀: 2.0.0-rc.5
- @tauri-apps/plugin-window-state : not installed!
- tauri-plugin-store 🦀: 2.0.0-rc.3
- @tauri-apps/plugin-store : not installed!
- tauri-plugin-log 🦀: 2.0.0-rc.2
- @tauri-apps/plugin-log : not installed!
- tauri-plugin-shell 🦀: 2.0.0-rc.3
- @tauri-apps/plugin-shell : not installed!
- tauri-plugin-dialog 🦀: 2.0.0-rc.7
- @tauri-apps/plugin-dialog : not installed!
- tauri-plugin-notification 🦀: 2.0.0-rc.5
- @tauri-apps/plugin-notification : not installed!
- tauri-plugin-fs 🦀: 2.0.0-rc.5
- @tauri-apps/plugin-fs : not installed!
[-] App
- build-type: bundle
- frontendDist: ../src
[-] iOS
- Developer Teams: <Redacted>
```
### Stack trace
_No response_
### Additional context
_No response_ | type: bug,status: needs triage,platform: iOS | low | Critical |
2,542,134,140 | ant-design | Select: add option data to labelRender props | ### What problem does this feature solve?
I want to render the label with additional data from the option, not only label and value.
### What does the proposed API look like?
same as "optionRender"
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | 💡 Feature Request,Inactive,🧶 Low Priority | low | Minor |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.