CupertinoDatePicker interface freezes during scrolling

Steps to reproduce

Set the maximum and minimum years
Scroll the day, month, and year tabs up and down at the same time

Expected results
Scrolling fine
Actual results
The interface becomes unresponsive after scrolling for tens of seconds
Code sample
Code sample
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  DateTime initDate = DateTime(
      DateTime
          .now()
          .year,
      DateTime
          .now()
          .month,
      DateTime
          .now()
          .day,
      0,
      0,
      0,
      0,
      0);

  MyHomePage({Key? key, required this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            SizedBox(
              width: 300.0,
              height: 300.0,
              child: CupertinoDatePicker(
                mode: CupertinoDatePickerMode.date,
                onDateTimeChanged: (value) {
                  print('value = $value');
                  widget.initDate = DateTime(
                      value.year,
                      value.month,
                      value.day,
                      0,
                      0,
                      0,
                      0,
                      0);
                },
                minimumYear: DateTime
                    .now()
                    .year - 5,
                maximumYear: DateTime
                    .now()
                    .year,
                maximumDate: DateTime.now(),
                initialDateTime: DateTime(widget.initDate!.year, widget.initDate!.month, widget.initDate!.day),
              ),),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/12441461/98785769-7eb2-4620-b83b-a18aebfad00d
[Upload media here]

Logs
Logs
I/flutter (21512): value = 2019-11-11 00:00:00.000
I/flutter (21512): value = 2019-12-11 00:00:00.000
I/flutter (21512): value = 2018-12-11 00:00:00.000
I/HiTouch_HiTouchSensor(21512): HiTouch Setting Switch, ON
I/HiTouch_HiTouchSensor(21512): isSecurityImePopup:false
I/flutter (21512): value = 2018-02-11 00:00:00.000
I/HiTouch_HiTouchSensor(21512): mIsHiTouchEnabled: true isSecurityImePopup: false mIsLandscapeOrient: false mIsInMultiWindowMode: false isGameMode: false
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2018-01-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2018-12-11 00:00:00.000
I/flutter (21512): value = 2018-11-11 00:00:00.000
I/flutter (21512): value = 2018-10-11 00:00:00.000
I/flutter (21512): value = 2018-09-11 00:00:00.000
I/flutter (21512): value = 2018-08-11 00:00:00.000
I/flutter (21512): value = 2018-07-11 00:00:00.000
I/flutter (21512): value = 2018-06-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2018-05-11 00:00:00.000
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2018-04-11 00:00:00.000
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:7.0, limit is:60The moving distance of Y is:62.0, limit is:60
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2019-04-11 00:00:00.000
I/flutter (21512): value = 2020-04-11 00:00:00.000
I/flutter (21512): value = 2021-04-11 00:00:00.000
I/flutter (21512): value = 2021-03-11 00:00:00.000
I/flutter (21512): value = 2022-03-11 00:00:00.000
I/flutter (21512): value = 2022-02-11 00:00:00.000
I/flutter (21512): value = 2023-02-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2023-01-11 00:00:00.000
I/flutter (21512): value = 2023-12-11 00:00:00.000
I/flutter (21512): value = 2023-11-11 00:00:00.000
I/flutter (21512): value = 2023-10-11 00:00:00.000
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2023-09-11 00:00:00.000
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:39.0, limit is:60The moving distance of Y is:113.0, limit is:60
I/HiTouch_HiTouchSensor(21512): HiTouch Setting Switch, ON
I/HiTouch_HiTouchSensor(21512): isSecurityImePopup:false
I/HiTouch_HiTouchSensor(21512): mIsHiTouchEnabled: true isSecurityImePopup: false mIsLandscapeOrient: false mIsInMultiWindowMode: false isGameMode: false
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2023-08-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2023-07-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2022-07-11 00:00:00.000
I/flutter (21512): value = 2022-06-11 00:00:00.000
I/flutter (21512): value = 2021-06-11 00:00:00.000
I/flutter (21512): value = 2020-06-11 00:00:00.000
I/flutter (21512): value = 2020-05-11 00:00:00.000
I/flutter (21512): value = 2019-05-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2019-04-11 00:00:00.000
I/flutter (21512): value = 2019-03-11 00:00:00.000
I/flutter (21512): value = 2019-02-11 00:00:00.000
I/flutter (21512): value = 2019-01-11 00:00:00.000
I/flutter (21512): value = 2018-01-11 00:00:00.000
I/flutter (21512): value = 2018-12-11 00:00:00.000
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:21.0, limit is:60The moving distance of Y is:77.0, limit is:60
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2019-12-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2021-12-11 00:00:00.000
I/flutter (21512): value = 2021-11-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2021-10-11 00:00:00.000
I/flutter (21512): value = 2022-10-11 00:00:00.000
I/flutter (21512): value = 2022-09-11 00:00:00.000
I/flutter (21512): value = 2023-09-11 00:00:00.000
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2023-10-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2023-11-11 00:00:00.000
I/flutter (21512): value = 2023-12-11 00:00:00.000
I/flutter (21512): value = 2023-01-11 00:00:00.000
I/flutter (21512): value = 2023-02-11 00:00:00.000
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:5.0, limit is:60The moving distance of Y is:62.0, limit is:60
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2023-03-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2023-04-11 00:00:00.000
I/flutter (21512): value = 2023-03-11 00:00:00.000
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:27.0, limit is:60The moving distance of Y is:84.0, limit is:60
I/flutter (21512): value = 2023-02-11 00:00:00.000
I/flutter (21512): value = 2023-01-11 00:00:00.000
I/flutter (21512): value = 2023-12-11 00:00:00.000
I/flutter (21512): value = 2023-11-11 00:00:00.000
I/flutter (21512): value = 2023-10-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:6.0, limit is:60The moving distance of Y is:129.0, limit is:60
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2022-10-11 00:00:00.000
I/flutter (21512): value = 2021-10-11 00:00:00.000
I/flutter (21512): value = 2021-08-11 00:00:00.000
I/flutter (21512): value = 2020-08-11 00:00:00.000
I/flutter (21512): value = 2020-06-11 00:00:00.000
I/flutter (21512): value = 2019-06-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2019-02-11 00:00:00.000
I/flutter (21512): value = 2019-12-11 00:00:00.000
I/flutter (21512): value = 2018-12-11 00:00:00.000
I/flutter (21512): value = 2018-11-11 00:00:00.000
I/flutter (21512): value = 2018-09-11 00:00:00.000
I/flutter (21512): value = 2018-07-11 00:00:00.000
I/flutter (21512): value = 2018-06-11 00:00:00.000
I/flutter (21512): value = 2018-04-11 00:00:00.000
I/flutter (21512): value = 2018-03-11 00:00:00.000
I/flutter (21512): value = 2018-01-11 00:00:00.000
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/HiTouch_HiTouchSensor(21512): HiTouch Setting Switch, ON
I/HiTouch_HiTouchSensor(21512): isSecurityImePopup:false
I/HiTouch_HiTouchSensor(21512): mIsHiTouchEnabled: true isSecurityImePopup: false mIsLandscapeOrient: false mIsInMultiWindowMode: false isGameMode: false
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:4.0, limit is:60The moving distance of Y is:70.0, limit is:60
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:4.0, limit is:60The moving distance of Y is:70.0, limit is:60
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2018-12-11 00:00:00.000
I/flutter (21512): value = 2018-11-11 00:00:00.000
I/flutter (21512): value = 2018-10-11 00:00:00.000
I/flutter (21512): value = 2018-09-11 00:00:00.000
I/flutter (21512): value = 2018-08-11 00:00:00.000
I/flutter (21512): value = 2018-07-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:14.0, limit is:60The moving distance of Y is:63.0, limit is:60
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2019-07-11 00:00:00.000
I/HiTouch_HiTouchSensor(21512): HiTouch Setting Switch, ON
I/HiTouch_HiTouchSensor(21512): isSecurityImePopup:false
I/flutter (21512): value = 2020-07-11 00:00:00.000
I/HiTouch_HiTouchSensor(21512): mIsHiTouchEnabled: true isSecurityImePopup: false mIsLandscapeOrient: false mIsInMultiWindowMode: false isGameMode: false
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2021-07-11 00:00:00.000
I/flutter (21512): value = 2021-08-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2022-08-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2022-09-11 00:00:00.000
I/flutter (21512): value = 2022-10-11 00:00:00.000
I/flutter (21512): value = 2022-11-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2022-10-11 00:00:00.000
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:21.0, limit is:60The moving distance of Y is:76.0, limit is:60
I/flutter (21512): value = 2022-09-11 00:00:00.000
I/HiTouch_HiTouchSensor(21512): HiTouch Setting Switch, ON
I/HiTouch_HiTouchSensor(21512): isSecurityImePopup:false
I/HiTouch_HiTouchSensor(21512): mIsHiTouchEnabled: true isSecurityImePopup: false mIsLandscapeOrient: false mIsInMultiWindowMode: false isGameMode: false
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2022-08-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
I/flutter (21512): value = 2022-07-11 00:00:00.000
I/flutter (21512): value = 2023-07-11 00:00:00.000
I/flutter (21512): value = 2023-06-11 00:00:00.000
I/flutter (21512): value = 2023-05-11 00:00:00.000
I/flutter (21512): value = 2023-04-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): handleTimerDrag: false
D/HwDragEnhancementImpl(21512): Start long press for hw drag enhancement.
I/flutter (21512): value = 2023-05-11 00:00:00.000
D/HwDragEnhancementImpl(21512): Touch move more than touch range.
W/HiTouch_PressGestureDetector(21512): Touch pointer move a lot. The moving distance of X is:6.0, limit is:60The moving distance of Y is:151.0, limit is:60
I/flutter (21512): value = 2023-06-11 00:00:00.000
I/flutter (21512): value = 2023-07-11 00:00:00.000
I/flutter (21512): value = 2023-08-11 00:00:00.000
D/WebViewDragEnhancement(21512): dragReset.
D/WebViewDragEnhancement(21512): dragReset cacheSize = 0
I/flutter (21512): value = 2023-02-11 00:00:00.000
I/flutter (21512): value = 2023-03-11 00:00:00.000

Flutter Doctor output
Doctor output
[✓] Flutter (Channel testing/koi/release, 3.0.0, on macOS 13.3.1 22E772610a darwin-arm (Rosetta), locale zh-Hans-CN)
    • Flutter version 3.0.0 at /Users/luffy/zcy_flutter_sdk_3_0_0
    • Upstream repository https://git.cai-inc.com/mobile-framework/flutter_sdk_3_0_0.git
    • Framework revision ee870834e3 (2 days ago), 2023-12-18 12:38:51 +0800
    • Engine revision d1b9a6938a
    • Dart version 2.17.0
    • DevTools version 2.12.2
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

⣷[compile]: command =  [pod, --version]                                                                                ⣽
[compile]: command =  [/Users/luffy/Library/Android/sdk/platform-tools/adb, -s, 7HX5T19A11005536, shell, getprop]                                             ⣻
[compile]: command =  [/Applications/Google Chrome.app/Contents/MacOS/Google Chrome, --version]                                                               ⣟
[compile]: command =  [/Users/luffy/Library/Android/sdk/platform-tools/adb, devices, -l]                                                                      [✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/luffy/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • ANDROID_HOME = /Users/luffy/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2021.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.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.85.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • LIO AL00 (mobile)          • 7HX5T19A11005536                     • android-arm64  • Android 12 (API 31)
    • iPhone 14 Pro Max (mobile) • 2F6EF803-E091-4501-971C-5A8CC16E8F54 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 13.3.1 22E772610a darwin-arm (Rosetta)
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 120.0.6099.109

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Hi @AbeiOS.
Thanks for filing this.
I can't seem to reproduce this on my end even after scrolling for quite sometime as shown in the video.
I see you are on an older version of Flutter, can you upgrade to the latest version 3.16.4 to see if this issue still persists there?

Hi @AbeiOS. Thanks for filing this. I can't seem to reproduce this on my end even after scrolling for quite sometime as shown in the video. I see you are on an older version of Flutter, can you upgrade to the latest version 3.16.4 to see if this issue still persists there?

Take it out and use it alone,

Hi @AbeiOS. Thanks for filing this. I can't seem to reproduce this on my end even after scrolling for quite sometime as shown in the video. I see you are on an older version of Flutter, can you upgrade to the latest version 3.16.4 to see if this issue still persists there?

Thanks for the reply, we are not able to upgrade at the moment. Because the old version relies on a lot of third-party libraries and codes, the cost of modification is high. It is fine for me to use 2.8.1 and 3.3.0 for Demo testing. However, version 3.0.0 has stability problems in the demo. I tried changing the two files from 3.3.0 to my project files(Not 3.0.0 SDK) : /flutter_sdk_3_3_0/packages/flutter/lib/src/cupertino/picker.dart
/flutter_sdk_3_3_0/packages/flutter/lib/src/cupertino/date_picker.dart.
but it does'nt work

Hi @AbeiOS. Thanks for filing this. I can't seem to reproduce this on my end even after scrolling for quite sometime as shown in the video. I see you are on an older version of Flutter, can you upgrade to the latest version 3.16.4 to see if this issue still persists there?

I will have a try

Hi @AbeiOS. Thanks for filing this. I can't seem to reproduce this on my end even after scrolling for quite sometime as shown in the video. I see you are on an older version of Flutter, can you upgrade to the latest version 3.16.4 to see if this issue still persists there?

Flutter SDK 3.16.4 was fine, Bug How Can I Fix it in my Flutter 3.0 SDK? Which PR or Commit Fix It？

Thanks for trying it out and for your response. Not sure which PR or commit fixed this.
But per triage policy, if an issue now works in the latest versions of flutter, then we close as fixed in newer versions.
Closing this as this has been fixed in newer versions of flutter, if you disagree, please comment and I'll reopen this.
Thank you!

Thanks for trying it out and for your response. Not sure which PR or commit fixed this. But per triage policy, if an issue now works in the latest versions of flutter, then we close as fixed in newer versions. Closing this as this has been fixed in newer versions of flutter, if you disagree, please comment and I'll reopen this. Thank you!

Ok, Thank you too!


Add support for HTTP/2

Hopefully this is in the works :-)
I just saw that Clojure now supports HTTP/2 and my LFE bones are itching to do the same.
Cowboy is working on it, currently targeted for the end of the year:

https://github.com/ninenines/cowboy/issues/853

Thoughts? Plans?

Yes, I was hoping to soon start working on adding this to Yaws.

Hurray! I use YAWS extensively in lots of different LFE applications (one of them embedded). I'm available and willing to test at any stage of the development process -- just say the word.

@vinoski any idea about the roadmap about it? What could help?

I've been busy finishing writing this book and also working to try to make dirty schedulers official for Erlang 19, so I just haven't had time to do much on this yet. The book goes to production mid-February, so perhaps I'll have some spare cycles after that. Not exactly sure what could help at this point unless someone wants to start trying to write it and then we could see how we might collaborate to finish it.

is it closed because it has been added or because you don't want to support it?

@benoitc, no, of course not.
@etnt, You close all opened issues. Is there any reason for that ?

What is the status of supporting HTTP/2 and HTTP/3?

Neither is currently supported. Only a couple requests for such support have been raised over the past few years.

what needs to be done?

Everything — design, implementation, testing, documentation.


v0.9.1 fixes a python 3.8 only bug

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Creating an Additional Environment

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.17.1
Amplify CLI Version
10.5.1
What operating system are you using?
MacOS
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
We had 3 environments, dev, test, and prod. Dev and test have been up and running and up to date for awhile and are running well.
Prod was left dormant for a very long time. I tried to git merge changes over from test to prod but it failed when I tried to check out the prod env with amplify env checkout prod.  Complaining about the APNS push notifications with the error 🛑 Failed to enable the APNS channel.
Thankfully the prod environment didn't have any important data so after some time I was able to remove the env (had issues getting over to another env but an amplify pull eventually worked when I was in the test env.)
However now when I try to create a new env I'm again plagued by the same issue and error.
See log output for details.
Also in the log you'll see the prompt at the end for the Google Web Client OD. I didn't get a chance to type anything in. The error showed up and that ended the process.
Expected behavior
Environment should be created with the provided APNS configuration.
Reproduction steps

Have a working environment with APNS push notifications working.
Execute the amplify env add command and follow the prompts.

Project Identifier
cf6680d5eea50e0f311acdd7f53684a0
Log output

# Put your logs below this line

amplify env add
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the environment prod
Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default
Adding backend environment prod to AWS Amplify app: [REDACTED]

Deployment completed.
Deployed root stack [REDACTED] [ ======================================== ] 4/4
	amplify-[REDACTED]-prod-143424 AWS::CloudFormation::Stack     CREATE_COMPLETE                Thu Jan 05 2023 14:34:55…
	DeploymentBucket               AWS::S3::Bucket                CREATE_COMPLETE                Thu Jan 05 2023 14:34:51…
	UnauthRole                     AWS::IAM::Role                 CREATE_COMPLETE                Thu Jan 05 2023 14:34:52…
	AuthRole                       AWS::IAM::Role                 CREATE_COMPLETE                Thu Jan 05 2023 14:34:51…

Deployment bucket fetched.
⠋ Initializing your environment: prod⠋ Building resource auth/[REDACTED][WARNING] @aws-cdk/core.Lazy#anyValue is deprecated.
  Use `Lazy.any()` or `Lazy.uncachedAny()` instead.
  This API will be removed in the next major release.
✔ Initialized provider successfully.
⚠ Pinpoint resource is only locally created
⚠ Run "amplify push" to deploy the Pinpoint resource and then retry...
? Choose authentication method used for APNs Key
? The bundle id used for APNs Tokens:  [REDACTED]
? The team id used for APNs Tokens:  [REDACTED]
? The key id used for APNs Tokens:  [REDACTED]
? The key file path (.p8):  [REDACTED]
✖ There was an error initializing your environment.

 You've opted to allow users to authenticate via Google.  If you haven't already, you'll need to go to https://developers.google.com/identity and create an App ID.

 Enter your Google Web Client ID for your identity pool:  🛑 Failed to enable the APNS channel.

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Some additional information (Progress?) :
I managed to get past the notification / APNS / auth issue by using the solution for a number of other tickets people have posted and that is to use amplify update auth command. Then selection Walkthrough all configs... This cleared things up and I was able to do an amplify push to a point. It appears to finish everything. Until it gets to Creating API models... and I get an error of 🛑 Cannot set property 'Id' of undefined. I ran the amplify push command with --debug and have the following log output...
Creating API models...
🛑 Cannot set property 'Id' of undefined

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

DeploymentFault: Cannot set property 'Id' of undefined
    at Object.run (/snapshot/repo/build/node_modules/amplify-provider-awscloudformation/lib/push-resources.js:450:11)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Promise.all (index 0)
    at async providersPush (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:107:5)
    at async AmplifyToolkit.pushResources [as _pushResources] (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:81:13)
    at async Object.executeAmplifyCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:212:9)
    at async executePluginModuleCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:142:5)
    at async executeCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:40:9)
    at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:153:5)

