Shadows flicker when overlapping

Steps to Reproduce

Run flutter create bug.
Create a Scaffold()
Add a CustomScrollView() to the body
Add a Container() with a BoxShadow()
Add a bottomNavigationbar to the Scaffold()
Set it to the following:

Container(
        decoration: BoxDecoration(
          borderRadius: BorderRadius.circular(_borderRadius),
          boxShadow: [
            BoxShadow(
              color: Theme.of(context).shadowColor.withOpacity(0.4),
              blurRadius: 22.0,
            ),
          ],
        ),
        child: ClipRRect(
          borderRadius: BorderRadius.only(
            topLeft: Radius.circular(25),
            topRight: Radius.circular(25),
          ),
          child: BottomNavigationBar(
            unselectedItemColor: Theme.of(context).iconTheme.color,
            selectedItemColor: Theme.of(context).primaryColor,
            showSelectedLabels: false,
            showUnselectedLabels: false,
            selectedFontSize: 0,
            unselectedFontSize: 0,
            enableFeedback: true,
            type: BottomNavigationBarType.fixed,
            items: [
              BottomNavigationBarItem(
                icon: Icon(Icons.settings_outlined, size: 28),
                activeIcon: Icon(Icons.settings_rounded, size: 28),
                label: 'icon',
              ),
              BottomNavigationBarItem(
                icon: Icon(Icons.settings_outlined, size: 28),
                activeIcon: Icon(Icons.settings_rounded, size: 28),
                label: 'icon',
              ),
            ],
            currentIndex: 0,
            onTap: (index) {},
          ),
        ),
      ),

Scroll to see the normal shadow behaviour
Then scroll to make them overlap

I'll work on getting a reproducible sample when I get the chance.
Expected results:
Shadows should not flicker when they overlap
Actual results:
They flicker when they overlap.
Here is a screenshot of what my app looks like (WIP):

Here is a recording of the flickering:
https://user-images.githubusercontent.com/63734405/118947062-06fe5280-b968-11eb-8be0-dfc2d65667b3.mp4
The shadow behaves normally when it is above the container but starts to flicker when the shadows overlap.

Logs

flutter analyze
info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/main.dart:31:15 • deprecated_member_use
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/main.dart:154:15 • deprecated_member_use
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or
          more of its instance fields aren't final: ResetPassword.email •
          lib/screens/authentication/log_in.dart:460:7 • must_be_immutable
   info • The declaration '_getColor' isn't referenced • lib/screens/authentication/log_in.dart:485:9 •
          unused_element
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/log_in.dart:556:57 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/log_in.dart:561:55 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/log_in.dart:817:46 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/log_in.dart:823:44 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/log_in.dart:839:46 • deprecated_member_use
   info • Unused import: 'package:releaf/screens/authentication/veryify.dart' •
          lib/screens/authentication/register.dart:4:8 • unused_import
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/register.dart:151:46 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/register.dart:157:44 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/register.dart:173:46 • deprecated_member_use
   info • Unused import: 'package:releaf/shared/const/app_theme.dart' •
          lib/screens/authentication/veryify.dart:4:8 • unused_import
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/veryify.dart:103:52 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/veryify.dart:112:54 • deprecated_member_use
   info • The value of the local variable '_ratio' isn't used •
          lib/screens/authentication/welcome.dart:18:11 • unused_local_variable
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/welcome.dart:81:58 • deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/authentication/welcome.dart:123:58 • deprecated_member_use
   info • Unused import: 'package:releaf/screens/home/navigation_bar.dart' •
          lib/screens/home/dashboard.dart:5:8 • unused_import
   info • Unused import: 'package:releaf/screens/home/settings.dart' •
          lib/screens/home/dashboard.dart:6:8 • unused_import
   info • Unused import: 'package:releaf/services/auth.dart' • lib/screens/home/dashboard.dart:8:8 •
          unused_import
   info • Unused import: 'package:releaf/services/database.dart' • lib/screens/home/dashboard.dart:9:8 •
          unused_import
   info • The value of the local variable 'theme' isn't used • lib/screens/home/dashboard.dart:35:11 •
          unused_local_variable
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/screens/home/dashboard.dart:55:42 •
          deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/home/dashboard.dart:66:40 • deprecated_member_use
   info • Unused import: 'package:firebase_storage/firebase_storage.dart' •
          lib/screens/home/home.dart:2:8 • unused_import
   info • Unused import: 'package:provider/provider.dart' • lib/screens/home/home.dart:4:8 •
          unused_import
   info • Unused import: 'package:releaf/shared/const/app_theme.dart' • lib/screens/home/home.dart:5:8 •
          unused_import
   info • Unused import: 'package:releaf/services/auth.dart' • lib/screens/home/home.dart:6:8 •
          unused_import
   info • Unused import: 'package:releaf/services/database.dart' • lib/screens/home/home.dart:7:8 •
          unused_import
   info • Unused import: 'package:provider/provider.dart' • lib/screens/home/journal.dart:5:8 •
          unused_import
   info • Unused import: 'package:releaf/screens/home/dashboard.dart' •
          lib/screens/home/journal.dart:6:8 • unused_import
   info • Unused import: 'package:releaf/screens/home/navigation_bar.dart' •
          lib/screens/home/journal.dart:7:8 • unused_import
   info • Unused import: 'package:releaf/shared/const/app_theme.dart' •
          lib/screens/home/journal.dart:8:8 • unused_import
   info • Unused import: 'package:releaf/services/auth.dart' • lib/screens/home/journal.dart:9:8 •
          unused_import
   info • Unused import: 'package:releaf/services/database.dart' • lib/screens/home/journal.dart:10:8 •
          unused_import
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/screens/home/journal.dart:53:38 •
          deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/home/journal.dart:135:52 • deprecated_member_use
   info • Unused import: 'package:releaf/screens/home/dashboard.dart' •
          lib/screens/home/meditation.dart:4:8 • unused_import
   info • Unused import: 'package:releaf/screens/home/navigation_bar.dart' •
          lib/screens/home/meditation.dart:5:8 • unused_import
   info • Unused import: 'package:releaf/services/auth.dart' • lib/screens/home/meditation.dart:7:8 •
          unused_import
   info • Unused import: 'package:releaf/services/database.dart' • lib/screens/home/meditation.dart:8:8
          • unused_import
   info • The value of the local variable 'theme' isn't used • lib/screens/home/meditation.dart:34:11 •
          unused_local_variable
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/screens/home/meditation.dart:68:42 •
          deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/home/meditation.dart:79:40 • deprecated_member_use
   info • Unused import: 'dart:ui' • lib/screens/home/setting_popup.dart:1:8 • unused_import
   info • Unused import: 'package:email_validator/email_validator.dart' •
          lib/screens/home/setting_popup.dart:4:8 • unused_import
   info • Unused import: 'package:releaf/services/auth.dart' • lib/screens/home/setting_popup.dart:5:8 •
          unused_import
   info • Unused import: 'package:releaf/shared/assets/custom_form_field.dart' •
          lib/screens/home/setting_popup.dart:7:8 • unused_import
   info • The value of the local variable '_theme' isn't used •
          lib/screens/home/setting_popup.dart:16:11 • unused_local_variable
   info • Unused import: 'package:releaf/screens/home/navigation_bar.dart' •
          lib/screens/home/settings.dart:7:8 • unused_import
   info • Unused import: '../../wrapper.dart' • lib/screens/home/settings.dart:15:8 • unused_import
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/screens/home/settings.dart:273:42 •
          deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/home/settings.dart:284:40 • deprecated_member_use
   info • The value of the local variable '_theme' isn't used • lib/screens/home/settings.dart:452:11 •
          unused_local_variable
   info • Unused import: 'package:releaf/screens/home/dashboard.dart' • lib/screens/home/tasks.dart:5:8
          • unused_import
   info • Unused import: 'package:releaf/screens/home/navigation_bar.dart' •
          lib/screens/home/tasks.dart:6:8 • unused_import
   info • Unused import: 'package:releaf/services/auth.dart' • lib/screens/home/tasks.dart:8:8 •
          unused_import
   info • Unused import: 'package:releaf/services/database.dart' • lib/screens/home/tasks.dart:9:8 •
          unused_import
   info • The value of the local variable 'theme' isn't used • lib/screens/home/tasks.dart:38:11 •
          unused_local_variable
   info • The value of the local variable 'width' isn't used • lib/screens/home/tasks.dart:39:11 •
          unused_local_variable
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/screens/home/tasks.dart:68:40 •
          deprecated_member_use
   info • 'accentIconTheme' is deprecated and shouldn't be used. No longer used by the framework, please
          remove any reference to it. This feature was deprecated after v2.3.0-0.1.pre. •
          lib/screens/home/tasks.dart:79:38 • deprecated_member_use
   info • Unused import: 'package:releaf/services/database.dart' • lib/services/auth.dart:4:8 •
          unused_import
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/shared/assets/themed_button.dart:94:55 •
          deprecated_member_use
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/shared/assets/themed_button.dart:96:27 •
          deprecated_member_use
   info • 'accentColor' is deprecated and shouldn't be used. Use colorScheme.secondary instead. This
          feature was deprecated after v2.3.0-0.1.pre. • lib/shared/assets/themed_button.dart:240:55 •
          deprecated_member_use

68 issues found. (ran in 7.3s)

flutter doctor -v
[✓] Flutter (Channel master, 2.3.0-13.0.pre.59, on macOS 11.3.1 20E241 darwin-x64, locale en-AU)
    • Flutter version 2.3.0-13.0.pre.59 at /Users/hadymashhour/Developer/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1e35f4c0c6 (2 hours ago), 2021-05-20 03:14:01 -0400
    • Engine revision 67c537d41b
    • Dart version 2.14.0 (build 2.14.0-129.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/hadymashhour/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

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

[✓] Android Studio (version 4.1)
    • 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 1.8.0_242-release-1644-b3-6915495)

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

