[Flutter 3.13.8 Crash] Crashed:: io.flutter.1.ui EXC_BAD_ACCESS (SIGSEGV) flutter::DisplayListBuilder::Restore()

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
We found a bug related to Flutter Clip.antiAliasWithSaveLayer that caused the app to crash on iOS, this bug seems to be related to the list, and we have found the  minimal reproducible sample that can be reproduced.
Basically, our scenario is in a list, and every item has an antiAliasWithSaveLayer, which I know is very performance-intensive, but I don't think it should cause the application to crash.
Expected results
App should not crash
Actual results
App Crashed
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  Widget buildSaveLayerContainer() => Container(
        decoration: BoxDecoration(
          borderRadius: BorderRadius.circular(4),
        ),
        clipBehavior: Clip.antiAliasWithSaveLayer,
        width: 35,
        height: 24,
      );

  Widget buildSaveLayerContainerWithChild({required Widget child}) => Container(
        decoration: BoxDecoration(
          borderRadius: BorderRadius.circular(4),
        ),
        clipBehavior: Clip.antiAliasWithSaveLayer,
        width: 35,
        height: 24,
        child: child,
      );

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: Scaffold(
        body: buildSaveLayerContainerWithChild(
          child: Stack(children: [
            Stack(
              children: [
                SingleChildScrollView(
                  child: Column(
                    children: List.generate(
                      1000,
                      (index) => buildSaveLayerContainerWithChild(
                        child: Row(
                          children: [
                            buildSaveLayerContainer(),
                            Container(
                              height: 60,
                              color: Colors.white,
                              padding: const EdgeInsets.symmetric(horizontal: 20),
                              child: Row(
                                children: [
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                  buildSaveLayerContainer(),
                                ],
                              ),
                            ),
                          ],
                        ),
                      ),
                    ),
                  ),
                )
              ],
            ),
          ]),
        ),
      ),
    );
  }
}

Screenshots or Video
any device or simulator can reproduce this issue with code above
Logs
Logs
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 1431A08D-406F-4288-A821-4E0F6030510E
CrashReporter Key:   8987C304-5DA4-F307-AB7D-DDFE550A1FF8
Hardware Model:      MacBookPro16,1
Process:             UNODriver [73121]
Path:                /Users/USER/Library/Developer/CoreSimulator/Devices/3FF0171B-E914-4058-8882-F84B91FBB07C/data/Containers/Bundle/Application/1E10F85F-E855-4DD9-8A9B-6BC28485EAE4/UNODriver.app/UNODriver
Identifier:          com.app99.driver.inhouse
Version:             7.7.78 (7.7.78)
Code Type:           X86-64 (Native)
Role:                Foreground
Parent Process:      launchd_sim [49594]
Coalition:           com.apple.CoreSimulator.SimDevice.3FF0171B-E914-4058-8882-F84B91FBB07C [50659]
Responsible Process: SimulatorTrampoline [9937]

Date/Time:           2023-10-23 17:27:03.6484 +0800
Launch Time:         2023-10-23 17:24:48.4347 +0800
OS Version:          macOS 12.5.1 (21G83)
Release Type:        User
Report Version:      104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x00007f9c551e6fa4
Exception Codes: 0x0000000000000001, 0x00007f9c551e6fa4
VM Region Info: 0x7f9c551e6fa4 is not in any region.  Bytes after previous region: 266149  Bytes before following region: 45148
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      MALLOC_LARGE             7f9c5519b000-7f9c551a6000 [   44K] rw-/rwx SM=PRV
--->  GAP OF 0x4c000 BYTES
      MALLOC_LARGE             7f9c551f2000-7f9c551ff000 [   52K] rw-/rwx SM=PRV
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [73121]

Triggered by Thread:  11

Thread 0::  Dispatch queue: com.apple.main-thread
0   libsystem_platform.dylib      	    0x7ff834c2e668 _platform_bzero$VARIANT$Haswell + 104
1   CoreGraphics                  	    0x7ff808de9aac CGBlt_fillBytes + 243
2   CoreGraphics                  	    0x7ff808e00c5f argb32_mark + 32105
3   CoreGraphics                  	    0x7ff808ee4f5c RIPLayerBltShape + 1194
4   CoreGraphics                  	    0x7ff808dde5a6 ripc_Render + 330
5   CoreGraphics                  	    0x7ff808de0644 ripc_DrawRects + 477
6   CoreGraphics                  	    0x7ff808dede68 CGContextFillRects + 115
7   CoreGraphics                  	    0x7ff808dedf4a CGContextFillRect + 138
8   CoreGraphics                  	    0x7ff808dee13e CGContextClearRect + 52
9   UIKitCore                     	       0x12110cb49 _UIGraphicsBeginImageContextWithOptions + 535