Cannot set property 'Id' of undefined
TypeError: Cannot set property 'Id' of undefined
    at analyticsPluginAPIPostPush (/snapshot/repo/build/node_modules/amplify-category-analytics/lib/analytics-resource-api.js:147:43)
    at AmplifyToolkit.invokePluginMethod [as _invokePluginMethod] (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/invoke-plugin-method.js:39:12)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async invokePostPushAnalyticsUpdate (/snapshot/repo/build/node_modules/amplify-provider-awscloudformation/lib/plugin-client-api-analytics.js:10:56)
    at async Object.run (/snapshot/repo/build/node_modules/amplify-provider-awscloudformation/lib/push-resources.js:432:17)
    at async Promise.all (index 0)
    at async providersPush (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:107:5)
    at async AmplifyToolkit.pushResources [as _pushResources] (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:81:13)
    at async Object.executeAmplifyCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:212:9)
    at async executePluginModuleCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:142:5)
    at async executeCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:40:9)
    at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:153:5)

This was the last step in the deployment as it shows 28/29 at the top of the output.
I see reference to "analytics" at the top of the second stack trace. Wondering if that is the culprit and if so, what to do about it?

This is also confirmed to be an issue with the current latest amplify cli, 10.6.1. Simpliest way to reproduce is to execute amplify analytics update.