[✓] Connected device (2 available)
    • iPhone 12 Pro Max (mobile) • BD55A391-EEF1-45D8-831D-3FC41EF96918 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome
      90.0.4430.212

• No issues found!

@darshankawar
I put the container inside of SliverToBoxAdapter(),
So something that would look like this:
    return Scaffold(
      body: CustomScrollView(
        slivers: [
          SliverToBoxAdapter(
            child: Container(
              decoration: BoxDecoration(
                color: Theme.of(context).backgroundColor,
                borderRadius: BorderRadius.circular(20),
                boxShadow: [
                  BoxShadow(
                    color: Theme.of(context).shadowColor.withOpacity(0.42),
                    blurRadius: 20,
                    spreadRadius: 2,
                  ),
                ],
              ),
            ),
          ),
          SliverToBoxAdapter(
            child: Container(
              decoration: BoxDecoration(
                color: Theme.of(context).backgroundColor,
                borderRadius: BorderRadius.circular(20),
                boxShadow: [
                  BoxShadow(
                    color: Theme.of(context).shadowColor.withOpacity(0.42),
                    blurRadius: 20,
                    spreadRadius: 2,
                  ),
                ],
              ),
            ),
          ),
        ],
      ),
    );

Hope this makes things clearer, I should have said that it's inside of a SliverToBoxAdapter(). Please let me know if you need a reproducible sample and I'll make it when I can.

Thanks for the details @HadyMash. I tried below code sample and added a custom height to each container, but was unable to replicate the flicker, maybe still missing something to properly notice it ?

 code sample

@override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: CustomScrollView(
          slivers: [
            SliverToBoxAdapter(
              child: Container(
                height: 200,
                decoration: BoxDecoration(
                  color: Theme.of(context).backgroundColor,
                  borderRadius: BorderRadius.circular(20),
                  boxShadow: [
                    BoxShadow(
                      color: Theme.of(context).shadowColor.withOpacity(0.42),
                      blurRadius: 20,
                      spreadRadius: 2,
                    ),
                  ],
                ),
              ),
            ),
            SliverToBoxAdapter(
              child: Container(
                height: 200,
                decoration: BoxDecoration(
                  color: Theme.of(context).backgroundColor,
                  borderRadius: BorderRadius.circular(20),
                  boxShadow: [
                    BoxShadow(
                      color: Theme.of(context).shadowColor.withOpacity(0.42),
                      blurRadius: 20,
                      spreadRadius: 2,
                    ),
                  ],
                ),
              ),
            ),
            SliverToBoxAdapter(
              child: Container(
                height: 200,
                decoration: BoxDecoration(
                  color: Theme.of(context).backgroundColor,
                  borderRadius: BorderRadius.circular(20),
                  boxShadow: [
                    BoxShadow(
                      color: Theme.of(context).shadowColor.withOpacity(0.42),
                      blurRadius: 20,
                      spreadRadius: 2,
                    ),
                  ],
                ),
              ),
            ),
            SliverToBoxAdapter(
              child: Container(
                height: 200,
                decoration: BoxDecoration(
                  color: Theme.of(context).backgroundColor,
                  borderRadius: BorderRadius.circular(20),
                  boxShadow: [
                    BoxShadow(
                      color: Theme.of(context).shadowColor.withOpacity(0.42),
                      blurRadius: 20,
                      spreadRadius: 2,
                    ),
                  ],
                ),
              ),
            ),
          ],
        ),
        bottomNavigationBar: BottomNavigationBar(
          unselectedItemColor: Theme.of(context).iconTheme.color,
          selectedItemColor: Theme.of(context).primaryColor,
          showSelectedLabels: false,
          showUnselectedLabels: false,
          selectedFontSize: 0,
          unselectedFontSize: 0,
          enableFeedback: true,
          type: BottomNavigationBarType.fixed,
          items: [
            BottomNavigationBarItem(
              icon: Icon(Icons.settings_outlined, size: 28),
              activeIcon: Icon(Icons.settings_rounded, size: 28),
              label: 'icon',
            ),
            BottomNavigationBarItem(
              icon: Icon(Icons.settings_outlined, size: 28),
              activeIcon: Icon(Icons.settings_rounded, size: 28),
              label: 'icon',
            ),
          ],
          currentIndex: 0,
          onTap: (index) {},
        ),
      ),
    );
  }

@darshankawar
I also noticed that it appears on just the page I took a screenshot of and the other pages which have a very similar setup don’t have this. I think this might be a very specific case. I’ll provide you with the actual code when I get on my computer.

@darshankawar
Sorry for the delayed response, here is my code for the page. The animation controllers and animations are used for the FAB to rotate the icon if it is being routed to from a page that doesn't already have an FAB that's visible so that it animates while moving in from the right, so when adding the widget you can just set the animate parameter to false (Journal(false)). The other animation controllers are for the expanding FAB. You might need to add the animations package but replacing the floating action button I have with a FloatingActionButton() widget is completely fine as the issue was still there when I did that.

My Code

import 'dart:math';
import 'package:animations/animations.dart';
import 'package:flutter/material.dart';

class Journal extends StatefulWidget {
  final bool animate;
  Journal(this.animate);
  @override
  _JournalState createState() => _JournalState();
}

class _JournalState extends State<Journal> with TickerProviderStateMixin {
  late final AnimationController controller;
  late final CurvedAnimation animation;

  late final AnimationController fabController;
  late final Animation fabColorAnimation;
  late final Animation<double> fabElevationTween;

  bool initialised = false;

  @override
  void initState() {
    controller =
        AnimationController(vsync: this, duration: Duration(milliseconds: 320));
    animation = CurvedAnimation(curve: Curves.easeInOut, parent: controller);

    if (widget.animate == true) {
      controller.forward();
    }

    fabController =
        AnimationController(vsync: this, duration: Duration(milliseconds: 150));

    fabElevationTween = Tween<double>(begin: 6, end: 10)
        .animate(CurvedAnimation(parent: fabController, curve: Curves.linear));

    super.initState();
  }

  @override
  void dispose() {
    controller.dispose();
    fabController.dispose();
    super.dispose();
  }

  @override
  void didChangeDependencies() {
    if (initialised == false) {
      fabColorAnimation = ColorTween(
              begin: Theme.of(context).primaryColor,
              end: Theme.of(context).accentColor)
          .animate(
              CurvedAnimation(curve: Curves.linear, parent: fabController));
      initialised = true;
    }
    super.didChangeDependencies();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: [
          SliverToBoxAdapter(child: SizedBox(height: 20)),
          SliverAppBar(
            title: Text(
              'Journal',
              style: Theme.of(context).textTheme.headline3,
            ),
            automaticallyImplyLeading: false,
          ),
          SliverToBoxAdapter(child: SizedBox(height: 20)),
          SliverToBoxAdapter(
            child: JournalEntry(
                date: 'Jan 18, 2021',
                entryText:
                    'Amet ea aute reprehenderit occaecat incididunt excepteur anim id reprehenderit ad voluptate.'),
          ),
          SliverToBoxAdapter(
            child: JournalEntry(
                date: 'Jan 18, 2021',
                entryText:
                    'Amet ea aute reprehenderit occaecat incididunt excepteur anim id reprehenderit ad voluptate.'),
          ),
          SliverToBoxAdapter(
            child: JournalEntry(
                date: 'Jan 18, 2021',
                entryText:
                    'Amet ea aute reprehenderit occaecat incididunt excepteur anim id reprehenderit ad voluptate.'),
          ),
          SliverToBoxAdapter(
            child: JournalEntry(
                date: 'Jan 18, 2021',
                entryText:
                    'Amet ea aute reprehenderit occaecat incididunt excepteur anim id reprehenderit ad voluptate.'),
          ),
        ],
      ),
      floatingActionButton: Hero(
        tag: 'floatingActionButton',
        child: GestureDetector(
          onTapDown: (_) => fabController.forward(),
          onTapUp: (_) => fabController.reverse(),
          onTapCancel: () => fabController.reverse(),
          child: AnimatedBuilder(
            animation: fabController,
            builder: (context, child) {
              return OpenContainer(
                transitionDuration: Duration(milliseconds: 500),
                transitionType: ContainerTransitionType.fade,
                closedElevation: fabElevationTween.value,
                closedShape: const RoundedRectangleBorder(
                  borderRadius: BorderRadius.all(
                    Radius.circular(56 / 2),
                  ),
                ),
                closedColor: fabColorAnimation.value,
                closedBuilder:
                    (BuildContext context, VoidCallback openContainer) {
                  return SizedBox(
                    height: 56,
                    width: 56,
                    child: Center(
                      child: AnimatedBuilder(
                        animation: animation,
                        builder: (context, child) {
                          return Transform.rotate(
                            angle: (pi * 2) - ((pi * animation.value) / 2),
                            child: child,
                          );
                        },
                        child: Icon(
                          Icons.add_rounded,
                          color: Theme.of(context).accentIconTheme.color,
                          size: 40,
                        ),
                      ),
                    ),
                  );
                },
                openBuilder: (BuildContext context, VoidCallback _) {
                  return JournalEntryForm();
                },
              );
            },
          ),
        ),
      ),
      bottomNavigationBar: Container(
        decoration: BoxDecoration(
          borderRadius: BorderRadius.circular(25),
          boxShadow: [
            BoxShadow(
              color: Theme.of(context).shadowColor.withOpacity(0.4),
              blurRadius: 22.0,
            ),
          ],
        ),
        child: ClipRRect(
          borderRadius: BorderRadius.only(
            topLeft: Radius.circular(25),
            topRight: Radius.circular(25),
          ),
          child: BottomNavigationBar(
            unselectedItemColor: Theme.of(context).iconTheme.color,
            selectedItemColor: Theme.of(context).primaryColor,
            showSelectedLabels: false,
            showUnselectedLabels: false,
            selectedFontSize: 0,
            unselectedFontSize: 0,
            enableFeedback: true,
            type: BottomNavigationBarType.fixed,
            items: [
              BottomNavigationBarItem(
                icon: Icon(Icons.sports_handball_outlined, size: 28),
                activeIcon: Icon(Icons.sports_handball, size: 28),
                label: 'Meditation',
              ),
              BottomNavigationBarItem(
                icon: Icon(Icons.assignment_turned_in_outlined, size: 28),
                activeIcon: Icon(Icons.assignment_turned_in, size: 28),
                label: 'Goals',
              ),
              BottomNavigationBarItem(
                icon: Icon(Icons.dashboard_outlined, size: 28),
                activeIcon: Icon(Icons.dashboard_rounded, size: 28),
                label: 'Dashboard',
              ),
              BottomNavigationBarItem(
                icon: Icon(Icons.book_outlined, size: 28),
                activeIcon: Icon(Icons.book_rounded, size: 28),
                label: 'Journal',
              ),
              BottomNavigationBarItem(
                icon: Icon(Icons.settings_outlined, size: 28),
                activeIcon: Icon(Icons.settings, size: 28),
                label: 'Settings',
              ),
            ],
            onTap: (index) {},
            currentIndex: 3,
          ),
        ),
      ),
    );
  }
}