Thread 11 Crashed:: didi_engine_group.1.1.ui
0   Flutter                       	       0x11988b7ad flutter::DisplayListBuilder::Restore() + 587
1   ???                           	       0x15fef7a85 ???
2   ???                           	       0x177fd9f0f ???
3   ???                           	       0x17930b4b6 ???
4   ???                           	       0x176781d3f ???
5   ???                           	       0x1717fdd33 ???
6   ???                           	       0x177fd7073 ???
7   ???                           	       0x177ffdc83 ???
8   ???                           	       0x1717fdcc8 ???
9   ???                           	       0x177fd7073 ???
10  ???                           	       0x177fe045f ???
11  ???                           	       0x1717fdc07 ???
12  ???                           	       0x177fd7073 ???
13  ???                           	       0x17932708e ???
14  ???                           	       0x1717fdd33 ???
15  ???                           	       0x177fd7073 ???
16  ???                           	       0x177ffd165 ???
17  ???                           	       0x1717fdbec ???
18  ???                           	       0x177fd7073 ???
19  ???                           	       0x1717f6022 ???
20  ???                           	       0x1717fdd33 ???
21  ???                           	       0x177fd7073 ???
22  ???                           	       0x177fe045f ???
23  ???                           	       0x1717fdc07 ???
24  ???                           	       0x177fd7073 ???
25  ???                           	       0x177fe045f ???
26  ???                           	       0x1717fdbb4 ???
27  ???                           	       0x177fd7073 ???
28  ???                           	       0x177fe045f ???
29  ???                           	       0x1717fdb98 ???
30  ???                           	       0x177fd7073 ???
31  ???                           	       0x17932708e ???
32  ???                           	       0x1717fdd33 ???
33  ???                           	       0x177fd7073 ???
34  ???                           	       0x177fe045f ???
35  ???                           	       0x1717fdbb4 ???
36  ???                           	       0x1767a54a7 ???
37  ???                           	       0x15fedbaa2 ???
38  ???                           	       0x1767a6548 ???
39  ???                           	       0x15fea7387 ???
40  ???                           	       0x17930dcee ???
41  ???                           	       0x15fea624f ???
42  ???                           	       0x15fea618a ???
43  ???                           	       0x176796f2b ???
44  ???                           	       0x1767a07a3 ???
45  ???                           	       0x160e535f7 ???
46  ???                           	       0x160e53407 ???
47  ???                           	       0x1767baa5d ???
48  ???                           	       0x14a9a3796 ???
49  ???                           	       0x133c82f16 ???
50  Flutter                       	       0x119bc746e dart::DartEntry::InvokeFunction(dart::Function const&, dart::Array const&, dart::Array const&) + 206
51  Flutter                       	       0x119bc7a60 dart::DartEntry::InvokeCallable(dart::Thread*, dart::Function const&, dart::Array const&, dart::Array const&) + 272
52  Flutter                       	       0x119f18290 Dart_InvokeClosure + 1024
53  Flutter                       	       0x11997977b tonic::DartInvokeVoid(_Dart_Handle*) + 15
54  Flutter                       	       0x119b31c8c flutter::PlatformConfiguration::BeginFrame(fml::TimePoint, unsigned long long) + 298
55  Flutter                       	       0x119b69097 flutter::RuntimeController::BeginFrame(fml::TimePoint, unsigned long long) + 43
56  Flutter                       	       0x11994ad72 flutter::Animator::BeginFrame(std::_LIBCPP_ABI_NAMESPACE::unique_ptr<flutter::FrameTimingsRecorder, std::_LIBCPP_ABI_NAMESPACE::default_delete<flutter::FrameTimingsRecorder> >) + 378
57  Flutter                       	       0x11994d878 std::_LIBCPP_ABI_NAMESPACE::__function::__func<flutter::Animator::AwaitVSync()::$_0, std::_LIBCPP_ABI_NAMESPACE::allocator<flutter::Animator::AwaitVSync()::$_0>, void (std::_LIBCPP_ABI_NAMESPACE::unique_ptr<flutter::FrameTimingsRecorder, std::_LIBCPP_ABI_NAMESPACE::default_delete<flutter::FrameTimingsRecorder> >)>::operator()(std::_LIBCPP_ABI_NAMESPACE::unique_ptr<flutter::FrameTimingsRecorder, std::_LIBCPP_ABI_NAMESPACE::default_delete<flutter::FrameTimingsRecorder> >&&) + 64
58  Flutter                       	       0x1199736e3 std::_LIBCPP_ABI_NAMESPACE::__function::__func<flutter::VsyncWaiter::FireCallback(fml::TimePoint, fml::TimePoint, bool)::$_0, std::_LIBCPP_ABI_NAMESPACE::allocator<flutter::VsyncWaiter::FireCallback(fml::TimePoint, fml::TimePoint, bool)::$_0>, void ()>::operator()() + 117
59  Flutter                       	       0x119825cb9 fml::MessageLoopImpl::FlushTasks(fml::FlushType) + 163
60  Flutter                       	       0x11982bc22 fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) + 26
61  CoreFoundation                	    0x7ff800387819 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
62  CoreFoundation                	    0x7ff800387363 __CFRunLoopDoTimer + 812
63  CoreFoundation                	    0x7ff800386ada __CFRunLoopDoTimers + 243
64  CoreFoundation                	    0x7ff800381322 __CFRunLoopRun + 2126
65  CoreFoundation                	    0x7ff8003806f7 CFRunLoopRunSpecific + 560
66  Flutter                       	       0x11982bd5f fml::MessageLoopDarwin::Run() + 65
67  Flutter                       	       0x119825bca fml::MessageLoopImpl::DoRun() + 22
68  Flutter                       	       0x11982aadd void* std::_LIBCPP_ABI_NAMESPACE::__thread_proxy[abi:v15000]<std::_LIBCPP_ABI_NAMESPACE::tuple<std::_LIBCPP_ABI_NAMESPACE::unique_ptr<std::_LIBCPP_ABI_NAMESPACE::__thread_struct, std::_LIBCPP_ABI_NAMESPACE::default_delete<std::_LIBCPP_ABI_NAMESPACE::__thread_struct> >, fml::Thread::Thread(std::_LIBCPP_ABI_NAMESPACE::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0> >(void*) + 169
69  libsystem_pthread.dylib       	    0x7ff834c3d4e1 _pthread_start + 125
70  libsystem_pthread.dylib       	    0x7ff834c38f6b thread_start + 15

Thread 12:: didi_engine_group.1.1.raster
0   libsystem_kernel.dylib        	    0x7ff834bdf97a mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff834bdfce8 mach_msg + 56
2   CoreFoundation                	    0x7ff8003868de __CFRunLoopServiceMachPort + 145
3   CoreFoundation                	    0x7ff80038102f __CFRunLoopRun + 1371
4   CoreFoundation                	    0x7ff8003806f7 CFRunLoopRunSpecific + 560
5   Flutter                       	       0x11982bd5f fml::MessageLoopDarwin::Run() + 65
6   Flutter                       	       0x119825bca fml::MessageLoopImpl::DoRun() + 22
7   Flutter                       	       0x11982aadd void* std::_LIBCPP_ABI_NAMESPACE::__thread_proxy[abi:v15000]<std::_LIBCPP_ABI_NAMESPACE::tuple<std::_LIBCPP_ABI_NAMESPACE::unique_ptr<std::_LIBCPP_ABI_NAMESPACE::__thread_struct, std::_LIBCPP_ABI_NAMESPACE::default_delete<std::_LIBCPP_ABI_NAMESPACE::__thread_struct> >, fml::Thread::Thread(std::_LIBCPP_ABI_NAMESPACE::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0> >(void*) + 169
8   libsystem_pthread.dylib       	    0x7ff834c3d4e1 _pthread_start + 125
9   libsystem_pthread.dylib       	    0x7ff834c38f6b thread_start + 15

Thread 13:: didi_engine_group.1.1.io
0   libobjc.A.dylib               	    0x7ff8000446f1 _objc_rootAllocWithZone + 41
1   Metal                         	    0x7ff811bc4b91 MTLResourceListPoolCreateResourceList + 104
2   MTLSimDriver                  	    0x7ff82d201066 -[MTLSimCommandBuffer initWithQueue:retainedReferences:] + 176
3   MTLSimDriver                  	    0x7ff82d201f25 -[MTLSimCommandQueue commandBufferWithDescriptor:] + 71
4   Flutter                       	       0x11977e467 GrMtlCommandBuffer::Make(id<MTLCommandQueue>) + 135
5   Flutter                       	       0x119780307 GrMtlGpu::commandBuffer() + 45
6   Flutter                       	       0x119780836 GrMtlGpu::uploadToTexture(GrMtlTexture*, SkIRect, GrColorType, GrMipLevel const*, int) + 420
7   Flutter                       	       0x119782c9b GrMtlGpu::onWritePixels(GrSurface*, SkIRect, GrColorType, GrColorType, GrMipLevel const*, int, bool) + 77
8   Flutter                       	       0x1196d8909 GrGpu::writePixels(GrSurface*, SkIRect, GrColorType, GrColorType, GrMipLevel const*, int, bool) + 481
9   Flutter                       	       0x1196d8569 GrGpu::createTexture(SkISize, GrBackendFormat const&, GrTextureType, skgpu::Renderable, int, skgpu::Budgeted, skgpu::Protected, GrColorType, GrColorType, GrMipLevel const*, int, std::_LIBCPP_ABI_NAMESPACE::basic_string_view<char, std::_LIBCPP_ABI_NAMESPACE::char_traits<char> >) + 471
10  Flutter                       	       0x1196e7c43 GrResourceProvider::createTexture(SkISize, GrBackendFormat const&, GrTextureType, GrColorType, skgpu::Renderable, int, skgpu::Budgeted, skgpu::Mipmapped, skgpu::Protected, GrMipLevel const*, std::_LIBCPP_ABI_NAMESPACE::basic_string_view<char, std::_LIBCPP_ABI_NAMESPACE::char_traits<char> >) + 721
11  Flutter                       	       0x1196dfc1c std::_LIBCPP_ABI_NAMESPACE::__function::__func<GrProxyProvider::createMippedProxyFromBitmap(SkBitmap const&, skgpu::Budgeted)::$_0, std::_LIBCPP_ABI_NAMESPACE::allocator<GrProxyProvider::createMippedProxyFromBitmap(SkBitmap const&, skgpu::Budgeted)::$_0>, GrSurfaceProxy::LazyCallbackResult (GrResourceProvider*, GrSurfaceProxy::LazySurfaceDesc const&)>::operator()(GrResourceProvider*&&, GrSurfaceProxy::LazySurfaceDesc const&) + 402
12  Flutter                       	       0x1196ebc74 GrSurfaceProxyPriv::doLazyInstantiation(GrResourceProvider*) + 130
13  Flutter                       	       0x1196de57c GrProxyProvider::createProxyFromBitmap(SkBitmap const&, skgpu::Mipmapped, SkBackingFit, skgpu::Budgeted) + 638
14  Flutter                       	       0x1196f29c8 make_bmp_proxy(GrProxyProvider*, SkBitmap const&, GrColorType, skgpu::Mipmapped, SkBackingFit, skgpu::Budgeted) + 239
15  Flutter                       	       0x1196f2aa1 GrMakeUncachedBitmapProxyView(GrRecordingContext*, SkBitmap const&, skgpu::Mipmapped, SkBackingFit, skgpu::Budgeted) + 172
16  Flutter                       	       0x1197316bd SkImages::CrossContextTextureFromPixmap(GrDirectContext*, SkPixmap const&, bool, bool) + 399
17  Flutter                       	       0x119b17e70 std::_LIBCPP_ABI_NAMESPACE::__function::__func<flutter::UploadRasterImage(sk_sp<SkImage>, fml::WeakPtr<flutter::IOManager> const&, fml::tracing::TraceFlow const&)::$_1, std::_LIBCPP_ABI_NAMESPACE::allocator<flutter::UploadRasterImage(sk_sp<SkImage>, fml::WeakPtr<flutter::IOManager> const&, fml::tracing::TraceFlow const&)::$_1>, void ()>::operator()() + 86
18  Flutter                       	       0x119828a06 fml::SyncSwitch::Execute(fml::SyncSwitch::Handlers const&) const + 56
19  Flutter                       	       0x119b177f1 std::_LIBCPP_ABI_NAMESPACE::__function::__func<fml::internal::CopyableLambda<flutter::ImageDecoderSkia::Decode(fml::RefPtr<flutter::ImageDescriptor>, unsigned int, unsigned int, std::_LIBCPP_ABI_NAMESPACE::function<void (sk_sp<flutter::DlImage>, std::_LIBCPP_ABI_NAMESPACE::basic_string<char, std::_LIBCPP_ABI_NAMESPACE::char_traits<char>, std::_LIBCPP_ABI_NAMESPACE::allocator<char> >)> const&)::$_1::operator()()::'lambda'()>, std::_LIBCPP_ABI_NAMESPACE::allocator<fml::internal::CopyableLambda<flutter::ImageDecoderSkia::Decode(fml::RefPtr<flutter::ImageDescriptor>, unsigned int, unsigned int, std::_LIBCPP_ABI_NAMESPACE::function<void (sk_sp<flutter::DlImage>, std::_LIBCPP_ABI_NAMESPACE::basic_string<char, std::_LIBCPP_ABI_NAMESPACE::char_traits<char>, std::_LIBCPP_ABI_NAMESPACE::allocator<char> >)> const&)::$_1::operator()()::'lambda'()> >, void ()>::operator()() + 1025
20  Flutter                       	       0x119825cb9 fml::MessageLoopImpl::FlushTasks(fml::FlushType) + 163
21  Flutter                       	       0x11982bc22 fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) + 26
22  CoreFoundation                	    0x7ff800387819 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
23  CoreFoundation                	    0x7ff800387363 __CFRunLoopDoTimer + 812
24  CoreFoundation                	    0x7ff800386ada __CFRunLoopDoTimers + 243
25  CoreFoundation                	    0x7ff800381322 __CFRunLoopRun + 2126
26  CoreFoundation                	    0x7ff8003806f7 CFRunLoopRunSpecific + 560
27  Flutter                       	       0x11982bd5f fml::MessageLoopDarwin::Run() + 65
28  Flutter                       	       0x119825bca fml::MessageLoopImpl::DoRun() + 22
29  Flutter                       	       0x11982aadd void* std::_LIBCPP_ABI_NAMESPACE::__thread_proxy[abi:v15000]<std::_LIBCPP_ABI_NAMESPACE::tuple<std::_LIBCPP_ABI_NAMESPACE::unique_ptr<std::_LIBCPP_ABI_NAMESPACE::__thread_struct, std::_LIBCPP_ABI_NAMESPACE::default_delete<std::_LIBCPP_ABI_NAMESPACE::__thread_struct> >, fml::Thread::Thread(std::_LIBCPP_ABI_NAMESPACE::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0> >(void*) + 169
30  libsystem_pthread.dylib       	    0x7ff834c3d4e1 _pthread_start + 125
31  libsystem_pthread.dylib       	    0x7ff834c38f6b thread_start + 15

Thread 14:: didi_engine_group.1.1.profiler
0   libsystem_malloc.dylib        	    0x7ff800195b81 nanov2_malloc + 127
1   CoreFoundation                	    0x7ff80031195b -[__NSArrayM insertObject:atIndex:] + 292
2   IOKit                         	    0x7ff801ae7c40 IOCFUnserializeBinary + 1438
3   IOKit                         	    0x7ff801aec5fe IORegistryEntryCreateCFProperties + 106
4   Flutter                       	       0x11952e715 flutter::ProfilerMetricsIOS::GenerateSample() + 201
5   Flutter                       	       0x119509008 std::_LIBCPP_ABI_NAMESPACE::__function::__func<-[FlutterEngine startProfiler]::$_0, std::_LIBCPP_ABI_NAMESPACE::allocator<-[FlutterEngine startProfiler]::$_0>, flutter::ProfileSample ()>::operator()() + 22
6   Flutter                       	       0x119b6c894 std::_LIBCPP_ABI_NAMESPACE::__function::__func<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0, std::_LIBCPP_ABI_NAMESPACE::allocator<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0>, void ()>::operator()() + 40
7   Flutter                       	       0x119825cb9 fml::MessageLoopImpl::FlushTasks(fml::FlushType) + 163
8   Flutter                       	       0x11982bc22 fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) + 26
9   CoreFoundation                	    0x7ff800387819 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
10  CoreFoundation                	    0x7ff800387363 __CFRunLoopDoTimer + 812
11  CoreFoundation                	    0x7ff800386ada __CFRunLoopDoTimers + 243
12  CoreFoundation                	    0x7ff800381322 __CFRunLoopRun + 2126
13  CoreFoundation                	    0x7ff8003806f7 CFRunLoopRunSpecific + 560
14  Flutter                       	       0x11982bd5f fml::MessageLoopDarwin::Run() + 65
15  Flutter                       	       0x119825bca fml::MessageLoopImpl::DoRun() + 22
16  Flutter                       	       0x11982aadd void* std::_LIBCPP_ABI_NAMESPACE::__thread_proxy[abi:v15000]<std::_LIBCPP_ABI_NAMESPACE::tuple<std::_LIBCPP_ABI_NAMESPACE::unique_ptr<std::_LIBCPP_ABI_NAMESPACE::__thread_struct, std::_LIBCPP_ABI_NAMESPACE::default_delete<std::_LIBCPP_ABI_NAMESPACE::__thread_struct> >, fml::Thread::Thread(std::_LIBCPP_ABI_NAMESPACE::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0> >(void*) + 169
17  libsystem_pthread.dylib       	    0x7ff834c3d4e1 _pthread_start + 125
18  libsystem_pthread.dylib       	    0x7ff834c38f6b thread_start + 15

Flutter Doctor output
Doctor output
Using Flutter Wrapper: 3.13.8
[✓] Flutter (Channel stable, 3.13.8, on macOS 12.5.1 21G83 darwin-x64, locale zh-Hans-CN)
    • Flutter version 3.13.8 on channel stable at /Users/didi/.taco/flutter/3.13.8/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (6 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
    • Android SDK at /Users/didi/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.79.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (3 available)
    • iPhone 14 (mobile) • 3FF0171B-E914-4058-8882-F84B91FBB07C • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1
      (simulator)
    • macOS (desktop)    • macos                                • darwin-x64     • macOS 12.5.1 21G83 darwin-x64
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 118.0.5993.88

[!] Network resources
    ✗ A network error occurred while checking "https://github.com/": Operation timed out

! Doctor found issues in 1 category.

Hi @Vadaski
I checked the issue on the latest master channel. The crash didn't happen but there is overflowed issue. Please try on master channel and confirm.

Output log (RenderFlex overflowed issue)
flutter: ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
flutter: The following assertion was thrown during layout:
flutter: A RenderFlex overflowed by 320 pixels on the right.
flutter:
flutter: The relevant error-causing widget was:
flutter:   Row
flutter:   Row:file:///Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/reproduce_issues_2/lib/crash_137131.dart:47:32
flutter:
flutter: The overflowing RenderFlex has an orientation of Axis.horizontal.
flutter: The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and
flutter: black striped pattern. This is usually caused by the contents being too big for the RenderFlex.
flutter: Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the
flutter: RenderFlex to fit within the available space instead of being sized to their natural size.
flutter: This is considered an error condition because it indicates that there is content that cannot be
flutter: seen. If the content is legitimately bigger than the available space, consider clipping it with a
flutter: ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex,
flutter: like a ListView.
flutter: The specific RenderFlex in question is: RenderFlex#512cc OVERFLOWING:
flutter:   creator: Row ← Padding ← ClipPath ← DecoratedBox ← ConstrainedBox ← Container ← Column ←
flutter:     _SingleChildViewport ← IgnorePointer-[GlobalKey#7d977] ← Semantics ← Listener ← _GestureSemantics
flutter:     ← ⋯
flutter:   parentData: offset=Offset(0.0, 0.0) (can use size)
flutter:   constraints: BoxConstraints(w=35.0, h=24.0)
flutter:   size: Size(35.0, 24.0)
flutter:   direction: horizontal
flutter:   mainAxisAlignment: start
flutter:   mainAxisSize: max
flutter:   crossAxisAlignment: center
flutter:   textDirection: ltr
flutter:   verticalDirection: down
flutter: ◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤
flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-x64, locale en-VN)
    • Flutter version 3.13.8 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (6 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio Giraffe.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio Giraffe.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 14.0 23A344 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 118.0.5993.96

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.16.0-15.0.pre.69, on macOS 14.0 23A344 darwin-x64, locale en-VN)
    • Flutter version 3.16.0-15.0.pre.69 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e4eecba71c (76 minutes ago), 2023-10-23 22:41:32 -0400
    • Engine revision bdbd105885
    • Dart version 3.3.0 (build 3.3.0-53.0.dev)
    • DevTools version 2.28.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio Giraffe.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio Giraffe.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 14.0 23A344 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 118.0.5993.96

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Thanks for such a quick response, this question may require you to swipe the screen, or try hot reload, basically there is a high probability of reproduction, I will now test whether the master branch can be reproduced

This really can't be reproduced on the master branch, I tried switching back to the 3.13.8 stable branch, and it was still stable to reproduce. It's possible that this issue has already been fixed on the master branch, can we merge the fix code in master on subsequent hotfix versions of 3.13? And how to determine which submission is effective for this issue, I still have no clue, if there is any information that needs me, I will respond promptly, thank you! @huycozy

I attempted to fix the overflowed issue temporarily and the crash didn't appear (on stable 3.13.8). Even so, I will keep this issue open as it still causes fatal crash on stable channel as the initial report.

Updated sample code (fix overflowed issue)
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  Widget buildSaveLayerContainer() => Container(
        decoration: BoxDecoration(
          borderRadius: BorderRadius.circular(4),
        ),
        clipBehavior: Clip.antiAliasWithSaveLayer,
        width: 35,
        height: 24,
      );

  Widget buildSaveLayerContainerWithChild({required Widget child}) => Container(
        decoration: BoxDecoration(
          borderRadius: BorderRadius.circular(4),
        ),
        clipBehavior: Clip.antiAliasWithSaveLayer,
        width: 35,
        height: 24,
        child: child,
      );

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: Scaffold(
        body: buildSaveLayerContainerWithChild(
          child: Stack(children: [
            Stack(
              children: [
                SingleChildScrollView(
                  child: Column(
                    children: List.generate(
                      1000,
                      (index) => buildSaveLayerContainerWithChild(
                        child: Row(
                          children: [
                            buildSaveLayerContainer(),
                            Flexible(
                              child: Container(
                                height: 60,
                                color: Colors.white,
                                padding: const EdgeInsets.symmetric(horizontal: 20),
                                child: Row(
                                  children: [
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                    buildSaveLayerContainer(),
                                  ],
                                ),
                              ),
                            ),
                          ],
                        ),
                      ),
                    ),
                  ),
                )
              ],
            ),
          ]),
        ),
      ),
    );
  }
}

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-x64, locale en-VN)
    • Flutter version 3.13.8 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (6 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio Giraffe.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio Giraffe.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 14.0 23A344 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 118.0.5993.96

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.16.0-15.0.pre.93, on macOS 14.0 23A344 darwin-x64, locale en-VN)
    • Flutter version 3.16.0-15.0.pre.93 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision dcbb2de0ad (19 minutes ago), 2023-10-24 19:45:26 -0700
    • Engine revision 6e09ee14e2
    • Dart version 3.3.0 (build 3.3.0-56.0.dev)
    • DevTools version 2.28.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio Giraffe.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio Giraffe.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.9 19H365
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 14.0 23A344 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 118.0.5993.117

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Does this issue reproduce on the beta channel with the 3.16 beta?