I dove into the amplify code and started looking for pinpoint-helper.js. I'm not familiar with the code base but I did managed to find a typescript version here :
https://github.com/aws-amplify/amplify-cli/blob/dev/packages/amplify-category-analytics/src/utils/pinpoint-helper.ts
Like 99 seems to be the same function where the stack trace is pointing to and lines 103 through 105 (105 specifically) seems to show where the error is occurring. On line 105 categoryResources[resource].output.Id suggests that the "output" variable is undefined.
I searched around and found in my amplify/backend/amplify-meta.json file a section for the analytics as seen here :
"analytics": {
    "[REDACTED]": {
      "service": "Pinpoint",
      "providerPlugin": "awscloudformation",
      "providerMetadata": {
        "s3TemplateURL": "https://s3.amazonaws.com/amplify-[REDACTED]-prod-[REDACTED]-deployment/amplify-cfn-templates/analytics/pinpoint-cloudformation-template.json",
        "logicalId": "analytics[REDACTED]"
      },
      "lastPushTimeStamp": "2023-01-06T00:16:30.735Z",
      "output": {
        "appName": "[REDACTED]-prod",
        "Region": "us-west-2",
        "Id": "[REDACTED]"
      },
      "lastPushDirHash": "kCsSCYQZGs79lElhqb6zTTennfw="
    }
  }

I redacted the ID as I wasn't sure how sensitive that information is from a security standpoint but there is definitely an ID in there. Not to mention there is definitely an output section for the analytics section.
I'm not sure if any of this is helping but I'm hoping so. But I feel like this is showing that things should be working but there must be some other file that I'm not looking at the right location.
Also, one final note. I cannot remove analytics nor notifications in order to recreate them. I get the same error. Therefore rebuilding this portion from scratch is not an option. This in turn does not allow me to create a new environment from scratch either.