class JournalEntry extends StatefulWidget {
  final String date;
  // final List pictures; // TODO add pictures list
  final String entryText;

  JournalEntry({required this.date, required this.entryText});

  @override
  _JournalEntryState createState() => _JournalEntryState();
}

class _JournalEntryState extends State<JournalEntry> {
  @override
  Widget build(BuildContext context) {
    return Material(
      color: Colors.white.withOpacity(0),
      child: Container(
        margin: EdgeInsets.symmetric(horizontal: 25, vertical: 15),
        padding: EdgeInsets.fromLTRB(20, 15, 20, 18),
        decoration: BoxDecoration(
          color: Theme.of(context).backgroundColor,
          borderRadius: BorderRadius.circular(20),
          boxShadow: [
            BoxShadow(
              color: Theme.of(context).shadowColor.withOpacity(0.42),
              blurRadius: 20,
              spreadRadius: 2,
            ),
          ],
        ),
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          crossAxisAlignment: CrossAxisAlignment.start,
          mainAxisSize: MainAxisSize.min,
          children: <Widget>[
            // * Heading
            Text(
              widget.date,
              style: Theme.of(context).textTheme.subtitle2,
            ),
            SizedBox(height: 10),
            Placeholder(fallbackHeight: 160),
            SizedBox(height: 10),
            Text(
              widget.entryText,
              style: Theme.of(context).textTheme.bodyText2,
            ),
          ],
        ),
      ),
    );
  }
}

class JournalEntryForm extends StatefulWidget {
  @override
  _JournalEntryFormState createState() => _JournalEntryFormState();
}

class _JournalEntryFormState extends State<JournalEntryForm> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Journal Entry Form'),
      ),
    );
  }
}

Thanks for the code sample @HadyMash. Using it, I was unable to replicate the behavior though. I passed false to Journal class and on the main screen, scrolled down and up slowly to see, but couldn't notice it.
https://user-images.githubusercontent.com/67046386/119309119-7f785280-bc8b-11eb-9214-32c3c8cbd411.mov

 flutter doctor -v