@zanderso The issue doesn't occur on beta 3.16.0-0.3.pre.

flutter doctor -v (beta)
[!] Flutter (Channel beta, 3.16.0-0.3.pre, on macOS 14.0 23A344 darwin-x64, locale en-VN)
    • Flutter version 3.16.0-0.3.pre on channel beta at /Users/huynq/Documents/GitHub/flutter_beta
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_beta. Consider adding /Users/huynq/Documents/GitHub/flutter_beta/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_beta. Consider adding /Users/huynq/Documents/GitHub/flutter_beta/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 476aa717cd (7 days ago), 2023-10-19 20:10:52 -0500
    • Engine revision 91cde06da0
    • Dart version 3.2.0 (build 3.2.0-210.3.beta)
    • DevTools version 2.28.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio Giraffe.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio Giraffe.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 14.0 23A344 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 118.0.5993.117
    ! Error: Browsing on the local area network for iPad. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

If this crash does not reproduce on the 3.16 beta, then we'll need to bisect between the 3.13 branch point and the 3.16 branch point in order to identify the change that fixed the crash.
However, since we're so late in the 3.13 cycle, my advice would be to either try the workaround suggested above and eliminate any RenderFlex overflow errors in the test or application code, or to use the 3.16 beta, which will be promoted stable in a matter of weeks.