Actually, looking at the code again I realized that it is looking at the "notifications" section. Not the analytics.
Indeed our notifications section is missing the "output" section and therefore no Id.
"notifications": {
    "[REDACTED]": {
      "service": "Pinpoint",
      "channels": [
        "APNS"
      ]
    }

So this is clearly the issue, but I've no idea how to resolve it? I've run the amplify update auth command many times but it does not seem to resolve this.

Well, I think I've resolved the issue!!
Here's what I've done...
Because I seemed to have an incomplete notifications section in my configs (even after doing the "walkthrough" mentioned above) I loaded up my test environment and grabbed the notifications section from there. Then checked out my prod environment (with errors of course) and then replaced the notification section back into my prod env's amplify/backend/amplify-meta.json file.
Next, as it seemed the pinpoint project my my prod env had indeed been created according to the Pinpoint web console, I  edited all the Id's to be what was shown the Pinpoint console (Project ID) and the Name to be my project name -prod. I also set the creationDate and lastModifiedDates to be the same as what is in the PinPoint web console as listed under All Projects, Creation date. For reference here is the json :
"notifications": {
    "[REDACTED]": {
      "Id": "[REDACTED]", ##  set to my prod pinpoint project ID
      "ResourceName": "[REDACTED]",
      "Name": "[REDACTED]-test", ## Changed -test to -prod
      "service": "Pinpoint",
      "output": {
        "Id": "[REDACTED]", ##  set to my prod pinpoint project ID
        "Name": "[REDACTED]-test", ## Changed -test to -prod
        "Region": "us-west-2",
        "APNS": {
          "ApplicationId": "[REDACTED]", ##  set to my prod pinpoint project ID
          "CreationDate": "2022-10-20T16:54:05.277Z", ## Changed to the Creation Date according to the Pinpoint console
          "DefaultAuthenticationMethod": "Key",
          "Enabled": true,
          "HasCredential": false,
          "HasTokenKey": true,
          "Id": "apns",
          "IsArchived": false,
          "LastModifiedDate": "2022-10-29T06:28:27.103Z", ## Changed to the Creation Date according to the Pinpoint console
          "Platform": "APNS",
          "Version": 9
        },
        "regulatedResourceName": "[REDACTED]"
      },
      "lastPushTimeStamp": "2023-01-05T23:49:50.400Z"
    }
  }

Note the fields that have ## comments. Those are the ones I changed.
Next I tried to do an amplify notifications update but that failed. Complained about a file missing from the #current-cloud-backend folder. backend-config.json. Which makes sense since this env has never been successfully pushed.
I therefore did an amplify push... With SUCCESS!
Before I did this push my pinpoint application for prod had APNS disabled under Settings/Push notifications. Which is why I tried to do the amplify notifications update first. However the amplify push seemed to resolve this as after the push, and they are now enabled. I'm hoping that's all that is needed because normally the amplify notifications command configures things immediately in AWS without a push.
Will update further if I find any issues with this build as I'm going to do some testing now. But hopefully this helps someone else in future should they come across it.

Have the same problem at the moment. This is why the id is not set I guess

I tried adding the following to my team-provider-info.json to match what i have for production (which is working as expected):
"analytics": {
        "fringePinpoint": {},
        "Pinpoint": {
          "Name": "XXXXX-qa",
          "Id": "XXXXX",
          "Region": "us-east-1"
        }
      },
      "notifications": {
        "Pinpoint": {
          "Name": "XXXXX-qa",
          "Id": "XXXXX",
          "Region": "us-east-1"
        }
      }

Still getting  Cannot read property 'Id' of undefined on amplify push Also tried running amplify analytics update and amplify notifications update but no luck

This issue is fixed in latest Amplify CLI, please upgrade and try again


Plan migration from django-pipeline to new asset pipeline

User story
As a developer, I want a plan to switch to a modern asset pipeline, so that I know when we can use better asset tooling.
Acceptance criteria

[ ] Current asset generation documents are updated
[ ] Follow-on user stories are written for migration from django-pipeline

References

bug 1380419 - Refactor static asset generation
Taiga Epic 1799 - Improve static asset development
Issue #764 - Adopt a modern build / packaging toolchain

Moved the (undone) documentation piece to issue #927. I spent about half a day looking into it, and will probably spend 1/2 a day reloading that into my head again later in the week.
I added issue #928 to do the work to retire django-pipeline and move to a model where node.js does work before Django moves assets into place.


Update for ctypes >= 0.6.

See the changelog for ctypes 0.6.0 for details.

@darioteixeira feel free to merge if you've tested this.

Alright @rgrinberg, I'm merging.  The patch only introduces local opens, which is enough to fix the compilation.  It shouldn't break anything...


The date picker becomes visible after visiting the "Get Assistance" page and then returning to the form.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open Settings -> Workspaces -> Connect Bank Account Manually -> Enter invalid information for only Date of birth at step 3.
Now press Save & Continue, an error will show up.
Focus on SSN field (or any field) and check that keyboard is opened.
Scroll down and press Fix the error, scroll up and press the Date picker.
check that Date picker doesn’t shows up when pressing on it.
Press get assistance -> Press back button to get to form.
Date picker is now visible

Expected Result:
The date picker should shows up before visiting "Get Assistance" page
Actual Result:
The date picker becomes visible after visiting the "Get Assistance" page
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.2.66-0
Reproducible in staging?: y
Reproducible in production?: could not check
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/217114345-9b327b28-42df-42e9-a36b-6f83914fc8c4.mov
https://user-images.githubusercontent.com/43996225/217114421-bf258802-cbf3-4f65-831a-dd48a1bf1434.MP4
Expensify/Expensify Issue URL:
Issue reported by: @fedirjh
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675456108095039
View all open jobs on GitHub

Triggered auto assignment to @sophiepintoraetz (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@kavimuru @fedirjh - please can you confirm the platforms this is occurring on?

Closing until I have an answer.

@sophiepintoraetz I have updated the platform it is occurring.


Augment decorator should apply to derived operations

When documenting APIs that compose interfaces and operations, I should be able to document the derived interfaces independently.  The only way to do this is through augment decorators.
For example, if I want to reuse a Collection interface, I should be able to provide documentation for operations on each interface that extends that interfaces.  If I can't, then the base interface is much less useful because emitting OpenAPI or other outputs require post-processing in order to generate the desired documentation.
Currently, when using augment decorators (@summary, in this case), the decorator is applied to targets that are directly defined on the target's parent, but not on those that are part of the parent through extends even though they are both reachable through type ahead and it compiles fine.  This is confusing.
In this Playground Link, I would expect the summary for both operations to be emitted, but only the one for the non-inherited operation is emitted.

Possibly related: https://github.com/microsoft/typespec/issues/2123.

Looks like this was fixed


Add new contributor adyachok

Application for the contributor role.

This change is

Thank you @adyachok for your interesting in contributing to Kubeflow. Can you please add a couple of PRs you have merged into any Kubeflow repositories for documentation purposes.

/assign @theadactyl
Agreement signed.

Hi @adyachok would also love to see a couple of issues/prs linked. Thanks!


custom baseURL is not working

Environment

Operating System: Darwin
Node Version:     v20.11.0
Nuxt Version:     3.12.3
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools, experimental, components, modules, colorMode, fonts, auth
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
I set the following config:
  auth: {
    provider: {
      baseURL: 'https://tx8_api.test/',
      type: 'refresh',
      endpoints: {
        signIn: { path: 'login', method: 'post' },
        signOut: { path: 'logout', method: 'post' },
        signUp: false,
        getSession: { path: 'me', method: 'get' },
        refresh: { path: 'refresh', method: 'post' },
      },
      token: {
        signInResponseTokenPointer: 'data/access_token',
        cookieName: 'access_token',
        type: 'Bearer',
        maxAgeInSeconds: 60 * 60,
        sameSiteAttribute: 'strict',
      },
      refreshToken: {
        signInResponseRefreshTokenPointer: 'data/access_token',
        cookieName: 'access_token',
        refreshRequestTokenPointer: 'access_token',
        maxAgeInSeconds: 20160 * 60,
      },
      pages: {
        login: '/login',
      },
    },
  },

My backend is running in Valet  (Laravel app) exposed in https://tx8_api.test/api and my Nuxt app is exposed in port 3000
Describe the bug
When I try to login, happens this

The baseURL still the default one.
On Postman the request is successfully

Additional context
I'm following the steps to use an external backend but doesn't work for me
No response
Logs
No response

Hi @alfredomtzrmz 👋
Sadly its pretty hard for me to identify what could be going wrong. Your configuration looks correct to me. However, I am surprised that the requests are still being made to localhost and not your external backend.
Could you try and reproduce this issue in a small reproduction?

@zoey-kaiser Thanks! But now i got this error net::ERR_CERT_COMMON_NAME_INVALID and my config:
  auth: {
    baseURL: 'https://tx8_api.test/api/auth/',
    provider: {
      type: 'refresh',
      endpoints: {
        signIn: { path: 'login', method: 'post' },
        signOut: { path: 'logout', method: 'post' },
        signUp: false,
        getSession: { path: 'me', method: 'get' },
        refresh: { path: 'refresh', method: 'post' },
      },
      token: {
        signInResponseTokenPointer: 'data/access_token',
        cookieName: 'access_token',
        type: 'Bearer',
        maxAgeInSeconds: 60 * 60,
        sameSiteAttribute: 'strict',
      },
      refreshOnlyToken: false,
      refreshToken: {
        signInResponseRefreshTokenPointer: 'data/access_token',
        cookieName: 'access_token',
        refreshRequestTokenPointer: 'access_token',
        maxAgeInSeconds: 20160 * 60,
      },
      pages: {
        login: '/login',
      },
    },
  },

@zoey-kaiser nevermind, I forgot to set my virtual domain to secure 😅. Now works fine!


About the evaluation on CALVIN with checkpoint provided

Thanks for providing such a great work! Considering the large size of the CALVIN dataset, I conducted evaluations only on the debug dataset. Is this result reliable?

The performance may vary given different hardware setups and environments. We've tested with multiple evaluation seeds and the performance variation should be within (+- 0.1 Avg.Len). Can you provide further details about your test bed?

The performance may vary given different hardware setups and environments. We've tested with multiple evaluation seeds and the performance variation should be within (+- 0.1 Avg.Len). Can you provide further details about your test bed?

Sure,  I conducted evaluations only on the debug dataset.
The full output is as follows.
`[2024-10-30 19:35:50,798] torch.distributed.run: [WARNING]
[2024-10-30 19:35:50,798] torch.distributed.run: [WARNING] *****************************************
[2024-10-30 19:35:50,798] torch.distributed.run: [WARNING] Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
[2024-10-30 19:35:50,798] torch.distributed.run: [WARNING] *****************************************
pybullet build time: Nov 28 2023 23:52:03
pybullet build time: Nov 28 2023 23:52:03
pybullet build time: Nov 28 2023 23:52:03
pybullet build time: Nov 28 2023 23:52:03
[W Utils.hpp:164] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarBool)
is_using_torchrun
[W Utils.hpp:164] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarBool)
is_using_torchrun
[W Utils.hpp:164] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarBool)
is_using_torchrun
[W Utils.hpp:164] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarBool)
is_using_torchrun
device_id:  cuda:0
world_size:  4
device_id:  cuda:2
world_size:  4
device_id:  cuda:3
world_size:  4
device_id:  cuda:1
world_size:  4
Loading checkpoint from  /data1/gyh/models/CLOVER/visual_planner.pt
Loading checkpoint from  /data1/gyh/models/CLOVER/visual_planner.pt
Loading checkpoint from  /data1/gyh/models/CLOVER/visual_planner.pt
Loading checkpoint from  /data1/gyh/models/CLOVER/visual_planner.pt
[rank0]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
[rank3]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
[rank1]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
[rank2]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
[rank3]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
[rank1]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
[rank2]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
Loading policy checkpoint from  /data1/gyh/models/CLOVER/feedback_policy.pth
[rank0]:[W Utils.hpp:106] Warning: Environment variable NCCL_BLOCKING_WAIT is deprecated; use TORCH_NCCL_BLOCKING_WAIT instead (function getCvarString)
Loading policy checkpoint from  /data1/gyh/models/CLOVER/feedback_policy.pth
Loading policy checkpoint from  /data1/gyh/models/CLOVER/feedback_policy.pth
Loading policy checkpoint from  /data1/gyh/models/CLOVER/feedback_policy.pth
argv[0]=
startThreads creating 1 threads.
starting thread 0
started thread 0
argc=3
argv[0] = --unused
argv[1] =
argv[2] = --start_demo_name=Physics Server
ExampleBrowserThreadFunc started
X11 functions dynamically loaded using dlopen/dlsym OK!
X11 functions dynamically loaded using dlopen/dlsym OK!
argv[0]=
startThreads creating 1 threads.
starting thread 0
started thread 0
argc=3
argv[0] = --unused
argv[1] =
argv[2] = --start_demo_name=Physics Server
ExampleBrowserThreadFunc started
X11 functions dynamically loaded using dlopen/dlsym OK!
X11 functions dynamically loaded using dlopen/dlsym OK!
argv[0]=
startThreads creating 1 threads.
starting thread 0
started thread 0
argc=3
argv[0] = --unused
argv[1] =
argv[2] = --start_demo_name=Physics Server
ExampleBrowserThreadFunc started
X11 functions dynamically loaded using dlopen/dlsym OK!
argv[0]=
startThreads creating 1 threads.
starting thread 0
started thread 0
argc=3
argv[0] = --unused
argv[1] =
argv[2] = --start_demo_name=Physics Server
ExampleBrowserThreadFunc started
X11 functions dynamically loaded using dlopen/dlsym OK!
X11 functions dynamically loaded using dlopen/dlsym OK!
X11 functions dynamically loaded using dlopen/dlsym OK!
Creating context
Creating context
Created GL 3.3 context
Direct GLX rendering context obtained
Making context current
GL_VENDOR=Mesa/X.org
GL_RENDERER=llvmpipe (LLVM 12.0.0, 256 bits)
GL_VERSION=4.1 (Core Profile) Mesa 21.2.6
GL_SHADING_LANGUAGE_VERSION=4.50
pthread_getconcurrency()=0
Version = 4.1 (Core Profile) Mesa 21.2.6
Vendor = Mesa/X.org
Renderer = llvmpipe (LLVM 12.0.0, 256 bits)
Created GL 3.3 context
Direct GLX rendering context obtained
Making context current
Creating context
GL_VENDOR=Mesa/X.org
GL_RENDERER=llvmpipe (LLVM 12.0.0, 256 bits)
GL_VERSION=4.1 (Core Profile) Mesa 21.2.6
GL_SHADING_LANGUAGE_VERSION=4.50
pthread_getconcurrency()=0
Version = 4.1 (Core Profile) Mesa 21.2.6
Vendor = Mesa/X.org
Renderer = llvmpipe (LLVM 12.0.0, 256 bits)
Created GL 3.3 context
Creating context
Direct GLX rendering context obtained
Making context current
GL_VENDOR=Mesa/X.org
GL_RENDERER=llvmpipe (LLVM 12.0.0, 256 bits)
GL_VERSION=4.1 (Core Profile) Mesa 21.2.6
GL_SHADING_LANGUAGE_VERSION=4.50
pthread_getconcurrency()=0
Version = 4.1 (Core Profile) Mesa 21.2.6
Vendor = Mesa/X.org
Renderer = llvmpipe (LLVM 12.0.0, 256 bits)
Created GL 3.3 context
Direct GLX rendering context obtained
Making context current
GL_VENDOR=Mesa/X.org
GL_RENDERER=llvmpipe (LLVM 12.0.0, 256 bits)
GL_VERSION=4.1 (Core Profile) Mesa 21.2.6
GL_SHADING_LANGUAGE_VERSION=4.50
pthread_getconcurrency()=0
Version = 4.1 (Core Profile) Mesa 21.2.6
Vendor = Mesa/X.org
Renderer = llvmpipe (LLVM 12.0.0, 256 bits)
b3Printf: Selected demo: Physics Server
startThreads creating 1 threads.
starting thread 0
started thread 0
MotionThreadFunc thread started
b3Printf: Selected demo: Physics Server
startThreads creating 1 threads.
starting thread 0
started thread 0
MotionThreadFunc thread started
b3Printf: Selected demo: Physics Server
startThreads creating 1 threads.
starting thread 0
started thread 0
MotionThreadFunc thread started
b3Printf: Selected demo: Physics Server
startThreads creating 1 threads.
starting thread 0
started thread 0
MotionThreadFunc thread started
ven = Mesa/X.org
ven = Mesa/X.org
ven = Mesa/X.org
ven = Mesa/X.org
ven = Mesa/X.org
ven = Mesa/X.org
ven = Mesa/X.org
ven = Mesa/X.org
received depth0
received depth0
received depth0
received depth0
successfully load env
successfully load env
successfully wrapped model
logging to /tmp/evaluation
0%|                                                                                | 0/250 [00:00<?, ?it/s]successfully wrapped model
logging to /tmp/evaluation
0%|                                                                                | 0/250 [00:00<?, ?it/s]successfully load env
successfully load env
successfully wrapped model
successfully wrapped model
logging to /tmp/evaluation
0%|                                                                                | 0/250 [00:00<?, ?it/s]logging to /tmp/evaluation
1/5 : 94.4% | 2/5 : 79.6% | 3/5 : 65.6% | 4/5 : 53.2% | 5/5 : 38.4% ||: 100%|████████████████████████████████████████████| 250/250 [11:39:47<00:00, 167.95s/it]
1/5 : 94.4% | 2/5 : 79.6% | 3/5 : 62.4% | 4/5 : 49.6% | 5/5 : 36.8% ||: 100%|████████████████████████████████████████████| 250/250 [12:06:51<00:00, 174.45s/it]
1/5 : 95.2% | 2/5 : 78.4% | 3/5 : 62.4% | 4/5 : 44.8% | 5/5 : 32.8% ||: 100%|████████████████████████████████████████████| 250/250 [12:07:11<00:00, 174.53s/it]
1/5 : 95.2% | 2/5 : 78.8% | 3/5 : 56.8% | 4/5 : 43.2% | 5/5 : 33.2% ||: 100%|████████████████████████████████████████████| 250/250 [12:09:16<00:00, 175.03s/it]
Results for Epoch 0:
Average successful sequence length: 3.187
Success rates for i instructions in a row:
1: 94.8%
2: 79.1%
3: 61.8%
4: 47.7%
5: 35.3%
disconnecting id 0 from server
rotate_blue_block_right: 50 / 69 |  SR: 72.5%
move_slider_right: 230 / 236 |  SR: 97.5%
lift_red_block_slider: 81 / 110 |  SR: 73.6%
place_in_slider: 162 / 295 |  SR: 54.9%
turn_off_lightbulb: 116 / 120 |  SR: 96.7%
turn_off_led: 139 / 141 |  SR: 98.6%
push_into_drawer: 68 / 97 |  SR: 70.1%
lift_blue_block_drawer: 10 / 15 |  SR: 66.7%
lift_pink_block_slider: 92 / 112 |  SR: 82.1%
open_drawer: 303 / 306 |  SR: 99.0%
rotate_red_block_right: 52 / 69 |  SR: 75.4%
lift_pink_block_table: 139 / 157 |  SR: 88.5%
push_blue_block_left: 57 / 63 |  SR: 90.5%
close_drawer: 163 / 165 |  SR: 98.8%
push_pink_block_right: 39 / 61 |  SR: 63.9%
push_red_block_right: 39 / 66 |  SR: 59.1%
push_red_block_left: 59 / 69 |  SR: 85.5%
lift_blue_block_table: 147 / 162 |  SR: 90.7%
rotate_blue_block_left: 47 / 62 |  SR: 75.8%
place_in_drawer: 102 / 141 |  SR: 72.3%
turn_on_lightbulb: 140 / 144 |  SR: 97.2%
move_slider_left: 212 / 227 |  SR: 93.4%
rotate_red_block_left: 51 / 55 |  SR: 92.7%
turn_on_led: 146 / 151 |  SR: 96.7%
stack_block: 84 / 155 |  SR: 54.2%
push_pink_block_left: 56 / 71 |  SR: 78.9%
lift_red_block_table: 138 / 157 |  SR: 87.9%
lift_pink_block_drawer: 4 / 7 |  SR: 57.1%
rotate_pink_block_right: 58 / 66 |  SR: 87.9%
lift_blue_block_slider: 84 / 116 |  SR: 72.4%
push_blue_block_right: 29 / 65 |  SR: 44.6%
rotate_pink_block_left: 44 / 53 |  SR: 83.0%
unstack_block: 37 / 40 |  SR: 92.5%
lift_red_block_drawer: 9 / 11 |  SR: 81.8%
disconnecting id 0 from server
Best model: epoch 0 with average sequences length of 3.187
disconnecting id 0 from server
disconnecting id 0 from server
numActiveThreads = 0
stopping threads
destroy semaphore
semaphore destroyed
Thread with taskId 0 exiting
Thread TERMINATED
destroy main semaphore
main semaphore destroyed
numActiveThreads = 0
stopping threads
Thread with taskId 0 exiting
Thread TERMINATED
destroy semaphore
semaphore destroyed
destroy main semaphore
main semaphore destroyed
numActiveThreads = 0
stopping threads
destroy semaphore
semaphore destroyed
Thread with taskId 0 exiting
Thread TERMINATED
destroy main semaphore
main semaphore destroyed
numActiveThreads = 0
stopping threads
destroy semaphore
semaphore destroyed
Thread with taskId 0 exiting
Thread TERMINATED
destroy main semaphore
main semaphore destroyed
finished
numActiveThreads = 0
btShutDownExampleBrowser stopping threads
Thread with taskId 0 exiting
Thread TERMINATED
destroy semaphore
semaphore destroyed
destroy main semaphore
main semaphore destroyed
finished
numActiveThreads = 0
btShutDownExampleBrowser stopping threads
destroy semaphore
semaphore destroyed
Thread with taskId 0 exiting
Thread TERMINATED
destroy main semaphore
main semaphore destroyed
finished
numActiveThreads = 0
btShutDownExampleBrowser stopping threads
Thread with taskId 0 exiting
Thread TERMINATED
destroy semaphore
semaphore destroyed
destroy main semaphore
main semaphore destroyed
finished
numActiveThreads = 0
btShutDownExampleBrowser stopping threads
destroy semaphore
semaphore destroyed
Thread with taskId 0 exiting
Thread TERMINATED
destroy main semaphore
main semaphore destroyed`
Environment:

ubuntu: 20.04.3 LTS
Pytorch 2.2
4 A6000
conda list:
_libgcc_mutex=0.1=conda_forge
_openmp_mutex=4.5=2_gnu
absl-py=2.1.0=pypi_0
accelerate=1.0.1=pypi_0
addict=2.4.0=pypi_0
aiohappyeyeballs=2.4.3=pypi_0
aiohttp=3.10.10=pypi_0
aiosignal=1.3.1=pypi_0
antlr4-python3-runtime=4.8=pypi_0
asttokens=2.4.1=pypi_0
async-timeout=4.0.3=pypi_0
attrs=24.2.0=pypi_0
beautifulsoup4=4.12.3=pypi_0
blas=1.0=mkl
blinker=1.8.2=pypi_0
blosc=1.11.2=pypi_0
brotli-python=1.0.9=py39h6a678d5_8
bzip2=1.0.8=h5eee18b_6
ca-certificates=2024.8.30=hbcca054_0
calvin=0.0.1=dev_0
calvin-env=0.0.1=pypi_0
certifi=2024.8.30=pyhd8ed1ab_0
cffi=1.14.2=pypi_0
charset-normalizer=3.3.2=pyhd3eb1b0_0
click=8.1.7=pypi_0
clip=1.0=pypi_0
cloudpickle=3.1.0=pypi_0
cmake=3.18.4=pypi_0
colorama=0.4.6=pyhd8ed1ab_0
colorlog=6.8.2=pypi_0
comm=0.2.2=pypi_0
configargparse=1.7=pypi_0
contourpy=1.3.0=pypi_0
cuda-cudart=12.1.105=0
cuda-cupti=12.1.105=0
cuda-libraries=12.1.0=0
cuda-nvrtc=12.1.105=0
cuda-nvtx=12.1.105=0
cuda-opencl=12.6.68=0
cuda-runtime=12.1.0=0
cuda-version=12.6=3
cycler=0.12.1=pypi_0
dash=2.18.1=pypi_0
dash-core-components=2.0.0=pypi_0
dash-html-components=2.0.0=pypi_0
dash-table=5.0.0=pypi_0
decorator=4.4.2=pypi_0
diffusers=0.30.3=pypi_0
docker-pycreds=0.4.0=pypi_0
docstring-parser=0.16=pypi_0
einops=0.8.0=pypi_0
einops-exts=0.0.4=pypi_0
ema-pytorch=0.7.3=pypi_0
exceptiongroup=1.2.2=pypi_0
executing=2.1.0=pypi_0
fastjsonschema=2.20.0=pypi_0
ffmpeg=4.3=hf484d3e_0
filelock=3.13.1=py39h06a4308_0
flask=3.0.3=pypi_0
fonttools=4.54.1=pypi_0
freetype=2.12.1=h4a9f257_0
freetype-py=2.5.1=pypi_0
frozenlist=1.4.1=pypi_0
fsspec=2024.9.0=pypi_0
ftfy=6.2.3=pypi_0
gdown=5.2.0=pypi_0
gitdb=4.0.11=pypi_0
gitpython=3.1.43=pypi_0
gmp=6.2.1=h295c915_3
gmpy2=2.1.2=py39heeb90bb_0
gnutls=3.6.15=he1e5248_0
grpcio=1.66.1=pypi_0
gym=0.26.2=pypi_0
gym-notices=0.0.8=pypi_0
h5py=3.12.1=pypi_0
html-testrunner=1.2.1=pypi_0
huggingface-hub=0.25.1=pypi_0
hydra-colorlog=1.2.0=pypi_0
hydra-core=1.1.1=pypi_0
idna=3.7=py39h06a4308_0
imageio=2.36.0=pypi_0
imageio-ffmpeg=0.5.1=pypi_0
importlib-metadata=8.5.0=pypi_0
importlib-resources=6.4.5=pypi_0
intel-openmp=2023.1.0=hdb19cb5_46306
ipython=8.18.1=pypi_0
ipywidgets=8.1.5=pypi_0
itsdangerous=2.2.0=pypi_0
jedi=0.19.1=pypi_0
jinja2=3.1.4=py39h06a4308_0
joblib=1.4.2=pypi_0
jpeg=9e=h5eee18b_3
jsonschema=4.23.0=pypi_0
jsonschema-specifications=2023.12.1=pypi_0
jupyter-core=5.7.2=pypi_0
jupyterlab-widgets=3.0.13=pypi_0
kiwisolver=1.4.7=pypi_0
lame=3.100=h7b6447c_0
lazy-loader=0.4=pypi_0
lcms2=2.12=h3be6417_0
ld_impl_linux-64=2.40=h12ee557_0
lerc=3.0=h295c915_0
libcublas=<IP_ADDRESS>=0
libcufft=<IP_ADDRESS>=0
libcufile=<IP_ADDRESS>=0
libcurand=<IP_ADDRESS>=0
libcusolver=<IP_ADDRESS>=0
libcusparse=<IP_ADDRESS>=0
libdeflate=1.17=h5eee18b_1
libffi=3.4.4=h6a678d5_1
libgcc=14.2.0=h77fa898_1
libgcc-ng=14.2.0=h69a702a_1
libgomp=14.2.0=h77fa898_1
libiconv=1.16=h5eee18b_3
libidn2=2.3.4=h5eee18b_0
libjpeg-turbo=2.0.0=h9bf148f_0
libnpp=<IP_ADDRESS>=0
libnvjitlink=12.1.105=0
libnvjpeg=<IP_ADDRESS>=0
libpng=1.6.39=h5eee18b_0
libstdcxx-ng=11.2.0=h1234567_1
libtasn1=4.19.0=h5eee18b_0
libtiff=4.5.1=h6a678d5_0
libunistring=0.9.10=h27cfd23_0
libwebp-base=1.3.2=h5eee18b_0
lightning-lite=1.8.6=pypi_0
lightning-utilities=0.11.8=pyhd8ed1ab_0
llvm-openmp=14.0.6=h9e868ea_0
llvmlite=0.43.0=pypi_0
lxml=5.3.0=pypi_0
lz4-c=1.9.4=h6a678d5_1
markdown=3.7=pypi_0
markdown-it-py=3.0.0=pypi_0
markupsafe=2.1.3=py39h5eee18b_0
matplotlib=3.9.2=pypi_0
matplotlib-inline=0.1.7=pypi_0
mdurl=0.1.2=pypi_0
mkl=2023.1.0=h213fc3f_46344
mkl-service=2.4.0=py39h5eee18b_1
mkl_fft=1.3.10=py39h5eee18b_0
mkl_random=1.2.7=py39h1128e8f_0
moviepy=1.0.3=pypi_0
mpc=1.1.0=h10f8cd9_1
mpfr=4.0.2=hb69a4c5_1
mpmath=1.3.0=py39h06a4308_0
multicoretsne=0.1=pypi_0
multidict=6.1.0=pypi_0
mypy-extensions=1.0.0=pypi_0
natsort=8.4.0=pypi_0
nbformat=5.10.4=pypi_0
ncurses=6.4=h6a678d5_0
nest-asyncio=1.6.0=pypi_0
nettle=3.7.3=hbbd107a_1
networkx=3.2.1=pypi_0
numba=0.60.0=pypi_0
numpy=1.23.0=pypi_0
numpy-quaternion=2023.0.4=pypi_0
nvidia-ml-py=12.560.30=pypi_0
omegaconf=2.1.2=pypi_0
open-clip-torch=2.29.0=pypi_0
open3d=0.18.0=pypi_0
opencv-python=<IP_ADDRESS>=pypi_0
openh264=2.1.1=h4ff587b_0
openjpeg=2.5.2=he7f1fd0_0
openssl=3.3.2=hb9d3cd8_0
packaging=24.1=pyhd8ed1ab_0
pandas=2.2.3=pypi_0
parso=0.8.4=pypi_0
pexpect=4.9.0=pypi_0
pillow=10.4.0=py39h5eee18b_0
pip=24.2=py39h06a4308_0
platformdirs=4.3.6=pypi_0
plotly=5.24.1=pypi_0
proglog=0.1.10=pypi_0
prompt-toolkit=3.0.48=pypi_0
propcache=0.2.0=pypi_0
protobuf=5.28.2=pypi_0
psutil=6.0.0=pypi_0
ptyprocess=0.7.0=pypi_0
pure-eval=0.2.3=pypi_0
pybullet=3.2.6=pypi_0
pycollada=0.6=pypi_0
pycparser=2.22=pypi_0
pyglet=2.0.18=pypi_0
pygments=2.18.0=pypi_0
pyhash=0.9.3=pypi_0
pyopengl=3.1.0=pypi_0
pyparsing=3.1.4=pypi_0
pyquaternion=0.9.9=pypi_0
pyrender=0.1.45=pypi_0
pyrep=<IP_ADDRESS>=dev_0
pysocks=1.7.1=py39h06a4308_0
python=3.9.19=h955ad1f_1
python-dateutil=2.9.0.post0=pypi_0
pytorch=2.2.0=py3.9_cuda12.1_cudnn8.9.2_0
pytorch-cuda=12.1=ha16c6d3_5
pytorch-fid=0.3.0=pypi_0
pytorch-lightning=1.8.6=pypi_0
pytorch-mutex=1.0=cuda
pytz=2024.2=pypi_0
pyyaml=6.0.1=py39h5eee18b_0
readline=8.2=h5eee18b_0
referencing=0.35.1=pypi_0
regex=2024.9.11=pypi_0
requests=2.32.3=py39h06a4308_0
retrying=1.3.4=pypi_0
rich=13.9.3=pypi_0
rlbench=1.2.0=dev_0
rotary-embedding-torch=0.8.4=pypi_0
rpds-py=0.20.0=pypi_0
safetensors=0.4.5=pypi_0
scikit-image=0.24.0=pypi_0
scikit-learn=1.5.2=pypi_0
scikit-video=1.1.11=pypi_0
scipy=1.13.1=pypi_0
sentence-transformers=3.2.1=pypi_0
sentry-sdk=2.14.0=pypi_0
setproctitle=1.3.3=pypi_0
setuptools=57.5.0=pypi_0
six=1.16.0=pypi_0
smmap=5.0.1=pypi_0
soupsieve=2.6=pypi_0
sqlite=3.45.3=h5eee18b_0
stack-data=0.6.3=pypi_0
sympy=1.13.2=py39h06a4308_0
tacto=0.0.3=dev_0
tbb=2021.8.0=hdb19cb5_0
tenacity=9.0.0=pypi_0
tensorboard=2.18.0=pypi_0
tensorboard-data-server=0.7.2=pypi_0
tensorboardx=<IP_ADDRESS>=pypi_0
termcolor=2.5.0=pypi_0
threadpoolctl=3.5.0=pypi_0
tifffile=2024.8.30=pypi_0
timm=0.6.11=pypi_0
tk=8.6.14=h39e8969_0
tokenizers=0.20.0=pypi_0
torchmetrics=1.5.1=pypi_0
torchtriton=2.2.0=py39
torchvideotransforms=0.1.2=dev_0
torchvision=0.17.0=py39_cu121
tqdm=4.66.5=pyhd8ed1ab_0
traitlets=5.14.3=pypi_0
transformers=4.45.1=pypi_0
trimesh=4.4.9=pypi_0
typed-argument-parser=1.10.1=pypi_0
typing-extensions=4.11.0=py39h06a4308_0
typing-inspect=0.9.0=pypi_0
typing_extensions=4.11.0=py39h06a4308_0
tzdata=2024.2=pypi_0
urdfpy=0.0.22=pypi_0
urllib3=2.2.2=py39h06a4308_0
vc-models=0.1=dev_0
wandb=0.18.1=pypi_0
wcwidth=0.2.13=pypi_0
werkzeug=3.0.4=pypi_0
wheel=0.44.0=py39h06a4308_0
widgetsnbextension=4.0.13=pypi_0
xz=5.4.6=h5eee18b_1
yaml=0.2.5=h7b6447c_0
yarl=1.16.0=pypi_0
zipp=3.20.2=pypi_0
zlib=1.2.13=h5eee18b_1
zstd=1.5.5=hc292b87_2

Conducting evaluations with debug dataset is fine. Texting Environments are dependent upon an independent configuration file in CALVIN regradless the dataset used. However, I've noticed you are not rendering with GPU acceleration:
GL_VENDOR=Mesa/X.org
GL_RENDERER=llvmpipe (LLVM 12.0.0, 256 bits)
GL_VERSION=4.1 (Core Profile) Mesa 21.2.6
GL_SHADING_LANGUAGE_VERSION=4.50

In my hardware setup:
GL_VENDOR=NVIDIA Corporation
GL_RENDERER=NVIDIA GeForce RTX 3090/PCIe/SSE2
GL_VERSION=3.3.0 NVIDIA 535.161.07
GL_SHADING_LANGUAGE_VERSION=3.30 NVIDIA via Cg compiler

If the appropriate GPU drivers are not installed or are malfunctioning, the system may revert to using LLVMpipe for rendering.

Conducting evaluations with debug dataset is fine. Texting Environments are dependent upon an independent configuration file in CALVIN regradless the dataset used. However, I've noticed you are not rendering with GPU acceleration:
GL_VENDOR=Mesa/X.org
GL_RENDERER=llvmpipe (LLVM 12.0.0, 256 bits)
GL_VERSION=4.1 (Core Profile) Mesa 21.2.6
GL_SHADING_LANGUAGE_VERSION=4.50

In my hardware setup:
GL_VENDOR=NVIDIA Corporation
GL_RENDERER=NVIDIA GeForce RTX 3090/PCIe/SSE2
GL_VERSION=3.3.0 NVIDIA 535.161.07
GL_SHADING_LANGUAGE_VERSION=3.30 NVIDIA via Cg compiler

If the appropriate GPU drivers are not installed or are malfunctioning, the system may revert to using LLVMpipe for rendering.

Thanks for your reply! After I used GPUs for rendering, the results improved. The result is shown below. Thanks for providing such a great work! However, I have one question: why didn't you train and test on other more up-to-date and challenging benchmarks?

CALVIN gets popular mostly after the last year's ICLR (thanks to RoboFlamingo and GR-1, I think), and it's still up-to-date in some way as you can see many papers summited to this year's ICLR using it.
It continues to present challenges as well; as a benchmark for long-horizon manipulation tasks, the success rate for completing a sequence of five consecutive sub-tasks remains low.
The 'long-horizon' characteristic is also a key reason for our selection of CALVIN, as it aligns with the what we aim to develop in CLOVER.

CALVIN gets popular mostly after the last year's ICLR (thanks to RoboFlamingo and GR-1, I think), and it's still up-to-date in some way as you can see many papers summited to this year's ICLR using it. It continues to present challenges as well; as a benchmark for long-horizon manipulation tasks, the success rate for completing a sequence of five consecutive sub-tasks remains low. The 'long-horizon' characteristic is also a key reason for our selection of CALVIN, as it aligns with the what we aim to develop in CLOVER.

Thanks for your reply! Thanks for providing such a great work!


CallKit QuickStart sample app improvements

This PR has following changes -

StartCall - Avoid updating call.
Report Connected Call state to CallKit for outgoing call.
Disconnect from the Room on providerDidReset callback.
Following speakerbox's guidelines to configure audio session while simulating incoming call

Thanks @bchen-twilio


Migrate to native classes + decorators

This moves the addon code to native classes and add ember-decorators using state 1 spec.
This drops support for Ember v2.18. Minimum tested version is Ember v3.4 using ember-native-class-polyfill.

@bgentry I believe this is ready for a review. Changes seem to work as expected, but it does removes support for Ember 2.18 as tests kept failing, making the minimum Ember tested version 3.4.
@buschtoens Mind taking a look in this PR as well? Maybe @pzuraq could also have his eyes on this?

I actually refactored how we do the setup of clientOptions, link and cache, removing the need for computed entirely. This does make things simper IMO and removes the need for requiring ember-decorators in runtime. I kept @ember-decorators/babel-transforms as it enables using native classes, class fields and whatnot. Will research if we really need to keep it long term.

@bgentry I believe this PR can move forward. Mind doing a review?

@bgentry I have refactor this a little bit to remove the breaking change, instead I have deprecated the old way of overwriting apollo options.

Released in v2.0.0-beta.4


git remote add origin https://github.com/Emanisay/https-github.com-emanisay27-create-react-app-b8fc7a0c.git git branch -M main git push -u origin main

          Ems

Originally posted by @emanisay27 in https://github.com/facebook/create-react-app/pull/13063#pullrequestreview-1347462504

De

Ems

Hi

G

G

G


[SPARK-7648] Add weights and intercept to GLM wrappers in spark.ml

Otherwise, users can only use transform on the models. @brkyvz

Merged build triggered.

Merged build started.

Test build #32732 has started for   PR 6156 at commit f709964.

LGTM

Test build #32732 timed out     for PR 6156 at commit f709964     after a configured wait of 150m.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32732/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #32745 has started for   PR 6156 at commit 1ae3d2d.

Test build #32745 has finished for   PR 6156 at commit 1ae3d2d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32745/
Test PASSed.

Merged build finished. Test PASSed.

Merged into master and branch-1.4.


Can't import old PDBs (VS 6 and below)

Describe the bug
Old PDBs cannot be imported, i.e. it gives the following error:
Incomplete PDB information (GUID/Signature and/or age) associated with this program. etc.
The problem may be that Ghidra parser/some related component does not consider the old signature and age fields (and possibly other stuff) from old versions of Visual Studio. MS apparently extended the format with VS 7.
This issue was also present in older versions of Ghidra.
See here https://technet.microsoft.com/zh-cn/ms680193(v=vs.90) , here https://github.com/microsoft/microsoft-pdb/blob/082c5290e5aff028ae84e43affa8be717aa7af73/PDB/dbi/pdb.cpp#L772 and here https://github.com/NationalSecurityAgency/ghidra/blob/fe11274fe7aff7c434921c3d7a5a88c51c1db3a3/Ghidra/Features/PDB/src/main/java/ghidra/app/util/bin/format/pdb/PdbParser.java
Here what is shown in Help->About...

Environment (please complete the following information):

OS: Win 10 x64 latest update
Java Version: 11
Ghidra Version: 9.1 beta

Looks like it should be pretty easy to implement, the pdb.exe extractor already handles these old files and exports all the infos in XML correctly (presumably). So it's just about adding it to Ghidra importer and make it use the PDB file anyway

After experimenting a bit, I devised a dumb hack to make it work. Just ignores the null age and signature. See my PR #1304
Works perfectly

@ryanmkurtz Sorry for the ping, but you seem to be the project leader.
Well, the issue with importing VS6 PDB files was fully fixed back in 11.1 version (issue #6464 referring to this), and additionally some support for specific old PDBs was recently fixed in #7100 issue (although this fix will only be added in the next release version - 11.3, but I have already managed to test the build from the latest commit and can confirm that fix helped).
So I guess this issue can also be closed so to have less reports in the bug tracker that have already been resolved.


Development: Fix executing server tests with MySQL and Postgres

Checklist
General

[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context
#8282 removed the database-platform property, as the dialect can now be inferred from the JDBC URL. However, this is not the case in the server tests, as we don't provide a JDBC URL there as we don't use an external database. Hence, JDBC can't infer the correct dialect and generates wrong SQL queries.
Description
re-added these configuration attributes.
Steps for Testing
see that MySQL and Postgres tests run again.

Good catch, thank you!


Data: Error when trying to commit

Files for one table look ok but "unpack not ok" error when trying to commit to repo
/data//mbtools/cmds.config.json
{
  "name": "/MBTOOLS/CMDS",
  "type": "TABU",
  "where": []
}

/data//mbtools/cmds.tabu.json
[
  {
    "command": "CALC",
    "shortcut": "=",
    "clsname": "/MBTOOLS/CL_COMMAND__CALC",
    "description": "Calculate"
  },
  {
    "...": "..."
  }
]

ZCL_ABAPGIT_GIT_TRANSPORT->RECEIVE_PACK
lv_line = `66e5c990075279e729a73f48a0d0be119b90ec1b ccb967b390c61924a761c676aec68f522b1d8614 refs/heads/main# report-status#`

lv_string = '0029#0024unpack index-pack abnormal exit#001eng refs/heads/main failed#00000000'

I guess its due to the namespaces which are not escaped yet, /data//mbtools/cmds.tabu.json

Oh right. Too many / in the file names. Will fix it and work on deserialize since it would come in handy for my repos now.


doubts

I have some doubt on a lot of words:
But defenetly berlusconi, torino, ministro, srl, marche, governo are not stopwords.
I also see some numbers I am not sure they should be here.
I see also some encoding issues on the txt file:
puã² -> può
sarã -> sarà
perchã¨ -> perché

I have some doubt on a lot of words:
But defenetly berlusconi, torino, ministro, srl, marche, governo are not stopwords.
I also see some numbers I am not sure they should be here.
I see also some encoding issues on the txt file:
puã² -> può
sarã -> sarà
perchã¨ -> perché

I totally agree, those words should be removed. Maybe we can send a pull request?

sorry for the very late response. thank you for your contribution! @deneb2 @giovannikraushaar


Polling + request response

There are some TODOS in places of the code where I am still unsure how to do certain things.  You guys can respond to those as well.
The request_response_provider may not be fully correct.
I have copied over the mqtt_transport with only some parameter changes and have renamed it
as state_based_mqtt_provider.

I'm not so sure about some of the architectural choices here, although I know a lot of it is probably due to blocking on the shared transport issue.
I would definitely like to see what this will look like after the transport design changes come through before I'd be comfortable putting this in master, now that we're releasing packages.

Why does azure-iot-device now have an __init__.py file? It isn't a package, it shouldn't have one.

Um, because you added it. :) I agree that it shouldn't have one -- it was causing iothub modules to be imported when I was testing common.  They weren't called, but I didn't even want them imported.

In reply to: 491020405 [](ancestors = 491020405)

Did I? That was definitely not supposed to have happened. We should get rid of this for sure.

In reply to: 491051759 [](ancestors = 491051759,491020405)


Adapt ps_bestsellers for multiples versions of PrestaShop

Questions
Answers

Description?
Adapt ps_bestsellers for multiples versions of PrestaShop

Type?
refacto

BC breaks?
no

Deprecations?
no

Fixed ticket?
Relative to PrestaShop/Prestashop#28988

How to test?
Try this module in version < <IP_ADDRESS> and in recent version (8.0.0)

Thank you @Progi1984 & @florine2623! 🥳


Switch from Zip to ZIPFoundation

Submitting this to get your input on switching from Zip to ZIPFoundation. This solves a lot of the dependency problems myself and others have encountered due to the minizip dependency in Zip. Problems such as "module minizip not found" or "duplicate minizip definitions".
The only downside to switching as far as I can tell is that ZIPFoundation raises the minimum iOS version from 8.0 to 9.0 (some compression APIs it uses were added in 9.0).

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks! iOS 9 is still good, as that's the maximum for iPhones 4S, as far as I remember. We'll have a look and come back to you. Please, ping us when it takes too long.

Thanks for considering this change. Just for completeness here are some of the minizip issues I referenced in case others have run into these issues:

https://github.com/NordicSemiconductor/IOS-Pods-DFU-Library/issues/185
https://github.com/NordicSemiconductor/IOS-Pods-DFU-Library/issues/190

@marcosiino You are welcome to try a branch I have that uses SSZipArchive instead of ZipFoundation.  It is located here: https://github.com/alanfischer/IOS-Pods-DFU-Library/tree/ssziparchive
Either way, I would approve of Zip being replaced by something else in this project.  It is a large source of headache.

Hi @alanfischer @marcosiino @jlubawy,
I'm about to do an update to the DFU lib. Do you think this PR should be in the new release?

Ok, time up ;)
We had a chat here and decided to merge the PR. We can always revert it.


RemoteEndpoint unavailable, current state [CLOSING], expecting [OPEN or CONNECTED]

Rancher Versions:
Server: 1.5.1
healthcheck: 0.2.3
ipsec: rancher/net:holder
network-services: metadata:v0.8.11/network-manager:v0.5.3
scheduler: 0.7.5
Docker Version: 1.12.6
OS and where are the hosts located? (cloud, bare metal, etc): CoreOS AWS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) HA setup behind ELB and connected to RDS.
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Cattle.
Steps to Reproduce:  No idea.  This is the only time I have ever seen this happen, just trying to get some ideas of what might have happened.
Results:
Last night I lost 3 of my rancher agents spontaneously. I SSH'd to the server, and everything looked fine, as far as I could tell. All of the containers were still running, just weren't connected to the cluster any longer. I cleared the rancher-agent and the other containers on the host, and re-ran the rancher bootstrap script and the node rejoined the cluster.
I can't figure out why the agents randomly disconnected though, which is concerning. I found the following in the logs in the rancher-server container.
Any ideas why there would be websocket issues? The IP address for TLS handshake error is 100% an ELB address.  I have double checked that I have proxy protocol turned on.
time="2017-03-28T04:32:33Z" level=info msg="Handling backend connection request."
time="2017-03-28T04:32:33Z" level=info msg="Registering backend for host 5ca832d9-e949-4e41-7b70-5b653b41ba1f with session ID e07437cc-0b52-49d9-b34b-ce8bc8d245a6."
2017/03/28 05:03:26 http: TLS handshake error from <IP_ADDRESS>:63316: EOF
2017/03/28 05:03:29 http: TLS handshake error from <IP_ADDRESS>:63324: EOF
time="2017-03-28T05:38:31Z" level=info msg="Shutting down backend d11849cb-d511-4055-4001-30001f8e149d. Connection closed because: websocket: close 1006 unexpected EOF."
time="2017-03-28T05:38:31Z" level=info msg="Removed backend. Key: d11849cb-d511-4055-4001-30001f8e149d. Session ID f9302ce6-8634-427f-82e8-d674978b09cb ."
time="2017-03-28T05:38:44Z" level=info msg="Handling backend connection request."
time="2017-03-28T05:38:44Z" level=info msg="Registering backend for host d11849cb-d511-4055-4001-30001f8e149d with session ID 29397ff5-664a-40ce-a3b7-77d48aedc376."
2017-03-28 05:45:31,659 WARN  [:] [] [] [] [p859417998-4093] [i.c.p.a.p.s.j.WebSocketMessageWriter] Unhandled Error (closing connection) org.eclipse.jetty.websocket.api.WebSocketException: RemoteEndpoint unavailable, current state [CLOSING], expecting [OPEN or CONNECTED]
at org.eclipse.jetty.websocket.common.WebSocketSession.getRemote(WebSocketSession.java:252) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:141) ~[websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:628) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:476) [websocket-common-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) [jetty-io-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_72]