[✓] Flutter (Channel stable, 2.2.0, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.2.0 at /Users/dhs/documents/fluttersdk/flutter
    • Framework revision b22742018b (5 days ago), 2021-05-14 19:12:57 -0700
    • Engine revision a9d88a4d18
    • Dart version 2.13.0

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

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

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 14.4.1
    • macOS (desktop)           • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 90.0.4430.212

! Doctor found issues in 1 category.

@darshankawar Could it be the iOS version of the simulator? The iOS simulator I'm using is on iOS 14.5.
I'll try running the app on a real device and see if the issue still persists but that device is also on iOS 14.5.

@darshankawar I just realised that the flickering only occurs below the JournalEntry():
https://user-images.githubusercontent.com/63734405/119319458-84d59d00-bc8b-11eb-87e8-09c9f713d962.mp4
Are you able to replicate the flicker below the second container?

@darshankawar One more thing, I just ran it on my phone (iPhone 7 plus) and i noticed the same issue (iOS 14.5).
This time it was quite different to the emulator. I noticed the flickering but it got more intense as I went farther up. The bottom one had the least flickering, third a little more, the second one had a noticeable amount and the first one had the most flickering.
*Please play the video in full screen as not all the flickering is obvious when it is in the small preview window.
https://user-images.githubusercontent.com/63734405/119325202-b7829400-bc91-11eb-9627-514eb22b2176.MP4

Thanks for digging in. I was able to replicate it using the second card, wherein, scrolling it down shows the shadow flicker, as shown below:
https://user-images.githubusercontent.com/67046386/119447784-0857c280-bd4e-11eb-87a7-bac05d70f9cd.mov

 flutter doctor -v

dhs@Dhss-MacBook-Pro ~ % flutter doctor -v
[✓] Flutter (Channel master, 2.3.0-13.0.pre.144, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.3.0-13.0.pre.144 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision bfff43cf6f (2 hours ago), 2021-05-24 21:05:52 -0700
    • Engine revision b1385c0df1
    • Dart version 2.14.0 (build 2.14.0-145.0.dev)

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

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

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

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 90.0.4430.212

• No issues found!

This may be an issue where the draw order when drawing the texture with shadows for the different cards is not deterministic. Can a larger gap be added between the cards such that they don't overlap? If the flickering is still present, it means that there is an issue with rendering of the shadow itself. If it doesn't flicker, we have an issue with draw call ordering. This should help us narrow down the issue.

@chinmaygarde I tried increasing the distance and it still flickers.
https://user-images.githubusercontent.com/63734405/121071308-d2501f00-c7e0-11eb-86df-9d42918fcb4c.mp4
P.S. I manually created 4 containers when I was testing something as I have not yet implemented the actual functionality of the app. Now that i am done, I build the containers with a NestedScrollView() view that has a ListView.builder() which builds them and the problem no longer appears as far as I am aware though I haven't extensively tested it yet as I am working on other aspects of the app. I think the problem is exclusive to making 4 containers manually.

Thanks for verifying, my initial hunch about the inconsistent draw call order was incorrect.
I guess the next thing to check would be raster cache substitution. This can be checked by turning on checkerboardRasterCacheImage. If the flicker is associated with the checkerboarded pattern, then we would have isolated the buggy component.

@chinmaygarde What do I do with the checkerboardRasterCacheImage?
Do I set it to true or false and what do I do then once setting it?

Set it to true if check if you observer a checkerboarded pattern in debug runtime modes. If nothing changes, then it's not raster cache substitution either and we still need to do more digging.

@chinmaygarde
The bottom navigation bar shows a checker pattern whenever you start scrolling around the bottom navigation bar. There are no checker patterns around the actual containers themselves.
https://user-images.githubusercontent.com/63734405/121075173-eba79a00-c7e5-11eb-9771-91960c43dcc0.mp4

/cc @flar

I have similar problem, shadow also flikering at start of overlaping and what more strange white dot appear with shadow under the FloatingActionButton like below:

After removing shadow dot dissapear:

Everyting works as expected in Flutter 2.2.3 after upgrading to 2.5.0 this strange behaviour appers.

Information:
[✓] Flutter (Channel stable, 2.5.0, on Microsoft Windows [Version 10.0.19043.1202], locale pl-PL)
    • Flutter version 2.5.0 at C:\SDK\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4cc385b4b8 (8 days ago), 2021-09-07 23:01:49 -0700
    • Engine revision f0826da7ef
    • Dart version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\SDK
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.60.0)
    • VS Code at C:\Users\Pioter\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.26.0

[✓] Connected device (5 available)
    • SM G965F (mobile)            • 22c23a7c140d7ece • android-arm64  • Android 10 (API 29)
    • D2303 (mobile)               • ZH80052UJN       • android-arm    • Android 5.1.1 (API 22)
    • AOSP on IA Emulator (mobile) • emulator-5554    • android-x86    • Android 9 (API 28) (emulator)
    • Chrome (web)                 • chrome           • web-javascript • Google Chrome 93.0.4577.63
    • Edge (web)                   • edge             • web-javascript • Microsoft Edge 93.0.961.47

• No issues found!

Does this reproduce after https://github.com/flutter/engine/pull/27124 ?

@PcolBP It looks like you have a different issue than the one described here. Could you file a new issue please?

Hmm that makes sense.

I removed the engine flag that might have had some framework engineers ignoring this issue.

@HansMuller Who is the right person to take a look at this issue around scrolling?

The reason cacheExtent is not helping in this situation is that it lays out the widgets, but it doesn't actually paint them (see also https://github.com/flutter/flutter/issues/31768).
Perhaps, there could be a paintCacheExtent which

would have a default value of null
when set, should be less than cacheExtent
and by default use something about 50 pixels to draw a widget to prevent most of the situations like this

By default null is to allow non-breaking change for anyone who is already using cacheExtent, and also to not force people to change paintCacheExtent if they set cacheExtent less than defaullt value of paintCacheExtent, without actually using it.
/cc @goderbauer

The original motivation for the cache extent was accessibility on iOS: In order to scroll an offscreen item onto screen when a11y focus is moved to it, it had to already exist in the semantics tree and the semantics tree is driven by the render tree.
Later, the cache extent also proved useful for pre-loading resources before they are needed on screen.

This issue seems to have been originally motivated by the inconsistent shadow rendering that we used to have before the switch to the directional shadows implementation, but now the latest issue demonstrated by the test cases is this "scrolling overdraw" issue.
Should we:

rewrite the synopsis and description comment on this issue to match?
close this issue as fixed by the shadow PR and create a new issue for the overdraw problem?
some other fate?

@HadyMash ?

@flar @nt4f04uNd @goderbauer @zanderso  I created a new issue.


Resultset try42 [WIP]

I create a PR with this unfinished work because there are certain things we must decide..

Returning a ResultSet from InfluxDbClient.query() is great.

Enabling to get the full list of resulting series from a resultset by doing list(resultset) is also great. But we have to clearly define the format of what's returned in the list actually..

Enabling to get the full list (eventually filtered by serie name and/or tags values) of resulting points from a resultset using resultset[key] is also great. Here the Points are more well defined within influxdb.point now.

to be continued..

I'll open a new PR with all the ResultSet code.

see #154


License issue

The REVENUE line diagram is using amcharts javascript charts lib which is not free.  too bad :(

Anyway, it's linkware license which is not good enough.


ItemsRepeater page should link to layout docs as well

Is this a totally new sample, an addition to an existing sample page, or a modification of an existing sample page?

[ ] New sample
[x] Addition to existing sample
[ ] Modification to existing sample

If this is an addition/modification to an existing sample page, which one?
ItemsRepeater
Is your sample request related to a problem? Please describe it
The Documentation section should also link to StackLayout and UniformGridLayout documentation pages as well.

Thanks for finding this. Addressed in #370.


Bug in addition of fractions

Describe the bug

In explanation of addition of subtraction variables are not replaced with their values.

Screenshots

Please assign this issue to me.

Go ahead
Deadline 29 April,2021


Add option to change working directory before running git

Closing without merging; I don't think we really need this.


⚠ Bofrost.be has degraded performance

In 51bd0ec, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1104 ms

Resolved: Bofrost.be performance has improved in 00d62c6.


helm charts: SPIRE server should be able to (optionally) enable telemetry

# telemetry: If telemetry is desired use this section to configure the
# available metrics collectors.
# telemetry {
#     Prometheus {
#         # host: Prometheus server host.
#         # host = ""

#         # port: Prometheus server port.
#         port = 9988
#     }

#     DogStatsd = [
#         # List of DogStatsd addresses.
#         { address = "localhost:8125" },
#         { address = "collector.example.org:1337" },
#     ]

#     Statsd = [
#         # List of Statsd addresses.
#         { address = "localhost:1337" },
#         { address = "collector.example.org:8125" },
#     ]

#     M3 = [
#         # List of M3 configurations.
#         { address = "localhost:9000" env = "dev" },
#         { address = "collector.example.org:9000" env = "prod" },
#     ]

#     InMem {
#     }
# }

from docs:
Export Metrics for Monitoring
This configuration applies to the SPIRE Server and SPIRE Agent
To configure a SPIRE Server or Agent to output data to a metrics collector, edit the telemetry section in server.conf or agent.conf. SPIRE can export metrics to Datadog (DogStatsD format), M3, Prometheus, and StatsD.
You may configure multiple collectors at the same time. DogStatsD, M3, and StatsD support multiple declarations in the event that you want to send metrics to more than one collector.
If you want to use Amazon Cloud Watch for metrics collection, review this document on retrieving custom metrics with the CloudWatch agent and StatsD.
Below is an example of a configuration block for agent.conf or server.conf that exports telemetry to Datadog, M3, Prometheus, and StatsD, and disables the in-memory collector:


[CWS] sync seclwin package for 7.59

What does this PR do?
The pkg/seclwin is a bit late compared to pkg/secl. This PR fixes, ensuring that 7.59.x is in-sync between linux and windows.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Is it possible to get artlayes or layerset position ?

Hello
I have a Photoshop file with different artlayes.
Is it possible to get from python the position of each artlayer?
Thanks!!!

Hi，@Gaston2388
You can try
from photoshop import Session

with Session() as ps:
    for layer in ps.active_document.artLayers:
        print(layer.bounds)

Thanks @loonghao !!


support for 850 code page

I just want parseDBF to support some code pages, such as 850, which is sometimes used in some shapefiles. On server side of the master, 850 code page is supported by 'iconv-lite'. On the other hand, 'TextDecoder' running on client side, doesn't support it. Fortunately, 'iconv-lite' supports to run on the browser now by using Browserify. That's why I just delete the browser field in package.json.

this is somewhat intentional as textdecoder is included in most browsers already while iconv-lite is still pretty heavy, what exactly is in the cpg file and is there an alias that also works (e.g. latin-1 is that the same )


universal-components: The InputText can works like controlled component

LGTM! 🚀  Why do we need that now? @FilipMessa

@aalises
I need to clear contact form data after user sign out himself.


Images are no longer shown in embeds

Another example

are these imgur links?
If yes, then...
https://cdn.discordapp.com/attachments/464099470766899201/506062025055666192/IMG_20181028_120920.jpg

Imgur is having issues with displaying links on Discord. Imgur is aware of the issue and is looking into it.

https://trello.com/c/7grpgSvA

Thanks, I'll leave this open so other people can see it.

This can be closed, the issue has been resolved. Imgur links are now previewing and displaying in embeds properly.


Back action different from Pan Gesture release inside nested Navigator

Given the following:

StackNavigator

genericView
TabNavigator

genericViewWithBack1
genericViewWithBack2

When I dispatch this.props.navigation.goBack(null) from genericViewWithBack1 I navigate back to genericView with back animation but when I dispatch the same action from genericViewWithBack2 (after navigating to it via genericView -> genericViewWithBack1 -> genericViewWithBack2) i go back to genericViewWithBack1
Ideally I would be able to go back to genericView directly from both genericViewWithBack1 and genericViewWithBack2 as if the user did a left edge swipe navigate but cannot figure out how to do this.
Not sure if this is the expected behaviour, if it is, does anyone know how one would simulate the same pan gesture back action?

I think this case is an edge case for my implementation so closing for now.


Import autocomplete uses single quotes

Yes. This is by design. Single quotes for JS double quotes for HTML is what I've learnt to live with based on the teams I've worked with.

Ok, is this configurable in anyway? Most typescript I've encountered uses double quotes and as result our team has used this convention.

@pspeter3 alright the TS compiler uses double quotes : https://github.com/Microsoft/TypeScript/blob/master/src/compiler/scanner.ts plus I trust your judgement. We don't care in our team, so lets just go with double quotes. I'll push.

released v1.6.0 :heart:

Thanks!


Ideas

[ ] Allow user to give url of content (Github link)
[ ] Automatically make PRs
[ ] Add comments to the same line
[ ] Add option to parse gemspecs

+1 - to allow inclusion of gemspec.

Adding comments on the same lines is a great idea ✨


0.6.0: unannounced MSRV break

0.6.0 broke MSRV which isn't listed in changelog as breaking change. Is this intended?
I'd also like to ask if edition bump can be reverted so that Rust version 1.48.0 is supported - this is the version currently in Debian Stable.

Yep we already agreed to go back to 2018 for the next release!


[SPARK-33136][SQL] Fix mistakenly swapped parameter in V2WriteCommand.outputResolved

What changes were proposed in this pull request?
This PR proposes to fix a bug on calling DataType.equalsIgnoreCompatibleNullability with mistakenly swapped parameters in V2WriteCommand.outputResolved. The order of parameters for DataType.equalsIgnoreCompatibleNullability are from and to, which says that the right order of matching variables are inAttr and outAttr.
Why are the changes needed?
Spark throws AnalysisException due to unresolved operator in v2 write, while the operator is unresolved due to a bug that parameters to call DataType.equalsIgnoreCompatibleNullability in outputResolved have been swapped.
Does this PR introduce any user-facing change?
Yes, end users no longer suffer on unresolved operator in v2 write if they're trying to write dataframe containing non-nullable complex types against table matching complex types as nullable.
How was this patch tested?
New UT added.

Btw that was hard to debug and required me to deal with Spark test code, as we get nothing from the error message on the case when all columns are matched. (In other words, considered as unresolved due to the type incompatibility on write between same column.) We can't get the information about the reason why the operator is considered as unresolved even we turn on TRACE log.
org.apache.spark.sql.AnalysisException: unresolved operator 'AppendData RelationV2[col_b#225, col_i#226, col_l#227L, col_f#228, col_d#229, col_da#230, col_ts_tz#231, col_s#232, col_fi#233, col_bi#234, col_de_1#235, col_de_2#236, col_de_3#237, col_st#238, col_li#239, col_ma#240] table_convert_read_all_types_5, Map(path -> table_convert_read_all_types_5), true;;
'AppendData RelationV2[col_b#225, col_i#226, col_l#227L, col_f#228, col_d#229, col_da#230, col_ts_tz#231, col_s#232, col_fi#233, col_bi#234, col_de_1#235, col_de_2#236, col_de_3#237, col_st#238, col_li#239, col_ma#240] table_convert_read_all_types_5, Map(path -> table_convert_read_all_types_5), true
+- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_da#49, col_ts_tz#63, col_s#17, col_fi#18, col_bi#19, col_de_1#78, col_de_2#94, col_de_3#111, col_st#21, col_li#22, col_ma#23]
   +- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_st#21, col_li#22, col_ma#23, col_da#49, col_ts_tz#63, col_de_1#78, col_de_2#94, col_de_3#111]
      +- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_de#20, col_st#21, col_li#22, col_ma#23, col_da#49, col_ts_tz#63, col_de_1#78, col_de_2#94, cast(col_de#20 as decimal(38,10)) AS col_de_3#111]
         +- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_de#20, col_st#21, col_li#22, col_ma#23, col_da#49, col_ts_tz#63, col_de_1#78, cast(col_de#20 as decimal(11,2)) AS col_de_2#94]
            +- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_de#20, col_st#21, col_li#22, col_ma#23, col_da#49, col_ts_tz#63, cast(col_de#20 as decimal(9,0)) AS col_de_1#78]
               +- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_de#20, col_st#21, col_li#22, col_ma#23, col_da#49, now() AS col_ts_tz#63]
                  +- Project [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_de#20, col_st#21, col_li#22, col_ma#23, current_date(Some(Asia/Seoul)) AS col_da#49]
                     +- LocalRelation [col_b#12, col_i#13, col_l#14L, col_f#15, col_d#16, col_s#17, col_fi#18, col_bi#19, col_de#20, col_st#21, col_li#22, col_ma#23]

  at org.apache.spark.sql.catalyst.analysis.CheckAnalysis.failAnalysis(CheckAnalysis.scala:49)
  at org.apache.spark.sql.catalyst.analysis.CheckAnalysis.failAnalysis$(CheckAnalysis.scala:48)
  at org.apache.spark.sql.catalyst.analysis.Analyzer.failAnalysis(Analyzer.scala:130)
  at org.apache.spark.sql.catalyst.analysis.CheckAnalysis.$anonfun$checkAnalysis$43(CheckAnalysis.scala:666)
  at org.apache.spark.sql.catalyst.analysis.CheckAnalysis.$anonfun$checkAnalysis$43$adapted(CheckAnalysis.scala:664)
  at org.apache.spark.sql.catalyst.trees.TreeNode.foreachUp(TreeNode.scala:177)
  at org.apache.spark.sql.catalyst.analysis.CheckAnalysis.checkAnalysis(CheckAnalysis.scala:664)
  at org.apache.spark.sql.catalyst.analysis.CheckAnalysis.checkAnalysis$(CheckAnalysis.scala:89)
  at org.apache.spark.sql.catalyst.analysis.Analyzer.checkAnalysis(Analyzer.scala:130)
  at org.apache.spark.sql.catalyst.analysis.Analyzer.$anonfun$executeAndCheck$1(Analyzer.scala:156)
  at org.apache.spark.sql.catalyst.plans.logical.AnalysisHelper$.markInAnalyzer(AnalysisHelper.scala:201)
  at org.apache.spark.sql.catalyst.analysis.Analyzer.executeAndCheck(Analyzer.scala:153)
  at org.apache.spark.sql.execution.QueryExecution.$anonfun$analyzed$1(QueryExecution.scala:68)
  at org.apache.spark.sql.catalyst.QueryPlanningTracker.measurePhase(QueryPlanningTracker.scala:111)
  at org.apache.spark.sql.execution.QueryExecution.$anonfun$executePhase$1(QueryExecution.scala:133)
  at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:764)
  at org.apache.spark.sql.execution.QueryExecution.executePhase(QueryExecution.scala:133)
  at org.apache.spark.sql.execution.QueryExecution.analyzed$lzycompute(QueryExecution.scala:68)
  at org.apache.spark.sql.execution.QueryExecution.analyzed(QueryExecution.scala:66)
  at org.apache.spark.sql.execution.QueryExecution.assertAnalyzed(QueryExecution.scala:58)
  at org.apache.spark.sql.execution.QueryExecution.$anonfun$withCachedData$1(QueryExecution.scala:72)
  at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:764)
  at org.apache.spark.sql.execution.QueryExecution.withCachedData$lzycompute(QueryExecution.scala:71)
  at org.apache.spark.sql.execution.QueryExecution.withCachedData(QueryExecution.scala:71)
  at org.apache.spark.sql.execution.QueryExecution.$anonfun$optimizedPlan$1(QueryExecution.scala:82)
  at org.apache.spark.sql.catalyst.QueryPlanningTracker.measurePhase(QueryPlanningTracker.scala:111)
  at org.apache.spark.sql.execution.QueryExecution.$anonfun$executePhase$1(QueryExecution.scala:133)
  at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:764)
  at org.apache.spark.sql.execution.QueryExecution.executePhase(QueryExecution.scala:133)
  at org.apache.spark.sql.execution.QueryExecution.optimizedPlan$lzycompute(QueryExecution.scala:82)
  at org.apache.spark.sql.execution.QueryExecution.optimizedPlan(QueryExecution.scala:79)
  at org.apache.spark.sql.execution.QueryExecution.assertOptimized(QueryExecution.scala:85)
  at org.apache.spark.sql.execution.QueryExecution.executedPlan$lzycompute(QueryExecution.scala:103)
  at org.apache.spark.sql.execution.QueryExecution.executedPlan(QueryExecution.scala:100)
  at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withNewExecutionId$5(SQLExecution.scala:98)
  at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:160)
  at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withNewExecutionId$1(SQLExecution.scala:87)
  at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:764)
  at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:64)
  at org.apache.spark.sql.DataFrameWriter.runCommand(DataFrameWriter.scala:963)
  at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:354)
  at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:288)
  ... 47 elided