Since this issue is fixed on the beta and main branch, I will go ahead and close it to be in alignment with our triage process, but we can continue discussing the bisect and/or need for a CP here.


In the example from setfit.modeling import SetFitBaseModel, SKLearnWrapper, sentence_pairs_generation, get an error after importing

Traceback (most recent call last):
File "/home/xzhou/paper-baseline/AncSetfit-main/train.py", line 3, in
from setfit.modeling import SetFitBaseModel, SKLearnWrapper, sentence_pairs_generation
ImportError: cannot import name 'SetFitBaseModel' from 'setfit.modeling' (/home/xzhou/miniconda3/envs/baselines-setfit/lib/python3.9/site-packages/setfit/modeling.py)
I looked at the setfit.modeling file that doesn't have these classes

It worked when I reinstalled the setfit package with version 0.6.0.


fix(report): Fix permission check for set up email report on charts/dashboards. Fixes #21559

SUMMARY
set up email report button should be enabled for users who have "menu_access on Manage" permission. However, the previous implementation only checks if the first role associated with the user has the required permission, not the others. For those who were granted with the permission through other roles, they won't be able to see the button.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before

After

TESTING INSTRUCTIONS
I have tested with our own superset stack. With the same set of permissions, before the change, the user couldn't see the button. But after the change, the button shows up.
ADDITIONAL INFORMATION

[X] Has associated issue: https://github.com/apache/superset/issues/21559
[X] Required feature flags: ALERT_REPORTS needs to be enabled
[X] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

added test is failing.

Yeah I noticed my tests were written based on an old commit head and the way it fetches user has been changed. Fixed.


Apply fix for deleted item record

What Bug fix for DEC-237 - relational integrity issue when item deleted that is attached to a showcase
Why It's a bug!
How Created a conditional in the relevant view that tests for the existence of the item in question

Coverage remained the same at 93.76% when pulling 19c98b0a59f9a4e9804ea10bebeb4af049facda6 on DEC-237 into cd3a40d5637098b9800fc4084998b20117fe3652 on master.

Coverage decreased (-0.02%) to 93.75% when pulling 611ad24f11a731b2db6e38db777cd314279eec2a on DEC-237 into cd3a40d5637098b9800fc4084998b20117fe3652 on master.

:+1:

:+1:


Clicking "Run All" runs cell out of order

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Clicking "Run All" at the top runs cell out of order. Same issue as #2316 which was closed without a solution.
I tried debugging this by adding cells via the "+Code" button at the top, vs via hovering at the bottom of a cell and clicking "+Code (Add Code Cell)", vs via "Shift+Enter" at the last cell to auto-create the next cell. No method was consistent or fixed this out-of-order cell execution bug.
Another interesting anomaly: when I tried deleting the problem cell/cells (the ones running out of order), it completely changed the order of the remaining cells, causing cells that originally ran in order to no longer run in order. Quite confusing and inconvenient. As with #2316 I had no issues running cells in order if I highlighted the top cell and quickly clicked "Shift+Enter+Enter+Enter...etc".
Some cells have large outputs and clicking "Clear All Outputs" fixed the issue one time, but it was not a consistent fix.
Sometimes I click "Shift+Enter+Enter+Enter..." and later switch to clicking "Run All", this sometimes triggers the issue but not always.
VS Code Version
1.92.2
Jupyter Extension Version
v2024.8.1
Jupyter logs
I don't see a Jupyter Output panel anywhere, nor a Jupyter Show Output option.

Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to trace
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel (use the command Jupyter: Show Output to get to the logs).


Native exception is thrown when calling requestPurchase after upgrading to 10.0.1

Native exception is thrown when calling requestPurchase after upgrading to 10.0.1
I'm trying to upgrade my library to v10.0.1 and I can't solve this issue. It happens when using the iOS emulator

react-native-iap: 10.0.1
react-native: 0.69.4
Platforms (iOS, Android, emulator, simulator, device): iOS emulator

this is my method:
    async requestPurchase(productId) {
        try {
            const result = await requestPurchase({ productId });
            console.log('purchased successfully');
        } catch (error) {
            console.log('could not purchase');
        }
    }

Attached a screenshot of the exception.
Please advise

I have tried it in every possible way
This is what I get when I use await requestPurchase({ sku: productId });:

@yanush are you sure you ran yarn? because the parameter name appAccountToken is no longer in the code base. I'm thinking that it could be a regression but it could also be that you are not using the version you think. Please let us know

@andresesfm im seeing a similar issue here only on android devices. I am on rn-iap version 10.0.1, react native 0.68.2. platforms: android only
Unfortunately when the error occurs, I dont see any error message provided in the logs. Strangely enough, the google play store dialog opens, while the app crashes in the background.

@hkeithk This is for an iOS issue please create a separate issue using the provided template

@yanush please try requestPurchase({ sku:productId });

Seems like it was fixed in the latest version (10.0.5)
Thanks


Dynamically create schedule which will be added to the user set of calendars on Google Calendar

The biggest things to note in this PR is:

SchedulerGenerationServlet.java. -- The MAIN Servlet in which we generate the schedule
UserPreferences.java is where we will UPDATE the user settings.
 This is just for the MVP.
@chrisc94 @maricarol3355 @cjhbh3 @ptai7

LGTM Payton!


[bug] Anchor tag not opening link in default browser

Describe the bug
When I create an anchor tag with target="_blank" and a href to some other domain and click on that anchor, the link does not get opened in the default browser but in a new tauri window.
Reproduction
The code base is in a private company repo, but I can share the code snippet. I use svelte if that is for relevance.

                Learn more
                <Icon IconName="external-link" />

Startup tauri
Click on the link.

Expected behavior
The link should normally open in the default browser.
Platform and versions
Environment
  › OS: Windows 10.0.22000 X64
  › Webview2: 103.0.1264.62
  › MSVC:
      - Visual Studio Build Tools 2019
  › Node.js: 16.13.2
  › npm: 8.1.2
  › pnpm: Not installed!
  › yarn: 1.22.18
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 1.0.0
  › @tauri-apps/api [NPM]: 1.0.0-rc.5
  › tauri [RUST]: 1.0.0,
  › tauri-build [RUST]: 1.0.0,
  › tao [RUST]: 0.11.2,
  › wry [RUST]: 0.18.3,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:3000/
  › framework: Svelte