There are more errors in the logs but they all started happening after this first error.

I'm continuing to see other odd messages in the rancher server logs.  The following messages repeat themselves every 30 minutes or so.
2017-03-28 08:10:50,736 ERROR [725bf9ec-02c9-4f03-b4e5-fd96b9491e55:167179] [instance:2984] [instance.start->(InstanceStart)] [] [cutorService-13] [i.c.p.process.instance.InstanceStart] Failed [2/5] to Starting for instance [2984]
2017-03-28 08:10:50,750 ERROR [e671ad9c-9be3-472e-ba92-320a2e0208f3:167184] [instance:2990->instanceHostMap:2348] [instance.start->(InstanceStart)->instancehostmap.activate] [] [ecutorService-6] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=956]: Timeout getting IP address
2017-03-28 08:10:50,750 ERROR [e671ad9c-9be3-472e-ba92-320a2e0208f3:167184] [instance:2990] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed [2/5] to Starting for instance [2990]
2017-03-28 08:10:50,869 ERROR [725bf9ec-02c9-4f03-b4e5-fd96b9491e55:167179] [instance:2984->instanceHostMap:2340] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-13] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=956]: Timeout getting IP address
2017-03-28 08:10:50,869 ERROR [725bf9ec-02c9-4f03-b4e5-fd96b9491e55:167179] [instance:2984] [instance.start->(InstanceStart)] [] [cutorService-13] [i.c.p.process.instance.InstanceStart] Failed [3/5] to Starting for instance [2984]
2017-03-28 08:10:50,947 ERROR [e671ad9c-9be3-472e-ba92-320a2e0208f3:167184] [instance:2990->instanceHostMap:2348] [instance.start->(InstanceStart)->instancehostmap.activate] [] [ecutorService-6] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=956]: Timeout getting IP address
2017-03-28 08:10:50,947 ERROR [e671ad9c-9be3-472e-ba92-320a2e0208f3:167184] [instance:2990] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed [3/5] to Starting for instance [2990]
2017-03-28 08:10:56,006 ERROR [3ad35107-8bd4-4981-914d-3501f9c20821:168841] [instance:3016->instanceHostMap:2369] [instance.start->(InstanceStart)->instancehostmap.activate] [] [ecutorService-9] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=956]: Timeout getting IP address
2017-03-28 08:10:56,007 ERROR [3ad35107-8bd4-4981-914d-3501f9c20821:168841] [instance:3016] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed [1/5] to Starting for instance [3016]
2017-03-28 08:10:56,089 ERROR [d85fd7ce-17c9-47fe-91a5-6ef93ff1b452:168835] [instance:3015->instanceHostMap:2370] [instance.start->(InstanceStart)->instancehostmap.activate] [] [utorService-888] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=956]: Timeout getting IP address