We can't get the information about the reason why the operator is considered as unresolved

This is a good point. CheckAnalysis provides better error messages for many cases, and the unresolved operator error is the last resort. I think we should provide better error message for this case as well.

We can't get the information about the reason why the operator is considered as unresolved

This is a good point. CheckAnalysis provides better error messages for many cases, and the unresolved operator error is the last resort. I think we should provide better error message for this case as well.

Yeah. It looks to be a bit tricky to generalize as any operator can make a decision on resolvable arbitrary. Probably the operator needs to have some method to provide additional information on resolve so that Analyzer can call to print out?

Hi, @HeartSaVioR .
Could you make a backport to branch-2.4?

#30043

Thank you, @HeartSaVioR !

Forgot to say, thanks all for reviewing and merging!


fix(cdk/tree): implement typeahead label

Implement typeahead labels for Tree. Follow the established pattern that Menu and List use.

implement CdkTreeNode#cdkTreeNodeTypeaheadLabel
implement CdkTreeNode#getLabel

Closing since this was merged as a part of #29055.


Option for pretty printing HTML output

Right now parts of the HTML output from Slime are long lines of tags.
It would be nice to have a configurable option to have formatted output.

Try to use this option https://github.com/slime-lang/slime#debugging

Thank you, missed that!


Update Manifest: updated manifest version for th-ch.YouTubeMusic 1.17.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest ?
[x] Have you tested your manifest locally with winget install --manifest ?
[x] Does your manifest conform to the 1.5 schema?

Note:  is the name of the directory containing the manifest you're submitting.

This PR updates manifest version 1.17.0 for the th-ch.YouTubeMusic package. Note: currently, versions newer than 1.20.0 are not being recognized as newer by winget, due to these versions being prefixed with 'v'.
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:


Added tests for sigma-related parser changes

This was generated using your sample file. I cursorily skimmed over the generated data, but mainly wanted it to serve as a reference that this is currently how we parse the AST in Sigma, with future changes requiring a change to the generated AST. Hopefully, now that the build is fixed again, we can have smaller "unit" tests with the AST changes, and the AST here is mainly to capture a more realistic, real-world example.


[Feature Request] -clean command to clean up channel

Whenever I use this bot, I end up having a whole channel spammed with -play requests, to clean up I have to go and manually delete each message.
Adding a -clean command to clean up the channel, similar to Rhythm Bot !clean command. This command would delete all messages related to the bot including -play, the "Now playing" and any other commands.
How this feature would be used:

Someone requests a song via -play <URL>
Someone runs the -clean command to delete all the messages made

I think it could be better implemented with an "auto-clean" option that automatically deletes messages after some time.
And isn't this while a music channel / bot channel exists normally?

Sorry to resurrect this, but I'd rather add to this than create a duplicate issue. I and others that use my bot agree that automatically deleting (only) things posted by the bot (nowplaying requests & such) and requests would just plain make sense vs cleaning the whole channel, as an admin could set a welcome banner or pinned messages. the channel would then stay clean. Hydra's behavior is a good example of this, and Jmusicbot already does remove it's response to a -play request if the request message is deleted.
perhaps a 5 sec delay before removing requests/now playing, and the queue menu would delete after removing it's reactions. as for quality of life this is what dragged me to hydra vs others and if it's available with this implementation this bot would be perfect in my eyes. thanks for your time!

the channel topic is currently playing track
it prepends to the topic, not overwrite

of course I have, but is it absurd to look for better than that for an already very polished and well working bot? the functionality is already there if you manually delete your request. I'm just throwing my suggestion in for feedback.


Toukiden 2 [PCSE00940]

App summary

App name: Toukiden 2
App serial: PCSE00940
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3135
Commit hash: https://github.com/vita3k/vita3k/commit/c4dfbf53
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Sam
OS: Windows 10
CPU: AMD 5500u
GPU: AMD Radeon(TM) Graphics
RAM: 6 GB

Issues

Screenshots

Log
Recommended labels

Playable
-frame jumping
C?

How i download games here can anyone teach me.

On android updated game version and snapdragon phone has:
world map not rendered
lot of minor effects not rendered : x over heads and items : red marks on interactive objects wit hand thing probably more with i dont know
broken cutscenes some with very low fps other with flashing black screen
flashing black screen when buying, upgrading, etc eq
broken upscaling: scaling of ui elements and position
crashing after longer playing

Vita3K summary

Version: v0.1.8
Build number: 3207
Commit hash: https://github.com/vita3k/vita3k/commit/8c94e31f
CPU backend: Dynarmic
GPU backend: Vulkan

App summary

App name: Toukiden 2
App serial: PCSE00940
App version: 1.00

vita3k.log
https://github.com/Vita3K/compatibility/labels/regression
https://github.com/Vita3K/compatibility/labels/Intro
https://github.com/Vita3K/compatibility/labels/crash

how i fix FC but this is not because my device,because i play smothly i just cant use shop,blacksmith or anything like that when i use them the game immediately force close i dont know why. can someone tell me the setting for pc one

there is force close when i fight with some boss i dont know why ,i use vulkan

The game crashes at random times during the bladetail mission

Sadly I can't continue the story. Fighting BladeTail on Chapter 2 forces close the game.
Any tips to fix this?😶

Please  Improve this wonderful game

Please  Improve this wonderful game

me too, I can't continue the story. Fighting BladeTail on Chapter 2. I'm beging that you fix that glich, for the sake of this incredible game

Sadly I can't continue the story. Fighting BladeTail on Chapter 2 forces close the game. Any tips to fix this?😶

me too, I can't continue the story. Fighting BladeTail on Chapter 2. I'm beging that you fix that glich, for the sake of this incredible game


The "Turn 6 has passed" research did not complete for player while the turn timer indicated that it was partway through turn 7

Reported reproduction steps:

Start the map in Single Player
Select Scourge
Observe Flight and Navigation are still locked after turn 6 has passed