App directory structure
  ├─ .git
  ├─ .github
  ├─ .vscode
  ├─ dist
  ├─ node_modules
  ├─ public
  ├─ src
  └─ src-tauri

Stack trace
No response
Additional context
No response

Do you have shell.open enabled in your allowlist?
Also, you should update @tauri-apps/api to a non-rc version too.

Do you have shell.open enabled in your allowlist?

I am not the rust developer for this project, but in tauri.conf.json the allowlist is set to:
{
    "all": true
}

Also, you should update @tauri-apps/api to a non-rc version too.

I assume the docs tell me how to update a rust crate, because I don't know how (as I stated, I am not a rust dev).

@tauri-apps/api is not a Rust crate, it's an NPM package.

Okay, so I updated @tauri-apps/api to version 1.0.2 but the problem is sadly not fixed.

Didn't expect it to fix it, that was mainly just to not get any other problems in the future 😅
What does the link roughly look like? Because i can't reproduce this at all. The only thing (other than a special-case url) i could imagine would be that your frontend bundler removes the target for whatever reason, but even than the behavior would be different (it would open the link in the current tauri window)

The link looks like this: https://********/optimizations/1 (domain censored).
This is happening in dev mode.
I just realized something even more weirder, I have another link with a target="_blank" on a different svelte page, on which works fully as intended. I don't know what is happening...
The other link:

            {$_("login.newHere.2")}
            <Icon height="18px" width="18px" IconName="arrow-forward" />

The URL: https://********/register (domain censored, same domain as other link).

We can find the issue if you share a minimal repo we can use to reproduce it.

Well, I would need some time to create a reproduction repo, as the app I am working on is closed source, and I am under a NDA.
I would need some time for that though.

Here is my solution (vue)
Html
<button class="btn btn-primary" @click.prevent="openFacebookPage">  Contact us</button>

JavaScript
import { open } from '@tauri-apps/api/shell';
const openFacebookPage = () => {
  open("https://www.facebook.com/aiocean.io/")
}

I used that solution too, but it sadly wont work with everything. for example, in one place i need to put in translations, and inside of that translations is an anchor tag. That way I cant call svelte/vue component functions from that control.
{@html $_("optimizer.tagWarning.messages." + warningTag.tag, {
                values: {
                    tweak: warningTag.optimization.name,
                    beginFeatureBreaking: `<a class="underline" href="${warningTag.optimization.learnMore}" target="_blank">`,
                    endFeatureBreaking: "",
                    beginReportProblem: `<a class="underline" href="${config.reportProblemLink}" target="_blank">`,
                    endReportProblem: "",
                },
            })}

An entire HTML element in a translation value is crazy though, you could probably just translate the URL.

An entire HTML element in a translation value is crazy though, you could probably just translate the URL.

Would it be smart to put an HTML element in the translations? Also, this doesn't change the tauri issue.

If you only translate the URL then you could use the workaround calling open directly. I'm just waiting for a reproduction example to fix the issue.

If you only translate the URL then you could use the workaround calling open directly. I'm just waiting for a reproduction example to fix the issue.

Totally agree. If you still want to translate whole DOM. you have to listen to the click event then call open.

if you want to jump into app to chrome when click on button you can use this code in angular
shell.open("example.com")

Here is my solution (vue)
Html
<button class="btn btn-primary" @click.prevent="openFacebookPage">  Contact us</button>

JavaScript
import { open } from '@tauri-apps/api/shell';
const openFacebookPage = () => {
  open("https://www.facebook.com/aiocean.io/")
}

This works for me !  ❤❤❤

I found the best approach:

In Cargo.toml `tauri = {version = "x.y z", features = [..., "shell-open"] }
In tauri.conf.json

"tauri": {
    "allowlist": {
      "shell": {
        "open": true // enable opening files/URLs using the default program
      }
    }
  }

Hope that helps

Closing this due to OP's inactivity and the missing reproduction. Once a reproduction is provided we will reopen this issue, thanks :)

I have a theory as to what the original user, or maybe others, were experiencing! The Tauri shell plugin injects this event listener for use in opening links with target = _blank. Under most circumstances it works fine of course, but if there is an element within the anchor tag that also has a click event listener, and it calls event.stopPropagation(), then Tauri's event will never get triggered.
This could (I say could because I don't know if this could introduce unknown bugs, haven't looked that deep) be solved by simply passing true to the addEventListener call, which is to enable useCapture (MDN Docs). Consider the following example (JSFiddle):
document.addEventListener('DOMContentLoaded', () => {
  const s1 = document.querySelector('#one span')
  const s2 = document.querySelector('#two span')
  const a1 = document.querySelector('#one a')
  const a2 = document.querySelector('#two a')

  s2.addEventListener('click', (e) => {
    e.stopPropagation()
    e.preventDefault()
  })

  a1.addEventListener('click', (e) => {
    console.log('It\'s me, anchor one!')
  })

  a2.addEventListener('click', (e) => {
    console.log('It\'s me, anchor two! But you\'ll never see this message...')
  })

  a2.addEventListener('click', (e) => {
    console.log('It\'s me, anchor two! But this time I work, because addEventListener is passed "true"!')
  }, true)
})

      Click me! I will log to the console!

      Click me! I will NOT log to the console!

I have been experiencing this in both v1 and v2 for like, actual years, and would love to see even just a shoe-horned-in option to pass somewhere that will make the shell plugin pass true :P

The solution In Cargo.tomltauri = {version = "x.y z", features = [..., "shell-open"] }  no longer works.  The feature shell-open is not available for tauri v2.  What is the proper way to have all external links with target="_blank" open in the default browser window and not in the tauri window..  I do not want to have to use shell open('http://...) in my frontend code for each link I want to open in a new browser.  Example code for vue3
<a :href="`${getAuthUrl}`" target="_blank">Login to your Account here and
                  enter your authorization code in the field below. Then click get access key.

Since target is blank this should open in the default browser window.  Thanks.

Figured it out.  For v2 if you are using the tauri cli you can run npm run tauri add shell this will setup the plugin correctly and since the open command is allowed by default you do not have to setup any permissions. Once shell is installed _blank is respected and all links are opened in the default browser, otherwise without shell installed it will open inside of the tauri window.


Extend current ImageConfig to allow more values to images as well as …

What this PR does:
Part of the implementation of https://github.com/k8ssandra/k8ssandra-operator/issues/532
Which issue(s) this PR fixes:
Fixes https://github.com/k8ssandra/k8ssandra-operator/issues/532
Fixes #636
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CHANGELOG.md updated (not required for documentation PRs)
[x] CLA Signed:  DataStax CLA

PR still missing modifications to ImagePullPolicy for certain imageTypes in the CassandraDatacenter spec..

@burmanm, should we close this?
We've had some evolutions lately that might cover this already?

You mean merge? We haven't merged any changes to master.

no, I mean is it still something we want to do?
Recently you've extended the capabilities of the imageConfig, allowing to add new images dynamically and dealing with defaults more efficiently.

Recently you've extended the capabilities of the imageConfig, allowing to add new images dynamically and dealing with defaults more efficiently.

Yes, in this PR, not anywhere else. We haven't changed imageConfig properties in anyway elsewhere. That includes HCD version overrides or namespace overrides for airgaps. They are all in this PR only.
Do we not want those features anymore? I thought there was a customer request for the override namespace registry.


More browsers

Are there any plans to add any more browsers? I usually use Chrome Canary or Firefox Nightly for development but that isn't listed in the dropdown. Also Safari?

I'll add an extra path field for custom installations here https://github.com/microsoft/vscode-livepreview/issues/514


Doesn't seem to work for me

Hi there,
here's my nuxt.config buildModules section:
 buildModules: [
    [
      'k-domains',
      {
        subDomains: ['app'],
        rootDomain: 'root',
      },
    ],
    [
      '@nuxtjs/router',
      {
        keepDefaultRouter: true, // this line is mandatory...
      },
    ],
  ],

and so I expect  app.myDomain/ to render the index.vue inside my pages/app directory
similarly, I expect myDomain/ to render the index.vue inside my pages/root directory
Instead I get a This page could not be found nuxt error:

Am I missing something?
thanks!

Can you share your pages tree?
i guess you may have an index.vue page in pages directory

Hey thanks for the reply, here's my page tree:
pages
   /app
       index.vue
       /otherPage
       /otherPage
   /root
      index.vue
      /otherPage

Oh the white-colored text is actually the footer of the page, so the error is "Page is not found".
Should I not have an index.vue in my pages directory?

@miketeix did you ever get a solution to this? I'm having the same problem.

@miketeix did you ever get a solution to this? I'm having the same problem.
I also get the following warnings when building nuxt begins building. I don't know if related or not;

No router.js found in [project_directory]
no proxy defined on top-level

you need to add the k-domains first in the nuxt.config.js or at least before the @nuxtjs/router module,
the warning no router.js found is coming from the @nuxtjs/router.


Top K Frequent Elements

Java code

hi @vaquarkhan ! thank you for the contribution! a solution already exists in java for this problem. if your solution is unique, feel free to add it to the existing file! see contribution guidelines for more details


merge: support gitea

used in yaml

      - name: Build Changelog
        id: github_release
        uses: https://proxy.ankio.top/dreamncn/release-changelog-builder-action@v3
        with:
          platform: "gitea" # your code platform，just support gitea and github
          baseUrl: "https://gitea.com" # if you used gitea official platform，no need to provide it.
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

if you want to extends to support more platform：

extend BaseRepository class and implement the corresponding functions
add your class to main.ts in line 10

 const supportedPlatform = {
   github: GithubRepository,
   gitea: GiteaRepository
 }

I find some errors , I closed it now.


Stop Feature

Does the pause/play button stop or just pause the audio? If it doesn't stop, is it possible to add the stop feature?
The stop feature ends the current audio completely, and when switched to another row it starts playing the new row instead of continuing from the last row that was playing. The stop feature may be in the form of another button next to the play/pause button.
On the other hand, that feature could be implemented right when the user switched to another row. (For some reason, I think this might cause some sort of problem/trouble, somehow.)

As of now, when the row is switched, the player should start from the beginning on that new row. I haven't been able to test it for safari, but it should behave that way everywhere else.

Okay, I think it does work on Safari too.
Another thing I've noticed: in Firefox and Chrome:

when I play row 1, for example
and go to row 2 while row 1 is playing
then click on pause/play button, in this case it pause row 1 audio
then click on pause/play button again, row 1 continues to play
after row 1 finished, click on the pause/play button again
row 2 now continues

Since the audio last shorter on Safari, that might be why this doesn't happen on Safari.
(test3.csv was used)

Regarding the last comment, both Firefox and Chrome still seems to be doing the same thing I've described earlier, the continuing last row after switching to another row thing.

Looks like my fix to #129 broke my previous fix for this issue. It should be working now.

Yup, it's working again.


[backport/v1.20] repo: Dev 1.20.7

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @pradeepcrao

LGTM

cc @mattklein123 i think it would be good to land this as ideally if create patch releases for multiple release branches we do it in order
that way, the releases carry correct info about earlier releases
i would like to do a round of patch releases now to bump the distroless container (again) and preferably before publising a 1.23.1 bugfix release

on that note it would be really helpful if google published a distroless:nonroot-noopenssl flavour - it would remove the need to keep updating these images for a problem that wont affect us directly


Update Korean version to 1.3

Hello, Hugo! I'm Woochul.
First of all, thank you for writing this awesome guide. It helped me a lot.
I was reading this guide translated in korean. But I found it is version 1.1.
So, I started to update korean translation version to 1.3 carefully. And now, I finished to update korean translation version to 1.3.

Hello, that is fantastic! I will have a look at it this weekend. Thank you so much. :)

This is merged, thank you so much for your high quality work. ✨


[Project Idea] Upgrading event-generator and automating Falco performance testing

Description
Falco is a real-time security tool designed to detect abnormal behaviours and security-related runtime events in Linux systems and the cloud. The event-generator is an utility within the Falco ecosystem that helps testing Falco’s detection capabilities. The tool also has benchmark capabilities that represent a building block of the Falco performance testing practices. However, the project received less attention than required in the past few years and would require some care and renovation. This Google Summer of Code project proposes upgrading the event-generator to improve its testing and benchmarking capabilities, its reliability, and its consistency, and developing new Continuous Integration pipelines based on it. The end goal is to evolve the event-generator and make it the standard tool for systematically assessing the correctness and performance of Falco’s threat detection capabilities at every release and development cycle
Expected outcome
The project will result in an extended version of the event-generator tool that reliably generates a consistent number of events per second and stresses the most common detection scenarios of Falco. This enhanced utility will be integrated into Falco’s Continuous Integration (CI) pipeline, allowing for efficient systematic monitoring of performance regressions while ensuring alignment with past benchmarking results. Eventually, this could originate new performance optimizations in Falco itself. A stretch goal for the mentee would be to become an official maintainer of the event-generator project and/or of other repositories of the Falco ecosystem
Recommended Skills
Go programming language, familiarity with continuous integration, understanding of performance benchmarking concepts
cc @alacuku

This has been proposed to the CNCF org for the Google Summer of Code 2024 in https://github.com/cncf/mentoring/pull/1169

Hey @octonawish-akcodes, I would suggest having a look to these docs: https://github.com/falcosecurity/event-generator#benchmark and more in general to Falco and event-generator.

As the creator of the event-generator, I'm just more than happy to see this. :star_struck:
I will be happy to share my knowledge and help.

Hello @jasondellaluce , @leogr .
I am looking forward to become a GSoC student in this project !

Hi @jasondellaluce sir i am also interested in this project for GSoC 2024.

Hi @jasondellaluce sir i am also interested in this project for GSoC 2024.

Hi everyone! Love to see good interest in the project! Please make sure to follow the GSoC application process, we're looking forward to seeing this project succeed!

Hello @leogr @jasondellaluce @alacuku I hope this message finds you well. My name is Parveen Rikhari, and I've recently come across the Falco Event Generator project on GitHub. I'm keen on contributing to this project and have been considering it for my GSoC 2024 proposal.It would be incredibly beneficial if you could provide guidance on the event generator project, as it will enable me to learn, contribute, and enhance my proposal.
Thank you

Hey folks, I'm very happy to see all this interest in the event generator. By the way, I'm receiving a lot of private requests asking for guidance on the event generator. I would recommend you all open an issue on the project repository and ask your questions. In this way, we will share the knowledge easily and quickly.
:pray:

Hello @jasondellaluce, @alacuku, and @leogr,
I hope this message finds you well. As we delve deeper into our GSoC project, I would greatly appreciate it if we could discuss in more detail about the specific tasks we'll be tackling beyond the integration of the event-generator into the Falco CI pipeline
Like what exactly "upgrading the event-generator" means, only adding wide range of events(That triggers default falco rules)? Or is there anything more to tackle?
If you can share anything more about this project idea it would be more helpful for us 😀❤

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale


Improve twiddle access for FFT

We implemented Bowers et al. "Improved Twiddle Access for Fast Fourier Transforms"
https://doi.org/10.1109/TSP.2009.2035984
In our experiments this is 10%+ faster than the existing DIT.
The algorithm turns out to be surprisingly simple because it's just like DIT, but with a DIF butterfly! 🤯
The key is that, by rearranging the computation, the twiddle is now constant within the inner-most loop, so you have less memory accesses. Because it was simple enough, I've also manually unrolled the case wˆ0 to save 1 mul.
Two things we didn't do (it's prob safer if you look at them later):

The roots_table is no longer a table, we just need 1 row. So you could slightly simplify the API.
I'm not sure I fully understood the trick with $r>0$ and sparse matrix... I clearly left the test so this new implementation is correct. However I removed that code, IMO with this new algo you no longer get that improvement, but I might be incorrect.

In summary:

less memory for root_table (only 1 row)
less memory access with const twiddle
pretty much same algorithm & code complexity (just a diff butterfly)
removed the special case for $r>0$, but unrolled the case $wˆ0$ (trying to maintain simplicity vs extreme perf)
in our experiments this is 10%+ faster in pretty much all cases we tested

Interesting, thanks for the contribution! Probably @unzvfu or @nbgl would be best to review.
It looks like fft_root_table may have a couple issues with the n=1 edge case; could you try (temporarily) changing the fft_and_ifft test to use let degree = 1usize;?

That’s a really neat trick! Looks good at first glance. I’ll need to refamiliarize myself with this (dense) code to do a thorough review, so pls be patient :)

@nbgl btw we looked at your py code for cache-oblivious. We believe we did something similar in hardware, we call it multi-layer, the idea is to reduce the number of times you cycles through all the data, and while you have a bulk of data you do multiple ntt layers on that. In hw we implemented 3 and 6 stages, that leads to exactly 3x and 6x perf.
In sw we didn't really do any analysis but it's definitely interesting. In our experience this is completely orthogonal to the twiddles trick, so you can benefit from both. I can't share the paper publicly yet because it's under review, but if you reach out via email I'm definitely happy to send it over, if you're looking into this stuff.

@0x0ece The cache-oblivious FFT algorithm is not actually my invention; see [1]. The benefit is that you get asymptotically better cache complexity, and of course memory becomes the main bottleneck for big enough inputs.
[1] Matteo Frigo, Charles E. Leiserson, Harald Prokop, and Sridhar Ramachandran. 2012. Cache-Oblivious Algorithms. ACM Trans. Algorithms 8, 1, Article 4 (January 2012), 22 pages. https://doi.org/10.1145/2071379.2071383

Oh, I should mention: vectorization only happens on x86 with AVX2 or AVX-512 when compiled with -Ctarget-cpu=native. That’s how I usually test PackedFields code

Thank you much @nbgl, I merged your commits. Sorry I didn't realized the -Ctarget-cpu=native, will make sure to use it in future, thank you for the hint!
As for the cache, I guess what I wanted to say is that following the literature approach there's a risk on the transpose.
It's similar to this code here, you can save in ram in shuffled location, or you could save in order and then call the reverse_index_bits_in_place. The latter is slower (about 100ms at 2ˆ24) because you're writing twice.
What we developed is essentially a streaming version of the transpose. Again, we did it for FPGA, but it'd be nice to see if it also works in software.

Hi @nbgl, just checking in to see if you need anything else for this PR.

Hello!
This PR has been open for a long time, please review and update as following:

If this PR is no l longer relevant, close it.
If this PR is relevant but not read, mark it as Draft and make a comment of what else needs to be done.
Fix any issues and get it merged / reviewed by 10/27/2023.

If there's no update by 10/27/2023 this PR will be closed.

Hey @0x0ece, apologies for never getting back to you!
I think we could still be interested in merging this. Could you rebase with latest main, so that we can proceed with another round of review?
Also I believe the comment from @nbgl to keep using the r parameter hasn't been applied, was there any particular rationale against this?


Add documentation for attributes_for_super_diff

By default, when SuperDiff is constructing a diff for two instances of the same PORO, it will list each instance variable in the class along with its value. As SuperDiff inspects values recursively, in certain cases this diff may unhelpfully produce a lot of output. To mitigate this, you can give your PORO class an attributes_for_super_diff method. SuperDiff will then use this method to list key/value pairs instead.
This fact is buried in the gem. In the absence of extensive documentation we should probably mention it the README, under the Configuration section. It might also be good to recommend implementing ==, since if you're implementing attributes_for_super_diff you probably also want to implement ==.

I think this has been resolved by #225, specifically https://github.com/splitwise/super_diff/pull/225/files#diff-42748c8eb0945ca999ed767e3bc9481068e029207049709f7b8dfd9f75fbf537R143. There's no mention of also overriding ==. Presumably the latter is needed in cases where matching fails on some attribute not indicated by attributes_for_super_diff.


Update login.html

Enable mysql
Need change "resources\app\map\config\config.ini"
[Database]
Type: sqlite
Database_Name:
Database_User:
Database_Pass:
Database_Host:
or
[Database]
Type: mysql
Database_Name: pokemap
Database_User: root
Database_Pass: root
Database_Host: localhost

The goal of this project is easy setup, not running a server. MySQL has a lot more dependencies and introduces a ton more complexity, so it's not a feature I want to support in the desktop app. If you want to run under MySQL, you're better off using https://github.com/AHAAAAAAA/PokemonGo-Map.


Menu test branch

As far as I'm concerned, we've currently 'fixed' the outstanding issues and have a system that works, especially once we've implemented your suggestion of putting all the abilities back into one list and tagging them by type.
Originally posted by @IJW-Wartrader in https://github.com/GameBrains/er-core/issues/10#issuecomment-860752151

While thinking about navigation and the special abilities section, I thought of an alternative to listing the whole lot alphabetically, but without hiding them all by nesting them within the four ability types.
Put the types and the abilities at the same level, and use Antora's/Asciidoc's standard formatting to pick out the types.
The current commit uses bold italic for some, and bold highlighted for others, so that they can be compared.

What do you think about this as an alternative? I'm slightly hesitant about an alphabetical list because that lumps the Data sheet modifiers in with all the other abilities, and once you're playing a game you don't care about them.
Hmm. Maybe even keep the Data sheet modifiers within a nested sub-level.

P.S. Just for curiosity, I added Jump Packs links in two places and it didn't cause anything to crash when building the site. When you go to the Jump Packs page, both navigation menu items are in bold, but the breadcrumb navigation at the top of the page says that it's a Data sheet modifier, as expected as that's where it appears first.

Although the formatting in the menu navigation is also used in the breadcrumb navigation. Which isn't too surprising when you think about it. This version hasn't been committed yet.

P.S. There is no pull request for this branch, as it is just for testing purposes.

I see what you're trying to do, but I'm always wary of visual trickery that isn't backed by something more concrete. One thing here is that it is problematic when a 'parent' topic like 'Unit abilities' is no longer actually a parent.
Further to our video chat, I've done something a bit different, but with the same general goal in mind.

One flat list of all abilities, alphabetical order. [Minor quibble: Although the file system puts assault-1.adoc before assault.adoc, I'm not sure that we should do the same for 'Assault +1' and 'Assault'...]
Note the new topic at the head of the list: This explains the types in one place. I could've put all this back into special-abilities-adoc, but I didn't like how long it made that topic and it felt like it made sense as a discrete topic. I think it works fine as the first topic in the list, and I have done similar elsewhere.
Note the ability 'labels' in the Jump Packs topic. I played around a bit with CSS, but for a couple of reasons I went with a quick and dirty solution instead — just plain text in the monospace 'code' styling. If we don't like how it appears in search snippets in future then we can cross that bridge when we come to it.

What do you think?

Oh, and what I was saying about giant ToC for a long section on mobile view — ignore that, I was thinking about the in-page ToC, which is different anyway. (And because we use good topic-based writing, the in-page ToC never gets to be giant.)

That looks good. In the long run it would be great if we could add the ability types as tags, and when you click on the tag you get a list of all abilities with that tag. But I suspect that doing that in Antora is going to involve manual creation of those lists.

Going off on a (big?) tangent, this discussion has helped me work out why the navigation on the Remastered site felt so 'weird' at first. Clicking on items in the navigation menu was unpredictable and never worked quite as expected.
In hindsight, navigation items that I expected to be disclosure buttons turned out to be links to new pages, instead of being disclosure buttons. So I'd click on a line with a disclosure triangle, expecting the 'standard' behaviour where this shows the next level of items in the navigation menu, and suddenly I'd be on a new page and the navigation menu had closed the sub-section I was previously looking at, instead of showing me both sub-sections at once!
Without having consciously worked this out, this is why my original version of the Special Abilities menu had non-linked headers for each type of ability, and kept the descriptions of the abilities in another page - each type of ability in the section now worked as expected, and you could open and close each type-section independently without ending up on a new page unexpectedly.
Looking at it all more carefully in a desktop browser, docs.antora.org and (less consistently) docs.asciidoc.org have the top-level sections as non-linking items so that they work as disclosure buttons, and the lower level ones that are links have a :hover underline behaviour to show that they are links, and the small disclosure triangle still works as a disclosure triangle.
Summary - I don't think there are any easy fixes. But we need to bear in mind that the default Antora navigation, if all menu items are links, is not easy to use on mobile devices where there is no :hover behaviour, and where the disclosure triangle icons are too small to work as touchable parts of the interface.
It might be worth making the top-level menu items ('Main rules' 'The Movement phase', etc.) into non-linking items, but obviously that would be more complex than simply changing the nav.adoc files as it would require restructuring the actual sections and pages. :-(

That looks good. In the long run it would be great if we could add the ability types as tags, and when you click on the tag you get a list of all abilities with that tag. But I suspect that doing that in Antora is going to involve manual creation of those lists.

Yes, there's nothing built in to handle that type of behaviour as far as I know, so it would require some kind of custom coding -- or possibly there is an extension already that could do it. (I stumbled across some at one point, but only took a brief look and didn't work out how to use them.)
It'd be nice to have as contributors, but I don't think players would use the feature much though would they? I'm struggling to think of when a player would especially want to see only a list of 'detachment abilities' for example, as opposed to just looking up a specific ability in the alphabetical list. Do you have use cases in mind?

Going off on a (big?) tangent...

Interesting. I never encountered anything that I thought was atypical or unexpected here. It did exactly what I expected.
I generally avoid having menu items that you click but that don't link to an actual topic. From experience, it nearly always results in an uneven experience because at some point you want to cross-reference to it as the section parent. So I write and structure in such a way that there is always a proper section parent topic, that is, an actual page rather than just a navigation item. Also, depending on the system and context, the empty navigation header doesn't always play nicely when it comes to a print version...

expecting the 'standard' behaviour where this shows the next level of items in the navigation menu

In my experience, that isn't standard at all, unless we're talking at cross-purposes. I only expect that when I click on the little triangle. That is harder on mobile, but we can probably fix that with CSS in due course.

Looking at it all more carefully in a desktop browser, docs.antora.org and (less consistently) docs.asciidoc.org have the top-level sections as non-linking items so that they work as disclosure buttons, and the lower level ones that are links have a :hover underline behaviour to show that they are links, and the small disclosure triangle still works as a disclosure triangle.

Yeah, I don't like such inconsistencies. Hence my remarks above about uneven experience and structuring with a proper topic instead.

Summary - I don't think there are any easy fixes. But we need to bear in mind that the default Antora navigation, if all menu items are links, is not easy to use on mobile devices where there is no :hover behaviour, and where the disclosure triangle icons are too small to work as touchable parts of the interface.
It might be worth making the top-level menu items ('Main rules' 'The Movement phase', etc.) into non-linking items, but obviously that would be more complex than simply changing the nav.adoc files as it would require restructuring the actual sections and pages. :-(

As above, I prefer the opposite solution: Make mobile UI easier to use, don't use odd tricks with empty section navigation headers. Plus, while disclosure of a section without actually browsing to the section (and closing the existing section) is occasionally nice, I've personally never found it to be a critical feature.

Meantime, if you don't have any objection to the current implementation on this branch, I'd be happy to go ahead and merge it into master -- I think we agree that it is at least more user-friendly than the current four sections?

I've now added the 'tags' to every ability topic in the branch. So, ready to merge I think.

Meanwhile, if you don't have any objection to the current implementation on this branch, I'd be happy to go ahead and merge it into master -- I think we agree that it is at least more user-friendly than the current four sections?
[Well, need to add the rest of the 'tags' first of course.]

Fine by me!

Done! Now live on the site. Nice.


Feature: Added building via npm run scripts.

Hey @midknight41,
This should fix issue #2.
Do we want to think about removing the dist files from git? If the CI server is able to build them on it's own now then they shouldn't really be stored in GIT anymore.
Regards,

Coverage remained the same at 100.0% when pulling 53279a73cdc586f0baadc3a839d2c2416c401acd on blacksun1:master into 086840c398565ab9240d6cc16d985756a275d08a on midknight41:master.

They should come out for sure but I'd want to test the npm publish workflow first.


Rename indexables to indexable_uris

Motivation
Addresses https://github.com/Shopify/ruby-lsp/pull/2916#discussion_r1859285417
Rename indexables to indexable_uris, which is a much clearer name.

Merge activity

Nov 27, 2:45 PM EST: A user merged this pull request with Graphite.


feat: remove readonly constraint from response related types

TL; DR: Go to every type that ends with ...Response.ts and remove readonly keywords.
A good type-system prevents problems from happening - that's why, by default, the given params to a async function in the client most be readonly. So they can't be modified while the promise is being resolved in background. Here is an example:
client.search('foo', params).then(console.log);
params.foo = 'bar'; // TYPE-ERROR: because those params may still be used inside the `search` function.

In the other hand, having readonly responses prevents the user from doing manipulations to the response object, and that's is annoying:
const response await client.search('foo', params);
delete response.hits; // TYPE-ERROR: grrrrrr
const myCustomObject = response;

Since having readonly responses add no value to the user or to us, to fix this problem, go to every type that ends with ...Response.ts and remove readonly keywords.

cc @francoischalifour

@francoischalifour Maybe would be cool to have actually fixing the problem. Is a good first issue for having you in touch with the source code.

Could we maybe expose it behind a generic? i.e. if you pass some parameters (not sure what), we could do type DeepWriteable<T> = { -readonly [P in keyof T]: DeepWriteable<T[P]> }; on the result type
Or the other way round, search<Mutability = ReadOnly> { return Mutability<xxx> } where you could pass the DeepWriteable manually?
Not sure if either of those options are something users think about though

@Haroenv You will have to explain me that in a zoom call, sorry.


Fix AccessLevelControl breaking

#29987 did an oopsie
This broke the ID computer, station records, and maybe some others too.
cc @Winkarst-cpu

I remember testing this and it's worked fine... Sorry anyway, my mistake...


vscodium: update script artifact names have changed

The vscodium project is now releasing artifacts with slightly different naming: VSCodium-darwin-${VSCODIUM_VER}.zip is now VSCodium-darwin-x64-${VSCODIUM_VER}.zip. This is likely due to arrival of the new ARM-based macs. In any case, it does mean that we need to update update-vscodium.sh to pull the correct artifact down.

Motivation for this change
The current update script is broken.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc maintainers @synthetica @turion


Error when using in Wails：[SSR Router - r86fbc1ba]"Navigation error"

// App.svelte
<script lang="ts">
  import { RouterView } from '@dvcol/svelte-simple-router/components'

  const routes = [
    {
      component: () => import('./A.svelte'),
      name: 'home',
      path: '/',
    },
    {
      component: () => import('./B.svelte'),
      name: 'b',
      path: '/b',
    },
  ] as const

  const options = {
    routes,
  } as const
</script>

<RouterView {options} />

hello @dvcol
The same code works in Electron but throws an error in wails.
[SSR Router - r86fbc1ba]"Navigation error"
Unhandled Promise Rejection: Error: Navigation failed: NAVIGATION_ABORTED

From the error stacks, it seems that the Promise prototype doesn't have withResolvers().
Support is quite good on the browser side, but maybe you might need a polyfill for wails?


Update README.md

Edited README.md regarding compilation of lex

@mashhoor-ahdal thanks for your interest in contributing! but, why would you prefer gcc over cc?

Oh , I see...

@mashhoor-ahdal thanks for your interest in contributing! but, why would you prefer gcc over cc?

Oh , I see... Sorry for the inconvenience

um... I didn't mean to demotivate, apologies if that sounded so. rather I was wondering the reason/advantage for using gcc!

@mashhoor-ahdal thanks for your interest in contributing! but, why would you prefer gcc over cc?

Oh , I see... Sorry for the inconvenience

um... I didn't mean to demotivate, apologies if that sounded so. rather I was wondering the reason/advantage for using gcc!

ok no worries, there is no advantage btw


muen: Drop explicit FPU initialization

The MXCSR register is initialized to the default value [1] so there is
no need to explicitly set it.
NOTE: The ABI version is unchanged since there has not been a Solo5 (or
Muen) release since it was raised to 2.
[1] - Muen commit f10bd6b

Thanks, LGTM. E2E error is random CI flakiness.


Replace deprecated usage of fs.unlink with fs.unlinkSync, and make compatible with tesseract 4

With node v10, a callback is required with fs.unlink, resulting in an error with the current code. I have replaced the call to fs.unlink with fs.unlinkSync.
Also, with tesseract 4, it seems that an additional hyphen is required for the "psm" argument. I have added this as well.

Existing pull requests provide these updates.


Pre-compile some date regexes

Precompiling some regexes in date.py offers some speedup, as compiling static regexes on every function call is pointless.
Before:

After:

Test file:
import dateparser

for i in range(1000):
    date = dateparser.parse(" " * i + "12.18.2015")

Codecov Report

Merging #293 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #293      +/-   ##
==========================================
+ Coverage   94.42%   94.44%   +0.01%
==========================================
  Files          34       34
  Lines        2960     2969       +9
==========================================
+ Hits         2795     2804       +9
  Misses        165      165

Impacted Files
Coverage Δ

dateparser/date.py
93.13% <100%> (+0.31%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2726c47...8e65276. Read the comment docs.


[TC-487] Multi Site Origin config gets applied even when no valid parents

If MSO is not properly configured with origin servers but is configured with multi site origin, it will install the multi site origin parent.config with no parent servers listed.
   (Mine had the origin servers in a non ORG type cache group, this generated parent="" in the config)
   parent.config: dest_domain=google.com port=443 parent="" ...
   Jul 12 01:26:46 lab-ats-mid-2.local traffic_server[3916]:
{0x2ae9206f1940}
 ERROR: [ParentSelection] No parents specified at line 2
Author: Matt Mills
JIRA Link: https://issues.apache.org/jira/browse/TC-487
Found Version: 2.1.0

we need better validation to ensure that MSO is configured properly.


[ST] < UI issue for ezETH Router and nextWETH >

Describe the bug

Currently there is an UI affecting the current balance of routers of ezETH/nextWETH when they try to add liquidity. It shows them they have 0 ezETH even they are holding those assests. (Affecting two routers)

Also, one of the router had an issue where they couldn't wrap their ezETH on mainnet ETH. They mentioned clicking on wrap doesn't do anything for them (Browser: Firefox/ wallets: Coinbase extension and metamask)

Another LP tried to add some nextWETH on the pools, but their balance shows 0 nextWETH

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
@oncall

@A-Keyboard Are you able to provide additional details on the last bullet point?

Another LP tried to add some nextWETH on the pools, but their balance shows 0 nextWETH

I've been able to get an approval request going on nextWETH without issue. Is there maybe some more info/context on how to trigger the bug there?

I haven't been able to reproduce any bugs when wrapping or adding liquidity.
I've been working off the latest main-sync-with-cutover branch as of aa2dc21, and tried a bunch of different routers. All tokens showed balances (0 or otherwise) and allowed me to initiate a wrap when the balance was available.

@OnCall Today I encountered a related issue, but for a user. User has necessary ezETH in wallet, yet balance didn't show for nextETH and for ezETH.
Solution ended up being deactivating his VPN. VPN is interfereing with some layer of data pulling. User demands it to be fixed.
TICKET: https://discord.com/channels/454734546869551114/1231995967931416651

On issue bullet 3 of the original post:
We're still seeing issues with selecting tokens from the router add liquidity modal. For example:

User has no balance of nextWETH on Arbitrum. They select nextWETH from the dropdown. Then the UI changes it to WETH:

They should never be supplying router liquidity in nextAssets on non-ETH chains.

@just-a-node need to force it.  It is a blocker for some LPs to add additional liquidity (Mesh LP and dialectic).

https://github.com/connext/frontend/pull/56

@regexpressyourself See my comments in https://github.com/connext/frontend/pull/56#issuecomment-2084440281.

Deploy here: https://frontend-connextscan-ui-git-sm-sof-6033-9394b0-connext-979dc950.vercel.app/

@regexpressyourself  #5724 and #6010 are included or not?

@regexpressyourself #5724 and #6010 are included or not?

@ekbainova I don't believe so

Let's deploy it separately from #6020 today. @just-a-node