Restarting the rancher-server container seems to clear things up in the logs temporarily.  I've beefed up my monitoring and alerting to catch this faster next time.
I'd still like to know if there is a proper "fix" for this behavior.  Bump the JVM memory on the server or maybe an extra flag to the docker run command to restart it automatically if it consumes too many resources?

We're seeing something similar, but it appears to be CPU related instead of memory due to possible websocket problems, https://github.com/rancher/rancher/issues/8326.
Having either more resources or a way to auto-recover would be helpful.

Fixed via #8326


where is this file? ingest.py

Looks like a typo in the instructions to me. scripts/injest_rst.py appears to be the correct file.

Thanks you, fixed!


Use the new setTimer function in LocalRest

These need to be replaced to use setTimer once TaskManager is fixed to use it.
https://github.com/bpfkorea/agora/blob/bebe6555052b830bff1040847edd035046d24cd4/source/agora/consensus/protocol/Nominator.d#L507-L509
https://github.com/bpfkorea/agora/blob/bebe6555052b830bff1040847edd035046d24cd4/source/agora/network/NetworkManager.d#L203-L210
https://github.com/bpfkorea/agora/blob/bebe6555052b830bff1040847edd035046d24cd4/source/agora/network/NetworkManager.d#L235-L246
Originally posted by @AndrejMitrovic in https://github.com/bpfkorea/agora/pull/871#issuecomment-633762479