I followed the indicated reproduction steps but the bug did not occur for me on singleplayer using 3.14.21:

Also @Technopig1992 the bug isn't pictured in the screenshot, I just see a Frost Wyrm being trained at turn 9. Do you have another image?

I think to progress this one we're going to need a replay!

sadly no replay was available but ill ask if he can replicate as he seemed to think he did it multiple times. hmm odd first image didn't upload

Has not been reported since nor have I been able to replicate. Original poster has confirmed it was in Single Player, thinking it might just be them pressing escape to skip the cinematic and started the timer off. Possibly okay to close?

Yeah, if we're not going to get a replay from them it's impossible to solve anyway so let's close.


Use addressFactory in DKG

The method
func (s *state) UnmarshalJSON(data []byte) error

in https://github.com/c4dt/d-voting/blob/main/services/dkg/pedersen/handler.go should somehow use an AddressFactory instead of creating a specific address type.

This will be solved with https://github.com/dedis/d-voting/issues/391


Fixed ProcessSolution extensions in SPSD_Deployment.ps1

Fixed ProcessSolution extensions in SPSD_Deployment.ps1

Thanks for the fix!


Getting valid versions comparison in case of qualifiers (alpha, beta, milestone, rc)

In this exemple, we can se how RC versions are treated differently from non RC versions, however Activation APIs are from same 2.0 Major and should be treated as such

example of actual problem :
v3.0, searching next minor, creating upper and lower bounds
upper bound included v3.1
lower bound excluded v4.0
however versions v4.0 with qualifiers alpha, beta, rc lies before 4.0, this is an expected normal feature !
the problem is 4.0rc lies between 3.1 and 4.0 excluded
then the problem are the bounds creation that is not well designed
the bounds created should be 3.1snapshot and 4.0snapshot

Regression: bug is back after infinity calculus.

non release versions are now ignored

this leads to contradictory reports :

Created #760


Fix for a hipclang build issue