setTimer available as of #860

https://github.com/bpfkorea/agora/blob/bebe6555052b830bff1040847edd035046d24cd4/source/agora/network/NetworkManager.d#L203-L210
https://github.com/bpfkorea/agora/blob/bebe6555052b830bff1040847edd035046d24cd4/source/agora/network/NetworkManager.d#L235-L246
Here's the question.
If it look at the existing code, wait after the function is done.
For the new function localrest, first wait and then call delegate.
Would it be okay to do the two things mentioned here after wait and call?
This creates a subtle time difference at the beginning.

Please be aware you're pointing to outdated commits.
Also yes, there's a difference. We probably don't want to delay every request. It would be nice to be able to do start + wait rather than just wait + start.

The setTimer() also requires the stop function.

Applied code line
2. https://github.com/bpfkorea/agora/blob/07dfc407a31828ee3d0596da29696235c5de5c81/source/agora/node/FullNode.d#L178
3.
https://github.com/bpfkorea/agora/blob/4c6b990955645003f6736d231fc781f366b7588b/source/agora/network/NetworkManager.d#L532


Redesign tests based on QueueTestHead and onFinalizeWeak

Http1ClientStageSuite and ClientTimeoutSuite."Idle timeout on slow POST body" use a combo of QueueTestHead to mock the network side of the connection and request.body.onFinalizeWeak to trigger some action in QueueTestHead.  In these tests onFinalizeWeak is meant to detect when the request has been sent. The problem is that finalisation of the request body stream, does not guarantee the request has been sent. This can be clearly seen in the code of org.http4s.blazecore.util.EntityBodyWriter#writeEntityBody where writeEnd is executed after drain:
  def writeEntityBody(p: EntityBody[F]): F[Boolean] = {
    val writeBody: F[Unit] = p.through(writePipe).compile.drain
    val writeBodyEnd: F[Boolean] = fromFutureNoShift(F.delay(writeEnd(Chunk.empty)))
    writeBody *> writeBodyEnd
  }

This issue leads to flaky tests like this one:
https://github.com/http4s/http4s/runs/4498891671?check_suite_focus=true#step:13:5129

 ==> X org.http4s.blaze.client.Http1ClientStageSuite.Submit a request line with a query  0.017s munit.ComparisonFailException: /home/runner/work/http4s/http4s/blaze-client/src/test/scala/org/http4s/blaze/client/Http1ClientStageSuite.scala:153 Obtained empty output!
152:      val statusLine = request.split("\r\n").apply(0)
153:      assertEquals(statusLine, "GET " + uri + " HTTP/1.1")
154:      assertEquals(response, "done")
    at munit.Assertions.failComparison(Assertions.scala:297)
    at munit.Assertions.failComparison$(Assertions.scala:287)
    at munit.FunSuite.failComparison(FunSuite.scala:11)
    at munit.Assertions$$anon$1.handle(Assertions.scala:31)
    at munit.internal.difflib.Diffs$.assertNoDiff(Diffs.scala:42)
    at munit.Assertions.$anonfun$assertEquals$1(Assertions.scala:141)
    at get @ fs2.Stream$.$anonfun$interruptWhen$3(Stream.scala:1566)
    at map @ org.http4s.blaze.client.Http1ClientStageSuite.$anonfun$getSubmission$14(Http1ClientStageSuite.scala:124)
    at apply @ org.http4s.blaze.client.Http1ClientStageSuite.$anonfun$getSubmission$12(Http1ClientStageSuite.scala:123)
    at fromFuture @ munit.CatsEffectFunFixtures$ResourceFixture$.$anonfun$apply$8(CatsEffectFunFixtures.scala:59)
    at guarantee @ fs2.internal.CompileScope.$anonfun$interruptWhen$1(CompileScope.scala:384)
    at flatMap @ org.http4s.blaze.client.Http1ClientStageSuite.$anonfun$getSubmission$12(Http1ClientStageSuite.scala:123)
    at apply @ org.http4s.blaze.client.Http1ClientStageSuite.$anonfun$getSubmission$10(Http1ClientStageSuite.scala:122)
    at flatMap @ org.http4s.blaze.client.Http1ClientStageSuite.$anonfun$getSubmission$10(Http1ClientStageSuite.scala:122)
    at void @ org.http4s.blaze.client.PoolManager.$anonfun$createConnection$2(PoolManager.scala:122)

I think this issue may be the root cause of why we have marked so many tests in Http1ClientStageSuite as flaky.

Shouldn't this be moved to http4s/blaze ?


Add vignette for 'visualising-xmaps'

Eventually will showcase visualisation designs and helpers in #56
For now just illustrate possible vis types using anzsco22 to isco8:

[ ] bigraph
[ ] matrix
[ ] fancy print (with arrows between)

Example crosswalks:

[ ] ANZSCO22 to ISCO8: excel download

Include any useful functions/abstractions from viz-panel-maps and the create-conformr docs; and sample code in #56.
Does it make sense to include this vignette in the package? Or maybe just as an article on the pkgdown?

Why is the vignette build not using xmap::print.xmap_df()???

Do I need to do #96

closed with 78403c3f3e60e5d44e7aaf192438207c64ef2158


Cut the v-prepend from the Git version

High Level Overview of Change
Our git tags are in the form vX.Y.Z, but our package.json version is in the form X.Y.Z, thus, to compare them, we need to cut the v-prefix from our git tag version.
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Release

Test Plan
I can now run npm run compareVersions and it works correctly.

@dino-rodriguez , not sure where this falls in with your other version/release PRs.

https://github.com/payid-org/payid/pull/571 should fix this once it's merged, so I think we can close this.


React memo bug

Component documentation does not generate when a functional component is wrapped within React.memo()

I think this might actually be a bug related to react-docgen https://github.com/reactjs/react-docgen/issues/342


Improve onEnd details

Operator onEnd can be improved with extra details about duration, by providing min/max duration, along with indexes of where those were reached.
This is to help locate deviations in iterable performance.
For example, have duration inside IIterationSummary of the following type:
export interface IDuration {
    average: number; // averge duration
    max: {delay, index, value} // delay = waiting time, index when the value was reached, the value
    min: {delay, index, value}; // same as above
    total: number; // total duration
}

This would be a breaking change, because duration property changes.

This change now has been merged into master.

Updated onEnd released in v2.0.0-beta.7


Remove compiler warning when U_CX_PORT_PRINTF is defined as nothing.

Hi Andreas: just a little tidy up.  There may be other ways of doing this, feel free to suggest.
When using uxclient with ubxlib we define U_CX_AT_CONFIG_FILE in order to use our own configuration file.  When ubxlib is configured to have no logging at compile-time, so U_CX_PORT_PRINTF is defined to be empty, we get a compiler warning from uCxLogPrintTime() because the stack variables in that function are no longer used.  This PR makes the whole of the body of uCxLogPrintTime() conditional on U_CX_PORT_PRINTF being defined as something useful in order to remove the warning.

Thanks for fixing Rob!
Don't mind the failing checks - it's just the unit test parser that fails to access the results from a forked PR (will need to find a workaround for it).
Have a nice Sunday!