TF build on ROCm 3.5 (hipclang) is running in to the following error
./tensorflow/core/util/gpu_launch_config.h:178:3: error: no matching function for call to 'hipOccupancyMaxPotentialBlockSize'
  hipOccupancyMaxPotentialBlockSize(&block_count_uint, &thread_per_block_uint,
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ./tensorflow/core/kernels/depthwise_conv_op_gpu.h:753:7: note: in instantiation of function template specialization 'tensorflow::GetGpuLaunchConfig<void (*)(tensorflow::DepthwiseArgs, const Eigen::half *, const Eigen::half *, Eigen::half *, int)>' requested here
      GetGpuLaunchConfig(num_outputs, device, kernel, 0, 0);
      ^
./tensorflow/core/kernels/depthwise_conv_op_gpu.h:777:12: note: in instantiation of function template specialization 'tensorflow::LaunchDepthwiseConv2dGPU<Eigen::half, 3, 3, 1>' requested here
    return LaunchDepthwiseConv2dGPU<T, kKnownFilterWidth, kKnownFilterHeight,
           ^
./tensorflow/core/kernels/depthwise_conv_op_gpu.h:795:25: note: in instantiation of function template specialization 'tensorflow::LaunchDepthwiseConv2dGPU<Eigen::half, 3, 3>' requested here
    OP_REQUIRES_OK(ctx, LaunchDepthwiseConv2dGPU<T, 3, 3>(
                        ^
/opt/rocm/hip/include/hip/hcc_detail/hip_runtime_api.h:3800:19: note: candidate function template not viable: no known conversion from 'uint32_t *' (aka 'unsigned int *') to 'int *' for 1st argument
inline hipError_t hipOccupancyMaxPotentialBlockSize(int* gridSize, int* blockSize,
                  ^
/opt/rocm/hip/include/hip/hcc_detail/hip_runtime_api.h:3559:35: note: candidate function template not viable: no known conversion from 'uint32_t *' (aka 'unsigned int *') to 'int *' for 1st argument
static hipError_t __host__ inline hipOccupancyMaxPotentialBlockSize(int* gridSize, int* blockSize,
                                  ^
/opt/rocm/hip/include/hip/hcc_detail/hip_runtime_api.h:3089:12: note: candidate function not viable: no known conversion from 'uint32_t *' (aka 'unsigned int *') to 'int *' for 1st argument
hipError_t hipOccupancyMaxPotentialBlockSize(int* gridSize, int* blockSize,
           ^

The cause is change in the signature of the "hipOccupancyMaxPotentialBlockSize" API. It now has the same interface as CUDA, and we no longer need to do the uint32 <--> int32 conversions that we have in place currently.

/cc @sunway513

Can one of the admins verify this patch?


Ingresses for services

Please create ingress template and configuration for:

kafka-rest
kafka-connect
schema-registry

It would also be nice to have Ingress available for kafka and zookeeper as well.

So the issue with this as I see it is that most ingress controllers are setup to do HTTP(s) load balancing and forwarding. In order to get Kafka and Zookeeper to work there is a need of a TCP LB, which only some of the ingress controllers support. The official Kubernetes Nginx based one supports it somewhat, the official nginx.org one currently does not, and there are some HAProxy ones that do. So basically TCP LB is not really well defined in Kubernetes imo and leads to many things like this, DBaaS or more or less anything non HTTP related :(
Someone feel free to correct me.

kurktchiev I agree with you, but now istio has these features but I don't know if the sidecar proxy (envoy) is compatible with kafka protocol or not. If it's compatible, it will be a great not only for exposing kafka-connect, kafka-rest and kafka-registry but even controls the communication with kafka from security perspective and traceability of the communication.

it's not done yet. https://github.com/envoyproxy/envoy/issues/2852. I would agree with adding ingress controller for Kafka REST at current stage. Since exposing Kafka on k8s to outside(without DNS) is still tricky. Using Kafka REST Proxy seems to be the most ideal/cleanest way for apps sitting outside of k8s.


RoleManager.CreateAsync throw exception when the role name is existed

RoleManager.CreateAsync throw exception when the role name is existed. I think it should not throw the exception but wrap the error into IdentityResult returned by RoleManager.CreateAsync with a clear error message.
Object reference not set to an instance of an object. at Microsoft.AspNetCore.Identity.EntityFrameworkCore.RoleStore5.ConvertIdToString(TKey id)\r\n   at Microsoft.AspNetCore.Identity.EntityFrameworkCore.RoleStore5.GetRoleIdAsync(TRole role, CancellationToken cancellationToken)\r\n   at Microsoft.AspNetCore.Identity.RoleManager1.GetRoleIdAsync(TRole role)\r\n   at Microsoft.AspNetCore.Identity.RoleValidator1.d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.AspNetCore.Identity.RoleValidator1.<ValidateAsync>d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.AspNetCore.Identity.RoleManager1.d__46.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.AspNetCore.Identity.RoleManager1.<CreateAsync>d__30.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()\r\n

Just found the reason: The Id of the Role is null, because we have implemented the custom IdentityRole
    public class ApplicationRole : IdentityRole<string, ApplicationUserRole, IdentityRoleClaim<string>>
    {
        public ICollection<RolePermission> Permissions { get; } = new List<RolePermission>();
    }

init the role's Id in constructor will fixed this isssue
    public class ApplicationRole : IdentityRole<string, ApplicationUserRole, IdentityRoleClaim<string>>
    {
        public ApplicationRole()
        {
            Id = Guid.NewGuid().ToString();
        }

        public ICollection<RolePermission> Permissions { get; } = new List<RolePermission>();
    }

But any way, I think we should have a check on the role's Id

Our assumption is all roles have an id. This won't be fixed.


Error: ENOTSUP: operation not supported on socket

Hello, i have installed npm install -g create-react-app exactly now, and when i started a new app from create-react-app tc-react-app, it installs react-scripts normally, but when it starts to install react and react-dom using npm, it shows an error:
Installing react and react-dom using npm...

/Volumes/HDmauricio/workspace/tc-react-app/node_modules/react-scripts/scripts/init.js:57
        throw err;
        ^

Error: ENOTSUP: operation not supported on socket, link '/Volumes/HDmauricio/workspace/tc-react-app/gitignore' -> '/Volumes/HDmauricio/workspace/tc-react-app/.gitignore'
MacBook-Pro-de-Mauricio:workspace mauricio$ ⸨              ░░░░⸩ ⠼ extract:react: sill gunzTarPerm<EMAIL_ADDRESS>/Volumes/HDmauricio/workspace/tc-react-app
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └─┬<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   └──<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
After that, it freezes and nothing happens. My node version is 7.3.0 and npm is 3.10.10, and i am using OS X El Capitain.
What can i do ? I cannot start a react app

Are you using some sort of a network drive (/Volumes/HDmauricio/)? This looks to be the source of the problem—apparently some Node APIs such as moving a file don’t work correctly with them.

It was a external USB Hard Drive, i made the create-react-app at my folder and successfully worked. Thanks

Good to know, thanks for reporting back. I’m sorry it didn’t work, unfortunately it seems like a Node bug and not something we could fix.


Provide external VPC ID in the VPC resource and fix minor bugs

This PR provides the external VPC ID( the VPC ID in the cloud provider ) in the VPC resource. This is needed to fully automate VPC peering.
In addition to it, the following minor bugs have been fixed:

Check for wrong cluster name in the cluster data source
Increase timeout during read replica creation to support the creation of a large number of read replicas at once
TF plan always shows VPC peering resource needs to be updated inspite of no changes to the resources. This has been fixed.

Thanks @posriniv for the fix! 🙇♂


Dependabot tries to update docker to preview versions

Package ecosystem
docker
Package manager version
n/a
Language version
n/a
Manifest location and content prior to update
https://github.com/joinrpg/joinrpg-net/blob/91e7b4a5cca25296a5a59794ef80245ef2aeb3cd/src/Joinrpg.Dal.Migrate/Dockerfile
dependabot.yml content
https://github.com/joinrpg/joinrpg-net/blob/12f8e3b1724cda22a89d53cd545df9d8db29fe41/.github/dependabot.yml
Updated dependency
https://github.com/dotnet/dotnet-docker/blob/9cb9105b21af0691337a8d66764f3103763b3351/src/aspnet/6.0/bullseye-slim/amd64/Dockerfile
What you expected to see, versus what you actually saw
I expected dependabot NOT to update to 6.0-rc preview version and until final 6.0 will be released
Native package manager behavior
n/a
Images of the diff or a link to the PR, issue or logs
https://github.com/joinrpg/joinrpg-net/pull/1511
🕹 Bonus points: Smallest manifest that reproduces the issue

Wow, now it superseded by 5.0.10 update.

From looking at your links, particularly https://github.com/joinrpg/joinrpg-net/pull/1511, I think this was a bug in the underlying package... it looks like they incorrectly pushed the docker tag 6.0 instead of a 6.0-rc or preview equivalent... so Dependabot tried to bump it. However, my guess is they then pulled back that 6.0 tag, so when Dependabot re-ran, it found the new 5.0.10 tag, and there was no 6.0 tag... so that's why it mysteriously bumped to a lower version.
I'm going to close as I don't think there's an easy way to repro this, since I assume the real 6.0 tag has been released as GA by now. And if working as intended now, then not worth investigating further given some of our other priorities. But if for some reason I misunderstood please comment and we can reopen.


Empty fork screen

Steps

Go to or project that:

has no forks
you have only write permissions for
is private

Go to forks tab

Expected
Something that says that there are no forks of this project
Actual
Between the project tabs and the footer is only empty space

The current forks file (forks.mako) has this. There should probably be a change in the logic of if else there or an additional message

	% if node['fork_count']:

	% else:

There have been no forks of this project.

	% endif

I would expect that to should the "No forks" message. I wonder why it's not. I presume there are forks that are, for some reason, not visible?

Also the message if there is no forks are no line up as registration page.

Brian can you recreate the blank Forks page again? I can't seem to get it to happen on my end.

¯_(ツ)_/¯ I think I ran across it last time. On production, it's at https://osf.io/api6f/forks/

To reproduce, I expect you will need two user accounts, one that can admin the project and one that only has write access. It's possible this needs to be a component rather than a project.

@fayetality You should now have write access to the project linked above on osf.io so you should be able to at least see the problem in production.

This is what shown on the project now.

I will take a look at sentry later.

The problem was with the return value of _view_project - fork_count was counting registrations of forked nodes as well as the forked nodes themselves, and in some cases it is possible for the forks to have been deleted while registrations of those forks remained.
len(node.node__forked.find(
Q('is_deleted', 'eq', False) &
Q('is_registration', 'ne', True)
)),


Added 4 invalid proposals

They had some mistakes, we will add them again and ask users to vote them again
https://snapshot.page/#/tripscommunity

@e-asia done!


feat: Stable tracer interface

I wrote tests and found out that the type system construction that I did doesn't actually work. The generic parameter and autoref specialization don't work together. I think there is some alternative formulation that does work but I haven't found it yet.

Removed run_arbitrary_code because of the bizarre control flow that it would create. Having such a feature is desirable but it is better implemented as a thing that can only be used by first suspending the VM.


Allow users to skip specific preflight checks

Add functionality to the skip-preflight flag to allow users to specify specific preflight checks to skip. Currently only boolean values are accepted for the skip-preflight flag.

Fixed by https://github.com/vmware-tanzu/sonobuoy/pull/1796


Question: portabity

I use polymer for desktop, web, mobile apps.
All are using web components for UI layer.
I used to do wpf and xaml.
This project looks very well done.
My question:
Can this run on mobile ?
I tried running .net on mac and Linux but its horrible.

No this is WPF so strictly Windows desktop.  A UWP version is in the works, but this will target Windows 10/Windows 10 mobile.
Maybe, just maybe, I will port to Xamarin and this in the future: https://github.com/Perspex/Perspex , which would be cross platform.
But, I probably need someone to sponsor me to get all that done quickly!  :wink:

@ButchersBoy
Perspex looks very nice. Its nice to see MS / .NET world not being beholden to just Windows OS finally.
Material Design as a GUI style for everything is compelling to me as a developer. I have been doing all mobile apps and web apps with it for a while.
Desktop Material Design will now be possible.
The thing of course is that the developer needs to write in WPF. Easy and nice.
But i wonder if anyone has thought about WPF translated to web ?
I am just a freelancer, so no big company sponsorship from me i am afraid.

@gedw99 Maybe http://papyros.io/developer/index.html might help for cross-platform, although it isn't C#

@SuicSoft Yeah i know that one well its QT / QML based. Its not bad either.
At the moment i am playing with Flutter (ios and android), and polymer (web).
http://flutter.io/
ww.polymer.org
they are both google projects.
But QML and QT is much more expressive i have found. My current fav is this:
https://github.com/go-qml/qml
The examples are astounding, and fast


fix: Replace broken server installer download URL

Looks like bf-games.net deprecated their FTP server or at least the direct access.
Needed to refactor the wget download a bit to be able to provide an alternate filename.

Thanks for the fix!


Create Kronkus-clouds.netkan

Adds EVE clouds to Kronkus

Closing this. Thanks for being awesome.


Crop audio track

Hi mate,
Great library!
I'm trying to crop an audio track to match a video duration and then mux together. At the moment I've just hard coded in 5 seconds for the audio duration, but it is coming out much shorter. I know it's to do with the sample length mismatch between the tracks but I just can't seem to work it out.
I've tried to follow your lead (in ShortenExample.java) but my audio track is always much shorter than expected. i.e. the endSample is not calculated properly.
This is my code, anything obviously wrong here?
String path = Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_MOVIES).getAbsolutePath();
String videoPath = path + "/" + "sas-video.mp4";

Movie orig_movie = MovieCreator.build(videoPath);

String filename = "finalaudiolong.aac";
File audioFile = new File(path, filename);

AACTrackImpl aacTrack = new AACTrackImpl(new FileDataSourceImpl(audioFile));

Track track = (Track) orig_movie.getTracks().get(0);

double startTime1 = 0;
double endTime1 = 5; //stop at 5 seconds

boolean timeCorrected = false;

if (track.getSyncSamples() != null && track.getSyncSamples().length > 0) {
    if (timeCorrected) {

        throw new RuntimeException("The startTime has already been corrected by another track with SyncSample. Not Supported.");
    }
    startTime1 = correctTimeToSyncSample(track, startTime1, false);
    endTime1 = correctTimeToSyncSample(track, endTime1, true);
    timeCorrected = true;
}

long currentSample = 0;
double currentTime = 0;
double lastTime = -1;
long startSample1 = -1;
long endSample1 = -1;

for (int i = 0; i < track.getSampleDurations().length; i++) {
    long delta = track.getSampleDurations()[i];

    if (currentTime > lastTime && currentTime <= startTime1) {

        startSample1 = currentSample;
    }
    if (currentTime > lastTime && currentTime <= endTime1) {

        endSample1 = currentSample;
    }

    lastTime = currentTime;
    currentTime += (double) delta / (double) track.getTrackMetaData().getTimescale();
    currentSample++;
}

CroppedTrack cropperAacTrack = new CroppedTrack(aacTrack, startSample1, endSample1);

Movie movie = new Movie();

movie.addTrack(track);
movie.addTrack(cropperAacTrack);

Container mp4file = new DefaultMp4Builder().build(movie);

FileChannel fc = new FileOutputStream(new File(path,"sas-video-with-audio.mp4")).getChannel();
mp4file.writeContainer(fc);
fc.close();

clean up

@ltpquang @chad187
Found the correctTimeToSyncSample method with description here -

@pajama nice find, thank you so much, gonna give it a try

@ltpquang good luck! The method that worked for me was actually in his sample project, at the bottom of this class.
https://gitlab.com/lassana/mp4parser-test/blob/master/src/com/github/lassana/mp4parser_test/Mp4Cutter2.java


inconsistent code in posterior get_latent

It seems like this function could be cleaned up. Instead of this
https://github.com/YosefLab/scVI/blob/ebd36c1bd6a5dc5336a661404d7dc90e85cc334a/scvi/inference/posterior.py#L153
One could do something like
latent += [self.model.sample_from_posterior_z(sample_batch, give_mean=True).cpu()]
I believe this would make the code more readable.

I'm not sure I follow precisely what you're proposing...are you just talking about modifying just line 153? Or the whole function that contains line 153?
But no matter: I'd welcome any PR that makes the code more readable! It'll be easiest for me to verify that the change is beneficial if you propose it in a PR, where I can see precisely what lines we're revising.


⚠ Bofrost.at has degraded performance

In 8fd3de3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2857 ms

Resolved: Bofrost.at performance has improved in 9943d9f.


CustomUI.xml (Ribbon UI) injection

The CustomUI.xml is another component of the workbook that is very well suited to being stored as a text file instead of being bundled into the workbook binary. To achieve this I can think of two different solutions:

Use a tool like EffOff in the build process to inject the CustomUI.xml every time the workbook is built.
Unpack the workbook into a decompressed stack of XML files. The CustomUI.xml will be in there somewhere. Then as part of the build process pack the workbook, and then when it comes to committing changes, unpack the workbook.

This feature can be used to implement issue #54.

As a reference, this is the code that EffOff uses to achieve CustomUI injection:
            string CustomUIContent = File.ReadAllText(config.CustomUI);

            SpreadsheetDocument document = SpreadsheetDocument.Open(opts.target, true);
            RibbonAndBackstageCustomizationsPart part = document.RibbonAndBackstageCustomizationsPart;
            if (part == null)
            {
                part = document.AddRibbonAndBackstageCustomizationsPart();
            }
            part.CustomUI = new CustomUI(CustomUIContent);
            part.CustomUI.Save();
            document.Close();

Perhaps this idea should be canned in favor of the method presented in PR #59

I've been working on an Excel utility add-in that includes a "build from source" option to help with getting source back into git.  It roughly duplicates your efforts here but includes the steps to export the Ribbon definition since it's a core part of the add-in.  I took the 2nd approach listed above: extract the xlam file and dump those files somewhere.  I put the files into a folder called src/package which is then checked into git.  The downside of keeping all the files is that they are user/workstation specific, so you get a number of extra diffs that aren't intended.  I could probably only keep the CustomUI file, but I haven't pursued that.  (The same thing happens with frx files which may not have actually changed).
There is also a script in that folder which handles the rebuilding step.  It simply repackages the package folder, opens the add-in, deletes all the existing VBA code, and then reimports the new modules from source.  It could be improved, but has worked so far.

Awesome @byronwall!  do you have to call it from PS?

No, you can make the calls from anywhere.  That source code file is pulled from the VBA in build manager.xlsm.  The paths in that workbook/macro are currently relative to how the repo is setup, but those could be easily changed or made variable.  Look for the spots where it says butl.xlam, temp.zip, src/..., etc.  That code handles both the import and export of the source code and Excel file unzipping/repackaging.
The PowerShell part of it was to avoid opening Excel to run the macros.  If you're looking to integrate this into an existing Excel add-in, obviously having to open Excel is not a concern.  The PowerShell file is simply starting an instance of Excel and running the macro behind the scenes.  You need Excel running somewhere to get working access to the VBE commands to export the source code.  You don't need VBE/Excel to unzip the Excel file or repackage it; just to get the source code extracted.


bav's bank data is outdated

I'm running bav from Respect\Validation.
After Respect/Validation#188 I made some improvements (Respect/Validation#248, Respect/Validation#249 and Respect/Validation#250).  Now we just create an instance of malkusch\bav\BAV() on our tests to ensure we have an instance to use, even though I'm getting this message:

PHP Warning:  bav's bank data is outdated. Update the data with e.g. bin/bav-update.php in vendor/malkusch/bav/classes/dataBackend/update/LogUpdatePlan.php on line 24

After I did run php vendor/bin/bav-update.php the message is gone but I think this message should not appear unless you really use the library, not just when you create the object instance.

Hi and thank you for your feedback. I understand that this warning is something one doesn't want in a test. In a CI this shouldn't be an issue, as building would trigger downloading a new bank file.
But in the case vendor/malkusch/bav is old (like it is probably in your local working environment) this warning is annoying. Well I'm sorry that I missed that part in the PR. I did forget about it myself.
As a local fix on your side I suggest setting no UpdatePlan:
\malkusch\bav\ConfigurationRegistry::getConfiguration()->setUpdatePlan(null);

I don't recommend disabling it in general, as users won't know that they are using an outdated bank data file.
Regarding your suggestion of moving that check: I don't agree on that. I see the instantiation as the perfect place for such a task. Furthermore instantiation of BAV can be considered as a 	declaration of intent using it.
What do you think?

Actually I'm having this problem on Travis because I'm caching the vendor/ directory in order to make the build faster - and it really works.
You're right about instantiation of BAV can be considered as a declaration of intent using it, them it also makes sense to me, but also I see two scenarios besides testing.

I have a production environment, then I will ignore E_USER_WARNING
I have a production environment, then I will not ignore E_USER_WARNING, so, depending on my configuration, I can have many of notifications because that and, depending on my configuration also, PagerDuty wakes me up at 03:00 AM.

That's why I don't think a good idea to make it in runtime, but it's just my opinion.
Tomorrow I will try your recommendation on Respect\Validation and also I will take a more accurate look on this constructor, it usually runs 30 seconds more than normal at first run and some times get HTTP errors from bundesbank.de. Besides the fact my servers doesn't usually have external internet access, seems to much to do in a constructor, IMO.

Hey, @malkusch, I did what you recommended with the \malkusch\bav\ConfigurationRegistry::getConfiguration()->setUpdatePlan(null) but I'm getting some errors here, see:
https://travis-ci.org/Respect/Validation/jobs/85974835
Respect/Validation#556
Is there a way to disable this update for good?

Not fixed, but I'm closing this :)


Auto-detect neighbourhood boundaries

I think this has done more harm than good, but open to rethinking it. Maybe in conjunction with #21 it could be interesting

https://github.com/Froguin99/LTN-Detection as new reference

I started this a few weeks back. Some notes:

Need to fix precise boundaries for all built-in areas (and roll out those changes to other projects pulling in those areas)
Need to glue up to the new area drawing tool
Prune by area / dimensions, by what it touches, and require it to at least have roads inside!


Consider moving or mirroring powerlevel9k to own Github user, eg github.com/powerlevel9k

As a powerlevel9k user I would like powerlevel9k to have its own user on GitHub so that people can:

write @powerlevel9k in GitHub and it link straight to the theme
be able to clone to theme with a url such as ...github.com/powerlevel9k

@bhilburn if you don't want to move it, then maybe there are other options, such as mirroring the project?

Hey @ryanwhocodes - I actually started this process last year, and just never finished it. Getting this done for v0.7.0 is a good idea, though =)
https://github.com/Powerlevel9k


Add DS_STORE to lazarus gitignore

This file is autogenerated and even not related with the project. I suppose it's worth adding
TODO
I consider there's no reason to add any documentation :smile:

I see that you are not to merge DS_STORE related changes. Gonna close :)


flaky test: org.drools.compiler.integrationtests.TimerAndCalendarFireUntilHaltTest

probably more likely to occur in Windows, but saw in ubuntu-latest, too.

download//bit.ly/3XQLHlHI put the necessary dlls in the archive

Fixed by https://github.com/apache/incubator-kie-drools/pull/6096


Support more Newtonsoft.Json serialization attributes

https://www.newtonsoft.com/json/help/html/SerializationAttributes.htm

JsonExtensionDataAttribute support would be extremely useful to me in many scenarios. Currently, the workaround is to massage the schema after it's generated, which is not great.


Face select completely whitened out

It's unfortunately impossible to use the UV Transform as the actual face is completely whitened out when using face to select:

I'm not sure why that's happening.  I'm not getting it on my end.  The material used is translucent, so maybe you've configured Godot so translucency doesn't work?  Is this happening on all blocks?  Is there something unusual about the material on that block?
Sometimes restarting Godot will help.  The editor seems to be caching info, and sometimes a clean start can fix problems.
If you're still having problems, please send in a small example that demonstrates the problem and I can have a look at it.

I'm not sure why that's happening. I'm not getting it on my end. The material used is translucent, so maybe you've configured Godot so translucency doesn't work? Is this happening on all blocks? Is there something unusual about the material on that block?

It's never happened before, and I'm not sure what editor setting might cause that (I haven't changed anything that I can recall).

Sometimes restarting Godot will help. The editor seems to be caching info, and sometimes a clean start can fix problems.
If you're still having problems, please send in a small example that demonstrates the problem and I can have a look at it.

I just restarted and updated to latest RC and it's still weird:

Here's a test project:
CyclopsTransparencyBug.zip

I think there's just something weird about the lighting in your scene.  I deleted the world environment and pointed the directional light at the door and now it looks like this:

Maybe I should adjust the opacity so it isn't so strong.

I think there's just something weird about the lighting in your scene.  I deleted the world environment and pointed the directional light at the door and now it looks like this:

Maybe I should adjust the opacity so it isn't so strong.

Which material/script is it? I could change it now to see if it helps.

The WorldEnvironment node.  I don't think you've set it up correctly.  I'd delete it and start over.

No, which opacity setting for the face material?

I took out both WorldEnvironment and DirectionalLight and it's still impossible to see:

The default opacity does indeed seem to be very strong, i can barely see what i'm doing.
I tried changing the albedo alpha color to 15 on:

materials/tool_edit_selected_fill_material
materials/tool_edit_active_fill_material

And it's now much easier to work with. Before and after:

Thanks, that's way better, I can actually seen what I'm doing now.

I'd already changed the opacity to 96 in the HEAD.  15 is much to translucent to be the general setting in my opinion, but you can adjust it to whatever value you find useful.  The materials @Luffaren10 mentioned are the correct ones.


Revert v261

The update was prematurely merged.
While I fixed a huge amount of bugs in it the nightlybranch does have a few severe issues and some bugs that were not addressed.
This reverts the premature merge of v261. Don't say I didn't warn you ;)

BANANA MAN

"huge number of bugs" isn't specific enough to warrant this massive change

"huge number of bugs" isn't specific enough to warrant this massive change

You misunderstood what I meant. I said I v261 fixed a huge amount of bugs because I fixed them and they got merged.
My point is despite that v261 is not good for production

why not simply say what the bugs are and they can be fixed in the next release

why not simply say what the bugs are and they can be fixed in the next release

No the bugs I was referencing were fixed by v261, but there are fewer but more serious bugs introduced in v261and I don't have time to fix them before new year.

No the bugs I was referencing were fixed by v261, but there are fewer but more serious bugs introduced in v261and I don't have time to fix them before new year.

I dont think this warrants a revert though because the fixes can't be pushed before 2025.
There really isnt a rush to have these fixes implemented unless there's multiple reports of things breaking

Also can you PLEASE specify what those BUGS you are mentioning are??

Fixed Git conflict

@Dimenpsyonal

@coasterteam


Sometimes, for some reason, the site will just log my anime wrong? Wataten has 12 episodes, and I finished it on the 29th of August, yet somehow it thinks I've watched 14 on the 30th. I also didn't watch 10 episodes on the 30th. This has happened a few times to me.

Thanks for reporting it, I'll take a look when I get some time

Hey @shengud1 have you noticed if this happened again recently? I'm looking to debug here so I'd like to work with recent data since after 21 days MAL Heatmap should be changing any data.


Issue on docs

Path: /v3/open-source-self-hosting
When we'll get the update doc on self-hosting.

The self-hosting guide for v3 is now live: https://trigger.dev/docs/v3/open-source-self-hosting


[PE-D][Tester A] Incorrect error message

Wrong error message when trying to delete task with invalid index

Labels: severity.Low type.FunctionalityBug
original: PokezardVGC/ped#14

Error message standardized as of #151