[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/event_add.g.dart    [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/home_menu.g.dart    [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/list_view.g.dart    [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/menu_arrow.g.dart   [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/menu_close.g.dart   [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/menu_home.g.dart    [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/pause_play.g.dart   [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/play_pause.g.dart   [        ] ->
+file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/search_ellipsis.g.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/animated_icons/data/view_list.g.dart    [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/app.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/app_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/app_bar_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/arc.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/back_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/banner.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/banner_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/bottom_app_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/bottom_app_bar_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/bottom_navigation_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/bottom_sheet.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/bottom_sheet_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/button_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/button_bar_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/button_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/card.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/card_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/checkbox.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/checkbox_list_tile.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/chip.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/chip_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/circle_avatar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/color_scheme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/colors.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/constants.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/data_table.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/data_table_source.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/date_picker.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/debug.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/dialog.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/dialog_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/divider.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/divider_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/drawer.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/drawer_header.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/dropdown.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/binding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/expand_icon.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/expansion_panel.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/expansion_tile.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/feedback.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/flat_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/flexible_space_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/floating_action_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/floating_action_button_location.dart    [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/floating_action_button_theme.dart       [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/flutter_logo.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/grid_tile.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/grid_tile_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/icon_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/icons.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/ink_decoration.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/ink_highlight.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/ink_ripple.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/ink_splash.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/ink_well.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/input_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/input_decorator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/list_tile.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/material.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/material_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/material_localizations.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/material_state.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/mergeable_material.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/outline_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/page.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/page_transitions_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/paginated_data_table.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/popup_menu.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/popup_menu_theme.dart
[   +1 ms] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/progress_indicator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/radio.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/radio_list_tile.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/raised_button.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/range_slider.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/refresh_indicator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/reorderable_list.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/scaffold.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/scrollbar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/search.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/selectable_text.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/shadows.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/slider.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/slider_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/snack_bar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/snack_bar_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/stepper.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/switch.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/switch_list_tile.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/tab_bar_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/tab_controller.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/tab_indicator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/tabs.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/text_field.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/text_form_field.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/text_selection.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/text_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/theme_data.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/time.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/time_picker.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/toggle_buttons.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/toggle_buttons_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/toggleable.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/tooltip.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/tooltip_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/typography.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/material/user_accounts_drawer_header.dart        [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/_network_image_io.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/alignment.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/basic_types.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/beveled_rectangle_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/binding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/border_radius.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/borders.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/box_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/box_decoration.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/box_fit.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/box_shadow.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/circle_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/clip.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/colors.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/continuous_rectangle_border.dart        [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/debug.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/decoration.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/decoration_image.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/edge_insets.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/flutter_logo.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/fractional_offset.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/geometry.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/gradient.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/image_cache.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/image_decoder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/image_provider.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/image_resolution.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/image_stream.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/inline_span.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/matrix_utils.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/notched_shapes.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/paint_utilities.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/placeholder_span.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/rounded_rectangle_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/shader_warm_up.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/shape_decoration.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/stadium_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/strut_style.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/text_painter.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/text_span.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/painting/text_style.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/clamped_simulation.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/friction_simulation.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/gravity_simulation.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/simulation.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/spring_simulation.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/tolerance.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/physics/utils.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/animated_size.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/binding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/binding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/scheduler/binding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/semantics/binding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/custom_layout.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/custom_paint.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/debug.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/debug_overflow_indicator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/editable.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/error.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/flex.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/flow.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/image.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/layer.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/list_body.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/list_wheel_viewport.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/paragraph.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/performance_overlay.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/platform_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/proxy_box.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/rotated_box.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/shifted_box.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_fill.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_fixed_extent_list.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_grid.dart
[   +1 ms] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_list.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_multi_box_adaptor.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_padding.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/sliver_persistent_header.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/stack.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/table.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/table_border.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/texture.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/tweens.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/viewport.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/viewport_offset.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/rendering/wrap.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/scheduler/debug.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/scheduler/priority.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/scheduler/ticker.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/semantics/debug.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/semantics/semantics.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/semantics/semantics_event.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/semantics/semantics_service.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/asset_bundle.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/binary_messenger.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/clipboard.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/font_loader.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/haptic_feedback.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/keyboard_key.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/keyboard_maps.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/message_codec.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/message_codecs.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/platform_channel.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/platform_messages.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/platform_views.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/raw_keyboard.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/raw_keyboard_android.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/raw_keyboard_fuchsia.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/raw_keyboard_linux.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/raw_keyboard_macos.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/system_channels.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/system_chrome.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/system_navigator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/system_sound.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/text_editing.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/text_formatter.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/services/text_input.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/actions.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/animated_cross_fade.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/animated_list.dart
[   +1 ms] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/animated_size.dart
[   +2 ms] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/animated_switcher.dart
[   +1 ms] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/annotated_region.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/app.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/async.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/banner.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/basic.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/bottom_navigation_bar_item.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/color_filter.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/constants.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/container.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/debug.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/dismissible.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/drag_target.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/draggable_scrollable_sheet.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_notification.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/editable_text.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/fade_in_image.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/focus_manager.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/focus_scope.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/focus_traversal.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/form.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/framework.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/gesture_detector.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/grid_paper.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/heroes.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/icon.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/icon_data.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/icon_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/icon_theme_data.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/image.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/image_icon.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/implicit_animations.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/inherited_model.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/inherited_notifier.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/inherited_theme.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/layout_builder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/list_wheel_scroll_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/localizations.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/media_query.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/modal_barrier.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/navigation_toolbar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/navigator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/nested_scroll_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/notification_listener.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/orientation_builder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/overlay.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/overscroll_indicator.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/page_storage.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/page_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/pages.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/performance_overlay.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/placeholder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/platform_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/preferred_size.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/primary_scroll_controller.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/raw_keyboard_listener.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/route_notification_messages.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/routes.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/safe_area.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_activity.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_configuration.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_context.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_controller.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_metrics.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_physics.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_position.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_position_with_single_context.dart [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_simulation.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scroll_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scrollable.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/scrollbar.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/semantics_debugger.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/shortcuts.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/single_child_scroll_view.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/size_changed_layout_notifier.dart        [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/sliver.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/sliver_layout_builder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/sliver_persistent_header.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/sliver_prototype_extent_list.dart        [        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/spacer.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/status_transitions.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/table.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/text.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/text_selection.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/texture.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/title.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/transitions.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/tween_animation_builder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/unique_widget.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/value_listenable_builder.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/viewport.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/visibility.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/widget_inspector.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/widget_span.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/src/widgets/will_pop_scope.dart
[        ] -> +file:///C:/Users/csell/flutter/packages/flutter/lib/widgets.dart
[        ] -> aac847c5-95f3-4a6f-a0bb-54ad51df2274 build\app.dill 0
[        ] Updating files
[ +102 ms] DevFS: Sync finished
[  +72 ms] Syncing files to device Windows... (completed in 2,419ms, longer than expected)
[   +3 ms] Synced 1.0MB.
[   +1 ms] Sending to VM service: _flutter.listViews({})
[   +2 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0x154486b28e0, isolate: {type:
@Isolate, fixedId: true, id: isolates/4430041082177899, name: main.dart$main-4430041082177899, number:
4430041082177899}}]}
[   +1 ms] <- accept
[        ] Connected to _flutterView/0x154486b28e0.
[   +2 ms] 🔥  To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".           [   +1 ms] An Observatory debugger and profiler on Windows is available at: http://<IP_ADDRESS>:57555/H1PhonUhw7k=/        [        ] For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".                       [+10601 ms] [ERROR:c:\b\s\w\ir\k\src\flutter\lib\ui\ui_dart_state.cc(148)] Unhandled Exception:
'package:flutter/src/gestures/converter.dart': Failed assertion: line 280 pos 20: 'state.down': is not true.
[        ] #0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:40:39)
[        ] #1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:36:5)                                   [        ] #2      PointerEventConverter.expand (package:flutter/src/gestures/converter.dart:280:20)                    [        ] #3      _SyncIterator.moveNext (dart:core-patch/core_patch.dart:144:12)                                      [        ] #4      ListQueue.addAll (dart:collection/queue.dart:655:25)                                                 [        ] #5      GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:84:27)            [        ] #6      _rootRunUnary (dart:async/zone.dart:1136:13)                                                         [        ] #7      _CustomZone.runUnary (dart:async/zone.dart:1029:19)                                                  [        ] #8      _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)                                             [        ] #9      _invoke1 (dart:ui/hooks.dart:263:10)                                                                 [        ] #10     _dispatchPointerDataPacket (dart:ui/hooks.dart:172:5)

PS C:\Users\csell\Code\flutter_cropping> flutter analyze                                                                Analyzing flutter_cropping...                                                                                No issues found! (ran in 12.2s)

PS C:\Users\csell\Code\flutter_cropping> flutter doctor -v                                                              [√] Flutter (Channel master, v1.10.1-pre.41, on Microsoft Windows [Version 10.0.18362.295], locale en-US)                  • Flutter version 1.10.1-pre.41 at C:\Users\csell\flutter                                                              • Framework revision 5a3a46ada2 (30 hours ago), 2019-09-07 18:37:41 -0400                                              • Engine revision c9ea4dba8d                                                                                • Dart version 2.5.0 (build 2.5.0-dev.4.0 ec7ec4ecf7)                                                                                [√] Android toolchain - develop for Android devices (Android SDK version 29.0.1)                                           • Android SDK at C:\Users\csell\AppData\Local\Android\sdk                                                              • Android NDK location not configured (optional; useful for native profiling support)                                  • Platform android-29, build-tools 29.0.1                                                                              • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java                                                 • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)                                          • All Android licenses accepted.                                                                                [√] Visual Studio - develop for Windows (Visual Studio Community 2017 15.9.14)                                             • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2017\Community                                       • Visual Studio Community 2017 version 15.9.28307.770                                                                                [!] Android Studio (version 3.4)                                                                                • Android Studio at C:\Program Files\Android\Android Studio                                                            X Flutter plugin not installed; this adds Flutter specific functionality.                                               X Dart plugin not installed; this adds Dart specific functionality.                                                     • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)                                                                                [√] VS Code (version 1.38.0)                                                                                • VS Code at C:\Users\csell\AppData\Local\Programs\Microsoft VS Code                                                   • Flutter extension version 3.4.1
[√] Connected device (1 available)                                                                                • Windows • Windows • windows-x64 • Microsoft Windows [Version 10.0.18362.295]
! Doctor found issues in 1 category.

I can reproduce in the FDE example app as long as the cursor isn't inside the window; there the app redraws the moment the cursor enters. That suggests that Flutter is getting the windows metrics event on maximize/restore; I wonder if the GL update isn't being propagated by the OS?

I can reproduce in the FDE example app as long as the cursor isn't inside the window; there the app redraws the moment the cursor enters. That suggests that Flutter is getting the windows metrics event on maximize/restore; I wonder if the GL update isn't being propagated by the OS?

Has this problem been followed up? If not, let me try to solve this problem.

@shoryukenn I haven't had a chance to investigate yet; it would be great if you could take a look!

@shoryukenn have you been able to investigate this?

I've seen at least one bug go by suggesting that maximize isn't redrawing correctly for web either. Needs investigation, but maybe this problem isn't entirely specific to Windows drawing. I wonder if it's something like a race condition between frame scheduling and the metrics event, and as such is sensitive to embedding details?

A similar problem occurs at launch for apps compiled in release mode.  Initial launch results in a black screen for a minimum of 5 seconds, resizing after that causes correct painting.

Was just pinged about this report on chat and a brain dump of some of the potential causes of these kinds of issues:
In the default configuration, Flutter renders into the window bound frame-buffer from a dedicated raster thread. This usually works out well on most platforms but some platforms do need coordination with their main threads for eventual presentation on the screen. Stuarts observation that that rendering continues when the cursor enters the window suggest that the main threads event loop perhaps needs to wake up before the rendered contents may be presented on screen. There are two ways to work around this. There may be a platform specific API that can be called from the raster thread that propagates these updates. If there is no such API, the Flutter engine can be configured such that Flutter renders from the platform thread directly (avoiding any synchronization issues but foregoing concurrency benefits). I believe the Mac embedder follows the second approach (I am not sure). Its plausible that the same issue manifests during resizing as well since Flutter needs to render frames after the resize is complete. If, after the resize, the main thread does not wake up, it is possible that contents rendered at the new size are not propagated to window server.
Another way to verify that frames are being rendered but not presented is to verify the frame traces in the Obvervatory timeline traces. You should see workloads on both UI and raster threads. This indicates that frames are being produced. The way the pipeline is constructed, it is very hard to stall it. So the usual issues on embedders usually have to deal with the embedder not delivering vsync events, or not propagating frames correctly for display.

Stuarts observation that that rendering continues when the cursor enters the window suggest that the main threads event loop perhaps needs to wake up before the rendered contents may be presented on screen.

I apparently forgot to update here, but running an animation makes rendering work even without mouse-movement, which suggested to me that it's not a runloop issue but a lost-draw issue.

I've also confirmed that the embedder.h "present" callback is being called once post-resize even when rendering is broken.

I apparently forgot to update here, but running an animation makes rendering work even without mouse-movement, which suggested to me that it's not a runloop issue but a lost-draw issue.

Hmm, by "lost-draw" do you mean the present callback was not called at all, or, it was called but the contents weren't updated?

I've also confirmed that the embedder.h "present" callback is being called once post-resize even when rendering is broken.

Hmm, the only thing that comes to mind is presentation from a background thread. As a quick hacky check, can you force rendering on the platform thread to see if the issue goes away (I am not sure if you are already)?

Hmm, by "lost-draw" do you mean the present callback was not called at all, or, it was called but the contents weren't updated?

The latter (but that's as much as I know at this point).

As a quick hacky check, can you force rendering on the platform thread to see if the issue goes away (I am not sure if you are already)?

I haven't. IIRC you said the mechanism that we used to do that for macOS wouldn't work on Windows?

IIRC you said the mechanism that we used to do that for macOS wouldn't work on Windows?

:/ I don't remember why I would have said that. Can't think of any limitations right now either. Do you remember the context?

Now that I think about it more, it may well have been before we'd wired up custom task runners in the desktop embeddings.

Ok, using the macOS thread configuration would be a quick way of checking if we are indeed running into issues due to rendering from a background thread. I looked over the implementation and it seemed like pretty straightforward usage of EGL but I am not sure if there are issues doing this with Angle.

Looked at the OSX custom_task_runner config
const FlutterCustomTaskRunners custom_task_runners = {
      .struct_size = sizeof(FlutterCustomTaskRunners),
      .platform_task_runner = &cocoa_task_runner_description,
      .render_task_runner = &cocoa_task_runner_description,
  };

and replicated this in windows by adding a render_task_runner:
FlutterCustomTaskRunners custom_task_runners = {};
custom_task_runners.struct_size = sizeof(FlutterCustomTaskRunners);
custom_task_runners.platform_task_runner = &platform_task_runner;
custom_task_runners.render_task_runner = &platform_task_runner;

No dice (everything ran has before).
I then did some poking around in the rasterization pipeline and instrumented a couple of methods with ETW.. you can clearly see the problem by looking at the traces:
debug: https://1drv.ms/u/s!AijXXv2M_HtCvqgPRqr293t4WGWacA?e=TVZxt3

In the debug case, although there is a trailing drawtosurface that is never displayed, a previous one is generated and gets picked up and presented.
release: https://1drv.ms/u/s!AijXXv2M_HtCvqgQOQ2erd_sb_Ni_g?e=CPY4D9

In the release case, there is never a presented issued after the drawtosurface.
This is exactly what happens in the window maximize case as well:
https://1drv.ms/u/s!AijXXv2M_HtCvqgR_8c-MIUnL4oVZg?e=7xQP2R

where there is a trailing drawtosurface that is never presented.  So at least we've confirmed that this is the same issue.

Digging further adding some more trace points, this is a failing case..  a little hard to read because of the ordering

Spent quite a lot of time digging in.  Here is an ETW trace for the working (debug) case:

In this case, Animator::BeginFrame calls Produce() on PipeLine:
>	flutter_windows.dll!flutter::Pipeline<flutter::LayerTree>::Produce() Line 108	C++
 	flutter_windows.dll!flutter::Animator::BeginFrame(fml::TimePoint frame_start_time, fml::TimePoint frame_target_time) Line 121	C++

and this happens ten different times.
For the broken (release mode) case Produce is only called one single time.

Animator::BeginFrame has been previously scheduled via the fml MessageLoop which I assume means by Dart.  Hence debugging this could require tracing on the Dart side as well to figure out why BeginFrame isn't being scheduled for AOT more than one time.  I have no clue how to do that and if it will work in Release / AOT mode.  I see a bunch of tracing infra in c++ that appears to call back into Dart so I'm guessing that Dart can see everything from both sides.  I'm not able to make further progress without guidance on how to trace Dart AOT.

#59738 is potentially the same issue on Linux, although it would need more debugging to be sure.
@chinmaygarde Can you suggest next steps based on the above (or recommend someone else who can)? I don't have experience with the internals of the drawing pipeline.

Although I don't have a fix yet, I do have a handle on what's going wrong and I can confirm that, on Windows at least, the release mode startup issue and the maximize issue are the same and both relate to how Flutter frame presentation is interacting with DirectX SwapChain resizing

Root cause established and PR with fix submitted.


Google Play Store initial release

Maybe a little premature, but just kicking off the TODO for initial release. Issues:

[x] #1
[x] #11
[x] #14
[x] #15
[ ] #10

Open to any input as always.
Post-release TODO:

[ ] Update README with link
[ ] Get friends to test it
[ ] [note to self - update old Big Red App info to link them to this (if they have Android, else say no longer supported)]

Okay, well, just finished #14. Please feel free to give any feedback! I am definitely willing to wait, accept pull requests, etc. to make it better before releasing this.
Anyway, #10 still needs to be decided on.
Something along the lines of What's Open Big Red does make sense, but I feel attached to keeping it a little simpler, which is why Big Red App feels nice and sweet. But again, I agree with the points raised in #10, so 100% open to thoughts/suggestions/etc. on this.

Okay added pull to refresh and the UI is pretty much ready to go. Now just for that name... Ha.

I now made a label for next-release, so this issue is no longer necessary to keep track of next-release things.


Allow alphabets and special characters in phone number

Describe your changes
As per title
Related Issues
Closes #181
Type of Change
Bugfix
Checklist

[x] Code follows project style guidelines
[x] I have performed a self-review of my code
[x] Code is commented where necessary, particularly in hard-to-understand areas
[x] Tests have been added/updated
[x] Documentation has been updated (if applicable)
[x] CI checks have passed

Screenshots (if applicable)

Closing because it will be counted under planned enhancements


Remove userId arguments in User Facade - Account Profile functions

See master ticker GH-1092
Remove the userId argument from these functions. Use the user id currentinstead inside the facade functions.

remove(userId: string): void {
updatePersonalDetails(username: string, userDetails: User): void {
updateEmail(uid: string, password: string, newUid: string): void {
updatePassword( userId: string, oldPassword: string, newPassword: string ): void {

We also need to refactor the components that use these functions and write down smoke test instructions for which feature we know we should look closer into for regression.

PR #2629

For tests:
Make regression tests on the update password functionality.
Also, validate that the userId in the occ calls used do not contain the user email, but the 'current' string instead.

Tested on dev17.

Update password now uses "current".

Update password still works as before. (Update password, Cancel, Save, Wrong original password, mismatch new passwords, back button, logout, can login with new password)


bugfix(libs/header/p2p): shuffle trusted peers before sending a request

Overview
We were using a weak random number generator that does not guarantee that we will get a really random peer within multiple attempts and we will request the same peer each time.
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

It's actually worth it. We are getting the same index each time in case of failed response, so we don't have a chance to request another peer one of them goes offline rn

Codecov Report

Merging #1903 (b817d34) into main (ffa3093) will decrease coverage by 0.04%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##             main    #1903      +/-   ##
==========================================
- Coverage   57.34%   57.31%   -0.04%
==========================================
  Files         242      243       +1
  Lines       16225    16144      -81
==========================================
- Hits         9305     9253      -52
+ Misses       5963     5946      -17
+ Partials      957      945      -12

Impacted Files
Coverage Δ

libs/header/p2p/exchange.go
79.12% <87.50%> (-0.49%)
:arrow_down:

... and 27 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Instructor material for slides

In order to expand the workshop, we will need a way to train new instructors.  This might include adding notes to the slides to highlight the main points of discussion or solutions to the interactive parts.  However, the participants receive the slides and can follow along during the workshop.  We do not want to reveal our solutions to them before they experiment on their own.
Copied from #14.

This can also include a timing guide that specifies approximately how long each portion of the workshop should take.

Closing this issue.  We now have an instructor notes page in the Carpentries style workshop as well as timing for each episode.


Improve the README for new users

We cannot expect that new users understand everything easily. We need to be more specific with the information in our README.

Hi @yFetz !
I have improved the README details.
Closed in d34c22114989d86d74475f0621396b32efbf0454!


Update send to class

add checkbox to send email  to only attending students of a past class.

functionality added


Dart2js: Trailing comma in asserts.

We have decided to allow trailing commas in asserts (an optional comma before the end-parenthesis) to match the trailing commas allowed in syntactically similar method calls.
Dart2js needs to implement this feature.

Its working on Dartpad - probably since it's on CFE now.


Side bar doesn't update when devices are unplugged

Describe the bug
When unplugging devices the side bar wont update and they will stay there
Expected behaviour
Device unplugged should disappear
System Information

OS Version: Windows 10 20H2 19042.844
App version: <IP_ADDRESS>

Thanks for this report. What kind of devices? Usb keys / mounted .iso / external hard drives..

I've only tried with my tab and my external HDD.

@josh-65 This issue should be resolved with #4192.


Update security-overview.md

Removing Internet reference
https://github.com/MicrosoftDocs/azure-docs/issues/28939#issuecomment-480714204

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Header shows the most recent project title

The header currently shows the project title as per the application, subsequent change from the signed agreement needs to be reflected in the header.
AC

[ ] When the SOW from a signed funding agreement is uploaded, the The Project Title should update to reflect the SOW in the: Analyst header, Analyst and applicant dashboard rows, assessment table
[ ] When SOW from a signed funding agreement is uploaded, the application form does NOT update, continue to show the project title from the application.
[ ] Use the latest un-archived version of the SOW from the signed funding agreement, not from the SOWs from Change Requests.

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @rafasdc

In new Jira now


Styling: emphasis of functions vs subheadings

Hello everybody,
while using the rust docs and other crates docs there is always one stylistic issue that is troubling me a bit. The subheadings in the documentation of each function are visually much more emphasized than the actual function. And that makes reading through the docs and for example searching for a function pretty hard because my eyes always jump to Examples Examples Examples Examples...
This screenshot is taken from zeal (offline doc browser, linux clone for dash), and demonstrates the issue quite nicely.

In the online docs it's slightly better, but still hard.
So I was wandering, is this actually intended? Or could we maybe improve the styles to visually put more emphasis on the functions?

Hi, thanks for reporting but this has nothing to do with docs.rs and a design choice made by rust-docs team and documentation creators of standard library. You can contact them in #rust-docs on IRC or you can open an issue report on rust-lang/rust repository instead.


Automatic Provider File Does not Pull Credentials from .zscaler-terraformer.yaml

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the library and it is still present.

zscaler-terraformer version
0.1.0
Expected outcome
When running zscaler-terraformer import, a Provider file named zpa-provider.tf or zia-provider.tf is automatically created. I expect it to create the file with both the provider and the credential information populated in my .zscaler-terraformer.yaml file
terraform {
    required_providers {
    zpa = {
      source  = "zscaler/zpa"
    }
  }
}

provider "zpa" {
  # Sensitive items removed
  zpa_client_id         = ""
  zpa_client_secret     = ""
  zpa_customer_id       = ""
  zpa_cloud             = "GOV"
}

Actual outcome
The automatically created provider file only has the provider defined like this:
terraform {
    required_providers {
    zpa = {
      source  = "zscaler/zpa"
    }
  }
}

I have populated .zscaler-terraformer.yaml in the default location with all of the necessary information for each service in what I believe to be the proper syntax, but it does not get pulled over when I run an import, requiring me to overwrite the file with the one I created manually and run the import again.
# Sensitive items removed
zpaClientID: ""
zpaClientSecret: ""
zpaCustomerID: ""
zpaCloud: "GOV"
ziaUsername: ""
ziaPassword: ""
ziaApiKey: ""
ziaCloud: "zscalergov"

Steps to reproduce

Create a .zscaler-terraformer.yaml file in the default location
Run zscaler-terraformer import on some or all resources
The command will complete but errors will be displayed in the terminal
Overwrite the automatically created Provider file with one created manually that has credentials defined
Run zscaler-terraformer import on some or all resources
The command will complete without error and resources will be imported

References
No response

Hi @drank-sinatra
Thanks for creating this issue.
I can confirm there's an issue with the way credentials are being read from the configuration file.
In the meantime, I encourage you to use environment variables instead in the following format which is more recommended and is the current working method.
# ZPA Configuration
export ZPA_CLIENT_ID=""
export ZPA_CLIENT_SECRET=""
export ZPA_CUSTOMER_ID=""
export ZPA_CLOUD="" --> Optional argument ["PRODUCTION", "BETA", "GOV", "PREVIEW"]

# ZIA Configuration
export ZIA_USERNAME=''
export ZIA_PASSWORD=''
export ZIA_API_KEY=''
export ZIA_CLOUD=--> Optional argument ["zscaler", "zscalerone", "zscalertwo", "zscalerthree", "zscloud", "zscalerbeta", "zscalergov"]

Thank you
Feel free to reach out via email as well<EMAIL_ADDRESS>;)

Ah, good to know! Thanks so much. :)

I actually just remembered that I had tried this before, and it fails to add my secret because there is a ' in it which ZSH interprets as a literal quote and thus breaks. I suppose I could get a new key though.

Hi @drank-sinatra
Would you mind reaching out offline? Also, I recommend that you delete the previous screenshot, as this information should be treated as private.
Feel free to reach out via email<EMAIL_ADDRESS>;)


Android: Deprecation warnings about SDCardDir and SDCardApplicationDir

Branch: 0.10.9
Just calling the following code:
import RNFetchBlob from 'react-native-fetch-blob';

const url = http://my.server.com/my/upload/API;
const headers = { Authorization: 'Bearer xxxxxxxxx' };
const body = RNFetchBlob.wrap('file:///storage/emulated/0/Android/data/some/local/file');
const res = await RNFetchBlob.fetch('POST', url, headers, body);

generates the following warnings in the Android logs:
W ReactNativeJS: SDCardDir as a constant is deprecated and will be removed in feature release. Use RNFetchBlob.android.getSDCardDir():Promise instead.
W ReactNativeJS: SDCardApplicationDir as a constant is deprecated and will be removed in feature release. Use RNFetchBlob.android.getSDCardApplicationDir():Promise instead. This variable can be empty on error in native code.

These warnings have been added by https://github.com/joltup/react-native-fetch-blob/commit/22fd32a but apparently there are still some occurrences of SDCardDir and SDCardApplicationDir in the code of the 0.10.9 branch.
I'm aware that the 0.10.9 branch isn't stable yet but it is intended to be released with a bunch of bug fixes so I believe that these warnings should be fixed before the release.
Thanks

@ataillefer  are you sure it's from react-native-fetch-blob itself, not from other package that uses it?

Hi,
Pretty sure yes.
Here's the output of yarn why react-native-fetch-blob:
yarn why react-native-fetch-blob
yarn why v1.6.0
[1/4] Why do we have the module "react-native-fetch-blob"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "react-native-fetch-blob"
info This module exists because it's specified in "dependencies".
info Disk size without dependencies: "32.49MB"
info Disk size with unique dependencies: "32.58MB"
info Disk size with transitive dependencies: "32.8MB"
info Number of shared dependencies: 8
Done in 1.04s.

Note that it states<EMAIL_ADDRESS>though I am relying on the latest commit of the 0.10.9 branch in my package.json:
"dependencies": {
  ...
  "react-native-fetch-blob": "git+https://github.com/joltup/react-native-fetch-blob#4add85726fab5dadc67f642840f9b64435329cb1",
  ...
},

(this is because the package.json of react-native-fetch-blob's 0.10.9 branch is versioned with 0.10.8.)
And the only place where we call RNFetchBlob in our app is the code mentioned above.
If I comment this code I don't get the warning anymore.
To reproduce, you only need to checkout the 0.10.9 branch and run some similar code.
In fact, I've realized that you don't even need to specify any parameter to the RNFetchBlob.fetch command, the minimum code required to reproduce is:
const res = await RNFetchBlob.fetch('POST', null, {}, null);

You're right, this getters are called when dirs object is instantiated just be importing fs.js file.
Will think about it @ataillefer .

This issue should be resolved by #77


Adds hive logging support

Which issue this PR addresses:
WI 15033872
What this PR does / why we need it:
Changes required on the ARO-RP side to enable hive logging support as per design defined in HIVE-1966 (this comment).
Work is still in progress on the Hive side. We will need to update Hive image once https://github.com/openshift/hive/pull/1828 merged.
Test plan for issue:
This code path must be a no-op for now. E2E should catch any regression.

Ready for review, I think

There are a lot of changes, but most of them are actually vendoring, tests and mocks
Hive image needs to be updated in hack/hive-generate-config.sh once https://github.com/openshift/hive/pull/1828 merged


feat: Allow users to register the same Meter multiple times without exception

Codecov Report

Merging #2017 into master will decrease coverage by 0.03%.
The diff coverage is 40%.

@@             Coverage Diff              @@
##             master    #2017      +/-   ##
============================================
- Coverage     83.11%   83.07%   -0.04%
- Complexity     2249     2251       +2
============================================
  Files           319      319
  Lines         10527    10536       +9
  Branches       1047     1048       +1
============================================
+ Hits           8749     8753       +4
- Misses         1438     1444       +6
+ Partials        340      339       -1

Impacted Files
Coverage Δ
Complexity Δ

...ensus/implcore/metrics/DerivedDoubleGaugeImpl.java
94.91% <0%> (-1.64%)
11 <0> (ø)

...us/implcore/metrics/DerivedLongCumulativeImpl.java
95.45% <0%> (-1.47%)
11 <0> (ø)

...ncensus/implcore/metrics/DoubleCumulativeImpl.java
93.33% <0%> (-1.27%)
16 <0> (ø)

...ncensus/implcore/metrics/DerivedLongGaugeImpl.java
91.52% <0%> (-1.58%)
10 <0> (ø)

...pencensus/implcore/metrics/LongCumulativeImpl.java
93.33% <0%> (-1.27%)
16 <0> (ø)

.../implcore/metrics/DerivedDoubleCumulativeImpl.java
95.45% <0%> (-1.47%)
11 <0> (ø)

...o/opencensus/implcore/metrics/DoubleGaugeImpl.java
94.44% <100%> (+0.07%)
17 <1> (+1)
:arrow_up:

.../io/opencensus/implcore/metrics/LongGaugeImpl.java
94.44% <100%> (+0.07%)
17 <1> (+1)
:arrow_up:

...pencensus/implcore/metrics/MetricRegistryImpl.java
71.71% <100%> (+0.28%)
7 <0> (ø)
:arrow_down:

...re/trace/export/InProcessSampledSpanStoreImpl.java
96.44% <0%> (+0.59%)
22% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

As discussed, please add test for
m1 = register.AddGauge("g1")
m2 = register.AddGauge("g1")

expect m1 and m2 to be the same.

@rghetia please review and approve when you get a chance, thank you :)


Warning: Undefined array key "producers" in /vendor\okstuff\phpnsq\src\phpnsq\Conn\Lookupd.php on line 48

ERROR:
Warning: Undefined array key "producers" in C:\xampp6\htdocs\api\vendor\okstuff\phpnsq\src\phpnsq\Conn\Lookupd.php on line 48
Warning: foreach() argument must be of type array|object, null given in C:\xampp6\htdocs\api\vendor\okstuff\phpnsq\src\phpnsq\Conn\Lookupd.php on line 48
Fatal error: Uncaught ValueError: array_rand(): Argument #1 ($array) cannot be empty in C:\xampp6\htdocs\api\vendor\okstuff\phpnsq\src\phpnsq\Conn\Pool.php:50 Stack trace: #0 C:\xampp6\htdocs\api\vendor\okstuff\phpnsq\src\phpnsq\Conn\Pool.php(50): array_rand(Array) #1 C:\xampp6\htdocs\api\vendor\okstuff\phpnsq\src\phpnsq\PhpNsq.php(57): OkStuff\PhpNsq\Conn\Pool->getConn() #2 C:\xampp6\htdocs\api\abc.php(12): OkStuff\PhpNsq\PhpNsq->publish('Hello nsq.') #3 {main} thrown in C:\xampp6\htdocs\api\vendor\okstuff\phpnsq\src\phpnsq\Conn\Pool.php on line 50
My Code is
require DIR . "/vendor/autoload.php";
use OkStuff\PhpNsq\PhpNsq;
$config = require DIR . '/vendor/okstuff/phpnsq/src/config/phpnsq.php';
$phpnsq = new PhpNsq($config);
//normal publish
$msg = $phpnsq->setTopic("sample_topic")->publish("Hello nsq.");
var_dump($msg);
exit();
//defered publish
$msg = $phpnsq->setTopic("sample_topic")->publishDefer("this is a defered message.", 10);
var_dump($msg);
//multiple publish
$messages = [
"Hello, I am nsq client",
"There are so many libraries developed by PHP",
"Oh, no, PHP is not so good and slowly",
];
$msg = $phpnsq->setTopic("sample_topic")->publishMulti(...$messages);
var_dump($msg);
Please help to resolve the issue. Thanks

Maybe your nsq lookupd server is not ready or your nsq lookupd server configuration is wrong.


Allow Generic automap to tolerate null values in json configs

This is not for requesting support for new games/applications
To do this you should go to https://github.com/CubeCoders/AMPTemplates and first attempt to build a configuration yourself - otherwise you can request a template from this repo.
Feature Request
Feature Information:

Vintage Story has a default serverconfig.json file that is generated on first server start, which is used to configure various server settings.
Some settings are set to null. If any of those settings are configured in AMP's configmanifest.json, AMP throws an error, complaining that the values cannot be null. Presumably when AMP reads the settings, it does not like the null value.
Ideally AMP would still be able to read the settings, and then write whatever default value/value is set via configmanifest.json.
I've looked at the option of supplying a serverconfig.json file as an update stage with the null values changed to some actual default value, but a number of aspects of the config file are generated by the server itself (mod paths, world configs) and are specific to the particular install, and so it is not feasible to supply a generic config file.
I confirm:

[x] that I have searched for an existing feature request matching the description.

[19:08:33] [Core:admin Error]     : ArgumentNullException
[19:08:33] [Core:admin Error]     : [0] (ArgumentNullException) : Value cannot be null.
Parameter name: o
[19:08:33] [Core:admin Error]     :   at Newtonsoft.Json.Linq.JToken.FromObjectInternal (Object o, Newtonsoft.Json.JsonSerializer jsonSerializer)
  at Newtonsoft.Json.Linq.JToken.FromObject (Object o)
  at GenericModule.ModuleMain.MergeJSON (String finalPath, GenericModule.MetaConfigFile fileInfo)
  at GenericModule.ModuleMain.MergeConfigFile (String finalPath, GenericModule.MetaConfigFile fileInfo)
  at GenericModule.ModuleMain.WriteMetaconfigs ()
  at GenericModule.ModuleMain.SaveChanges (String key, String value)
  at GenericModule.GenericApp.DoAppStartup (Boolean IsUpdating)
  at GenericModule.GenericApp.Start ()

What would be the expected behaviour? Just an empty value?

Whatever value the relevant setting is set to write.
Eg a starting node in the json file might be "Password": null,. (This is an actual example.)
The AMP setting in configmanifest.json is configured to write a text value to that node.
So the node should be populated with: "Password": "abc123",.
Could be other examples like "Port": null -> "Port": 7777.
Basically, the nodes should be able to written as per normal json conventions.

How does VintageStory tolerate those values that are null being straight up missing from the config file? AMP would have a hard time dealing with null values because there's no way to differentiate null from empty string in the web interface.

I think you are really missing the point. I will try to explain further when I get time. In no circumstances do I want or need null in the UI

Would just like to express my desire to have this resolved.  Server defaults to 1.16.5, and will not update to the new stable, 1.18.12.  I'm running on linux, but it is trying to launch the .exe instead of the .sh
Does resolving this issue require action on the dev's part?  I know they have expressed willingness to work with your team to have the server better intergrated with AMP, but it was two years ago.

If you are referring specifically to Vintage Story:

from v 1.18.8, the devs changed how the server is downloaded and run
as a result, the template was split in AMP: for v 1.18.8+, there is a new template
you need to update your templates
the question of versions etc is entirely unrelated to this GH issue

Right after posting this, I looked more closely at the commits, and noticed that I was on 2.4.4, and not 2.4.5 of AMP.  You have indeed fixed my problem already. I thought I would have to manually download a special template, but I now have a better understanding of how AMP works  I came back to delete my comment, but you've already responded, which I appreciate greatly.
I'm extremely grateful for everything you do, which makes my server hosting so simple and easy.

@PhonicUK The  issue here is if you have a json file that already contains a null value amp will not be able to change that setting, it will error because it's a null value.
Example json
{"name": "someName","version": null }
If you try making a generic template for AMP with just those two config options, none of them will be changed because of that null value
e.g if you set name="Some other name" and version=5
The expected behavior is for the json to become
{"name": "Some other name","version": 5 }
However, what actually happens is an error and nothing modified


Race condition in worker.shutdown() in a cluster environment

So this took me some time and hair-pulling to debug.
Apparently when you have more than one worker process for the same queue, a race condition can prevent some of the workers to gracefully shut down, forcing the whole thing to wait for a timeout.
Some of the jobs I'm processing may take longer than an hour, which forces me to adjust a timeout accordingly, thus making this bug especially painful as it triggers even when the queue is empty.
Here's what's going on:

Let's say we start with a completely empty queue.
Process A does queue.shutdown() which calls worker.shutdown() for every worker.
Process B does the same.
Process A is almost done, hits this line, adding an item to jobs list.
Process B hits this line, then this line, setting self.job = true, then yielding to event loop while waiting for ZPOP I/O to complete (next line).
At this time Process B hits this line, so assumes there's a job running and subscribes to relevant events to be notified when the job is completed or failed.
In reality, once ZPOP I/O is done, self.job is reset to null on this line, but worker.shutdown() is not notified about it, so it waits for the whole timeout duration.

My (ugly) workaround was to add the following piece of code right between these two lines:
if (this.job === true) {
    return setTimeout(self.shutdown.bind(self, fn, timeout), 10);
}

But you probably can come up with a better fix.

thank you @laggyluke for the details, I'll check it...

Can you test/confirm that removing this line https://github.com/LearnBoost/kue/blob/90d902b74f87edabb8c0e6055ebf9ee50dbf78b2/lib/queue/worker.js#L282 prevents from this to happen !?

Yes, I can confirm that I can't reproduce this bug when that line is commented out.
Though it looks like this won't fix the underlying race condition, just make it more rare / difficult to trigger.
I thought about adding a 'job idle' event that will fire when zpop returns nothing, so that shutdown could subscribe to it as well, but it still looks a bit hackish... Anyway, I'm no expert, you should probably know better :)

@laggyluke  Could you please confirm this is not happening any more!?

I've tried installing kue from master, but unfortunately got the following error during workers shutdown:
TypeError: undefined is not a function
  at fn (/path/to/project/node_modules/kue/lib/kue.js:327:20)
  at _fn (/path/to/project/node_modules/kue/lib/queue/worker.js:301:9)
  at Worker.shutdown (/path/to/project/node_modules/kue/lib/queue/worker.js:309:16)
  at /path/to/project/node_modules/kue/lib/kue.js:346:22
  at Array.forEach (native)
  at Queue.shutdown (/path/to/project/node_modules/kue/lib/kue.js:344:20)
  [...]

I'll try to debug it more thoroughly tomorrow.

Have you read the history changes and latest docs?
we have some API breaking changes from 0.8.x to 0.9

Thanks, you're right - I've updated my code for the new API and it worked just fine.
I can confirm that this issue is now resolved.
Thanks again!

happy to hear that :)


mapping Rights (of Image or Object)

This is all wrong.
  ?image crm:P104_is_subject_to ?right .
  ?right a crm:E30_Right .
  ?image crm:P67i_is_referred_to_by ?rights_statement_class .
  ?rights_statement_class a crm:E33_Linguistic_Object ;
    crm:P2_has_type <http://vocab.getty.edu/aat/300055547> ;
    rdf:value ?rights_statement .

You say there's some Right over the image, but provide no info about it; then say there's some Linguistic Object but it;s not related to the right. Should be like this:
  ?image crm:P104_is_subject_to ?right .
  ?right a crm:E30_Right
    # crm:P2_has_type # pick a license from creativecommons.org or rightsstatements.org
    crm:P3_has_note ?rights_statement .

You're right that it's wrong ... but not because the model is, because this should be two separate features.
?image is_subject_to <license_uri> .
is one half, and no need to associate any more information with the license URI.
The linguistic object is a rights statement, rather than a license and follows the linguistic object + rdf:value pattern.
Propose splitting the description into these two distinct concepts.

I'm fine with splitting them—I think it's an abstraction problem in the review tool, because they're really  about an image, not about an object.  Should I create a new section for Images (like we have for MMOs and Actors?)

A rights statement is absolutely certainly crm:E30_Right.
How about this:
<image> crm:P104_is_subject_to <image/rights>.
<image/rights> a crm:E30_Right;
   crm:P3_has_note "<rights_statement>";
   crmx:P3_credit_line "<credit_line>";
   P148 has component http://rightsstatements.org/license_url.

Optionally, include some RDF info about http://rightsstatements.org/license_url from their site.
The Credit Line is closely related to rights, so we also put it there.
crmx:P3_credit_line is a CRMX ext that I defined for CONA (Rob has access)

they're really about an image, not about an object

Yes, in this particular case. Objects may and often have different rights from images. If there's info about Object rights, it should be mapped separately, but in exactly the same way as for Images.
This bug is about keeping <rights_statement> outside of crm:E30_Right. If a <rights_statement> is not E30_Right then pray tell, what is?

No, a rights statement could be "We have not assessed the copyright status of this image", as per http://rightsstatements.org/page/CNE/1.0/?language=en.
That is absolutely not an E30_Right, poorly defined in CRM as "This class comprises legal privileges concerning material and immaterial things or their derivatives." as no legal privileges are being claimed. Quite the opposite, the statement is that the organization explicitly does not know what legal privileges are claimed.
It is not a license or a legal privilege, it is a statement about the (potential lack of) knowledge of the rights status of the resource.

Seems to me CNE should be omitted, following the semweb best practice "you don't need to say you don't know".
I'm not sure, do you propose to use some rightstatements URL or not? Could you please write some turtle here?

It is explicit that the organization has not assessed copyright for this object. But the same would apply to any of the other non license rights statements. They are not legal privileges, per E30, they're statements about the status of the resource according to the issuer.
_:x a ManMadeObject ;
  refered_to_by [
    a LinguisticObject ;
    rdf:value "rights statement text goes here" ;
    classified_as <aat:rights> ]
  dct:rights <rightsstatements.org/whatever> .

Also, the rights model in CRM (E72, E30, P104, P105, P75) is just broken when there are multiple Rights and multiple Actors that hold them.  You would need multiple E72s, one per Right/Actor combination. As such it could not be associated directly with the object ... and then you need some way to relate the E72s to the Man Made Object ... which could be composed of ... but in some weird non physical way.

Issue raised for CRM:

http://lists.ics.forth.gr/pipermail/crm-sig/2017-February/002892.html

You would need multiple E72s, one per Right/Actor combination.

Yes, you do. Eg (adapting your JSONLD above):
<object/31> crm:P104_is_subject_to <Right/0>, <Right/1>.

<Right/0> a crm:E30_Right;
  crm:P75i_is_possessed_by <actor/6>;
  rdfs:label "Ownership Right by Owner of Object".

<Right/1> a crm:E30_Right;
  crm:P75i_is_possessed_by <actor/7>;
  "Copyright by Holder of Object".

then you need some way to relate the E72s to the Man Made Object ...

The relation is crm:P104_is_subject_to

As such it could not be associated directly with the object

What "could not be associated directly"? If you mean a link actor-object, that's P105. However, P105 is a short-cut that provides less info than the long-path: "P105 right held by (has right on) is a shortcut of the fully developed path from E72 Legal Object through P104 is subject to (applies to), E30 Right, P75 possesses (is possessed by) to E39 Actor."
So you don't need to use P105.

which could be composed of ... but in some weird non physical way.

Above I've suggested to use crm:P148_has_component to link the specific E30_Right instance to the generic "right type" on RightsStatements.org.
You suggest to use P2 which is also possible, but imho P148 is more accurate: we're saying that the specific Right, being a Propositional Object, is composed of a generic "right type" plus extra info.
We can also state that an object doesn't have its rights evaluated because crm:P75i_is_possessed_by is not mandatory in E30_Right:
<object/32> crm:P104_is_subject_to <right/13>.
<right/13> a crm:E30_Right; crm:P148_has_component <http://rightsstatements.org/vocab/CNE/1.0/>.

<http://rightsstatements.org/vocab/CNE/1.0/> a crm:E30_Right;
  rdfs:label "COPYRIGHT NOT EVALUATED".

Of course, in this case making a local Rights node is unnecessary, so we could simplify to:
<object/32> crm:P104_is_subject_to <http://rightsstatements.org/vocab/CNE/1.0/>.

<http://rightsstatements.org/vocab/CNE/1.0/> a crm:E30_Right;
  rdfs:label "COPYRIGHT NOT EVALUATED".

And this shows why "rights types" should be treated as E30_Right not E55_Type, and why P148_has_component is better than P2.

the rights model in CRM is just broken

I'm not sure what fault you find with it, please elaborate


Publish new version to npm (w/ new package name?)

Packages are published https://github.com/react-page/react-page/issues/684#issuecomment-498795371


[GEP-18] Adapt service-account-key secret to new secrets manager

How to categorize this PR?

/area security
/kind enhancement
/merge squash
What this PR does / why we need it:
This PR adapts the service-account-key secret to new secrets manager.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/3292#issuecomment-1036058890
/invite @timebertt @BeckerMax
Release note:

NONE

After reconciling an existing shoot with the change, the service-account-key secret was replaced by:
apiVersion: v1
data:
  id_rsa: ...
immutable: true
kind: Secret
metadata:
  finalizers:
  - gardenlet.gardener.cloud/secret-controller
  labels:
    checksum-of-config: "4940742756935928387"
    last-rotation-initiation-time: ""
    managed-by: secrets-manager
    manager-identity: gardenlet
    name: service-account-key
    persist: "true"
  name: service-account-key-c37a87f6
  namespace: shoot--dev--i500152-gcp
  ...
type: Opaque

The id_rsa is the same, the secret is immutable and has the new secrets manager labels, and is renamed to service-account-key-c37a87f6. Why does it also have a finalizer (it wasn't there before)?

Thanks for the review!
The finalizer exists because the secret is persisted in the ShootState (added by this controller).

The finalizer exists because the secret is persisted in the ShootState (added by this controller).

It wasn't persisted in the ShootState before, why is it persisted there now?

The finalizer exists because the secret is persisted in the ShootState (added by this controller).

It wasn't persisted in the ShootState before, why is it persisted there now?

The old service-account-key was also persisted in the ShootState before, for sure.


Add relationships and attributes, update tests

Opening this PR upon your request. Please, note that this PR needs to be refined since certain tests fail.

Once again, thank you for your efforts here. I based my implementation of this in #62 based on what you wrote here. Instead of a defaultValue I put in an optional getDefault function, where you can pass () => 'myDefaultValue' if it's a constant value. I'll probably add the AttributeDescriptor in, too - it'll be cleaner than my current code.
Some differences: if you pass an object with keys that are not defined as fields, an error is raised. I think this will catch bugs early for a lot of people.
With the non-relationship attributes, it should be easier for people to build extra functionality and validation on top of Redux-ORM -- something similar to redux-orm-proptypes, which needs some updating after React deprecated those APIs. I think this is a good step forward.

@tommikaikkonen thanks! Agreed with all of the above.

Closing since this was incorporated into #62

for validation i'm using this:
https://github.com/yiminghe/async-validator

maybe it will help

@tommikaikkonen : Side question - what do you mean by "React deprecated those APIs"?  If you're talking about React.PropTypes, the React team is definitely encouraging the use of Flow overall, but PropTypes aren't actually "deprecated" that I know of.

@markerikson https://facebook.github.io/react/warnings/dont-call-proptypes.html


add generateCertificate, fixes #41

@KaptenJansson @alvestrand
Not sure if I want to do the same for FF... maybe we should just drop support for versions < 38? Trivial to add though. cc @jan-ivar

Nice work! ;)
Maybe we should look over all version checks? Not sure what versions we have committed to support, be aware of Firefox ESR though which lags behind for a while, I think it's still 38.
Also having a test for this would be nice, otherwise LGTM.

That was quick :-)
Travis' hiccups seem to be a problem with fetching external content.
Should we add a function that throws a "notSupported" error when the function is not present?

@alvestrand code that wants to use it will have to check if that is a function anyway (if anyone is using it at all)

Filed #159 WRT to checking versions just to make sure we do not forget.

Is this only available in M49 when setting --enable-experimental-web-platform-features?
Should we do that for beta and canary?

LGTM


Crate documentation not up to date

WIndows build macro has probably been deprecated but there is no indication given on windows crate version 0.35.0. Please update the crate docs so that it is easier to find an alternative on the docs. Currently I am trying to search online and getting nowhere.
https://docs.rs/windows/0.6.0/windows/macro.build.html

Code generation has been pulled out of the windows crate and moved into the windows-bindgen crate. There's documentation, too, even if it doesn't explain a whole lot at this time. The bindings tool implementation is more educational in this respect.

Crate documentation can be found here:

windows
windows-sys

The build macro is no longer needed as these crates are pre-generated.


Wiki is full of duplicated entries and broken links.

The last commit of the wiki left most of its pages chock full of duplicates and incorrect links. I cleaned it up some, but someone should probably write a proper script to generate those files instead of whatever bone-headed method was used last time.

I dunno how the hell to edit the wiki or pull request my changes.  If you care about the wiki not being all in shambles, just replace what's there with what's on my version: https://github.com/destenson/ActiveState--code/tree/wiki

Thanks for the issue report - the bug in the auto-generation script has been fixed and wiki updated. Closing this issue.


XML getElementsByTagName returns Node

Hi,
I understand all concerns around HTML/SVG elements with querySelector(), etc. But why method which should return Element cannot even return Element but returns Node? Do you think it's possible to query processing instructing with getElementsByTagName()? I know it's NodeList returned by that method, but NodeList does not mean that it always should contains only Node class, not its subclasses.
This code won't work:
let xml: XMLDocument;
let element = xml.getElementsByTagName('test')[0];

element.getAttribute('attr');

Also, fine thing here is that Node has method hasAttributes().

As per the W3C DOM Level 3, NodeList is an array-like structure containing items of Node.  And Node does not contain getAttribute.
The easiest way to deal with this, because you know something that can't be derived from the code, is to use a cast:
let xml: XMLDocument;
let element = <Element> xml.getElementsByTagName('test')[0];

element.getAttribute('attr'); /* no error */

@kitsonk Oh, man, I know how it's per spec, but I am a bit tired of such answers here. It's not a question how to solve this problem, I understand how to cast types. Problem is that getElementsByTagName() cannot return anything than Element, am I wrong?
And if you are so spec funs, why then getElementsByTagName('a') in HTML document returns NodeListOf<HTMLAnchorElement>?
Plus do not miss this:

Also, fine thing here is that Node has method hasAttributes().

As per the W3C DOM Level 3, NodeList is an array-like structure containing items of Node. And Node does not contain getAttribute.

And please, as per spec, Element inherits from Node, right? I believe it's true because this code returns true in browsers:
document.getElementsByTagName('a')[0] instanceof Node &&
document.getElementsByTagName('a')[0] instanceof Element

So returning Element won't be any incorrect per-spec, if you always like to be per-spec (but you are not of course in some other cases, but who cares).

Oh, man, I know how it's per spec,  but I am a bit tired of such answers here.

If you think I am affiliated with TypeScript, you are wrong.  I am trying to point out though that your expectations do not align to the specs, so I am surprised you think that TypeScript shouldn't follow the specs and do what you think it should do, versus what the spec says.  I even gave you a working piece of code that gets around the issue.  So to be honest, I am "tired of such" attitude for just trying to help.
Why do you think TypeScript should magically ignore the spec for you?
Yes, you are right that Element inherits from Node.  But Node !== Element, just because at runtime, in 99% percent of the cases, it only returns something an Element doesn't mean that it is always the case.  In fact, you are  using the one thing a lot of other developers argue isn't "realistic" in that you are using an XMLDocument, when others argue Document is just fine.
There are several other issues that talk about the usability of the lib.d.ts in practice and the TypeScript team have indicated they are thinking about the right way to deal with it.  I am sure if you have bright ideas of how to make it work, they would be glad to hear from you.
As far as hasAttributes() and why Node has it, but not getAttribute, you should be mad at the W3C, because that is  as per the spec.  There is a lot in the DOM that I consider awkward and challenging. Maybe if you e-mail them, they will change the spec.  Let me know how you get on with that.

Note that the DOM spec is written in a language called WebIDL. The mapping of WebIDL to ECMAScript is defined in WebIDL spec, but is undefined for other languages. So it is up to TS to decide how to map from DOM spec. Also note that some WebIDL features are not possible in TS currently, such as overriding a member in a sub interface.
As to getElementsByTagName(), the spec says "Returns a NodeList of all the Elements ...", so it is perfectly safe and logical to return a NodeListOf<Element> in TS.

@duanyao that is a fair point about getElementsByTagName().  Thanks for taking the time to look up information and reference it.
As far as the WebIDL, if I understand correctly, lib.d.ts is auto-generated from the internal implementation of IE's ECMAScript engine, which is based on Chakra's implementation of the DOM spec.  Ergo, I suspect Chakra is returning a NodeListOf<Node>.  Obviously @RyanCavanaugh felt this was a bug so hopefully the team will be willing to vary the lib.d.ts for usability.

@kitsonk AFIW NodeListOf<N> and related things are manual tweaks on top of auto-generated lib.d.ts, and lib.d.ts is auto-generated from WebIDL files of IE 11 (those files are also used to generated C++ bindings of DOM objects).

@kitsonk You know, after your answers here I really do not want to report any bugs here to TypeScript. If you are tired here, then please, do not answer here, it's simple. You was wrong here but was arguing with such rage like only you can be right.
It's so obvious that getElementsByTagName returns Elements. Treating the spec so literally it's like junior Police man (or any such position, like moderator somewhere) treats rules literally word-to-word. It's of course wrong, their job is to be people, so please, be people here.

If you don't mind, I'd like to leave this open so that we can fix the bug?

@zhengbli can you take a look.

I agree that it is safe to assume that getElementsByTagName() returns only NodeList<Element>. And similar functions include getElementsByClassName, getElementsByName and getElementsByTagNameNS.

and NodeSelector.querySelectorAll as well.

I agree this should not be throwing an error.  Example code
No error thrown because it is ById which is HtmlElement and defined correctly in lib.d.ts
document.getElementById('left-aside-wrapper')[0].classList.toggle('isOpen');
Error thrown Property 'classList' does not exist on type 'Node'.
document.getElementsByClassName('left-aside-wrapper'[0].classList.toggle('isOpen');
I understand this is because it is not defined in the lib.d.ts file but this is the is related to the issue from OP.

@NekR give the latest library a test and let us know if the issue has been solved.

@mhegazy it seems to work fine. Thanks!


Object Detection Images directory layout

Hi,
I'm trying to run Object Detection on a custom images dataset.
I tried to mimics Tiny bike example.
What is the expected images directory layout ?
For Tiny bike example, the root directory is like :
Annotations*.xml
ImageSet\Main\trainval.txt
ImageSet\Main\test.txt
JPEGImages*.jpg
Do you support PNG files ?
I'm using PNG images. I converted them to JPG using mogrify.

@zhreshold Could you take a look?

@montardon
The structure is
├── Annotations
├── ImageSets
│   ├── Main
│   │   ├── test.txt
│   │   └── trainval.txt
│   └── Segmentation
│       ├── test.txt
│       └── trainval.txt
├── JPEGImages

as for now, only .jpg files are supported in such voc format. In upcoming https://github.com/awslabs/autogluon/pull/733, the major image extensions will be supported.


document coercion rules in Zed language

This text was removed from the ZNG spec as it belongs somewhere in the language docs:
## Appendix B. Recommended Type Coercion Rules

> TBD: it might be better to put this in the Zed language docs

While outside the scope of the ZNG format specification, we include here
some suggested rules for converting types when mixed-type operations occur,
e.g., adding an uint32 field to an int32 fields or aggregating a stream of
mixed-type numeric values in a sum operator.

The age old question is "does unsigned(-1) equal unsigned(maxint) and thus
that signed -1 is larger than unsigned 1 in a coerced comparison?"
The standard SQL specification goes so far as to avoid unsigned types altogether
to avoid this confusion.  However, since unsigned types are prevalent
in the real world, and we want ZNG to be a reliable and complete language-independent
model for communicating structured data, ZNG embraces the unsigned type.

Given the dynamic typing nature of ZNG streams (e.g., x in one record might
be a uint8, in another an int64, and in still another, a string), type coercion
is important for ergonomic use, and implementations are thus encouraged
to handle mixed-type operations robustly.

For systems that perform analytics directly on ZNG, the following coercion
patterns are recommend for logical comparisons of numbers, arithmetic operations,
or streaming aggregations over numbers:
* For float32 and float64, the float32 is converted to float64.
* For float32 and any integer type, the integer is converted to float32
and any loss of precision causes no error.
* For float64 and any integer type, the integer is converted to float64
and any loss of precision causes no error.
* For integers of same signed-ness but different widths, the smaller width
type is converted to the wider type.
* For any signed and unsigned integers smaller than 64 bits, the unsigned value
is converted to the corresponding signed type if possible, and otherwise,
both are converted to the widest signed type that will allow conversion of
the unsigned value unless the unsigned value cannot be converted,
in which case an overflow error occurs.   e.g., uint8(255) and int8(-1), are
converted to int16(255) and int16(-1), but uint64(2^32) and any signed value
will result in overflow.
* For a time or duration with a number, automatic coercion is not performed
and casts or conversion functions should be used.
* For a string with number, automatic coercion is not performed
and casts or conversion functions should be used.

Also,
* numeric constants should be int64 or float64 unless cast, which means
comparisons with constants will generally be coerced to these types and results
of mathematical operations with constants will be promoted as well;
* times and durations may be added, resulting in a time;
* times may be subtracted, resulting in a duration; and,
* a "plus" operator applied to two strings, implies concatenation,
but a "plus" applied to a string and a non-string is a type mismatch and casts
or conversion functions should be used.

I can see this is a duplicate of #3706. Closing.


fix(nginx) Adjusting nginx proxy send time

https://github.com/longhorn/longhorn/issues/2937
image: wangsiye/longhorn-ui:d6e1099
Signed-off-by: Siye Wang<EMAIL_ADDRESS>

Let's close this first because the original question resolved and increasing the timeout is not what we pursue at the moment.


"nlinum-hl-mode is deprecated"

Hello again. I was investigating some lag caused by nlinum. Disabling nlinum fixed the lag. I re-enabled it and tried disabling nlinum-hl-mode.  Running M-x nlinum-hl-mode I saw the following:
nlinum-hl-mode is deprecated; use (setq nlinum-highlight-current-line t) instead

Once my body had recovered from the shock and I returned to consciousness I quickly rushed here to report the issue. I figure the deprecation message is due to this (from the readme):
nlinum 1.7 is now available on ELPA and offers current-line highlighting, so this plugin has changed its focus.

I know we've had our differences in the past, Mr. Meatball, but please... pl... p...

Looking at the readme again, I think I misunderstood how to use this package. Sorry... :sob:


Tag 1.1.7 release

Your Question
On Play Store release 1.1.7 is available, however this is not tagged on this repo.
Can you tag 1.1.7 properly?
Regards
Andrea

Hello @ilGimmy

On Play Store release 1.1.7 is available, however this is not tagged on this repo.

There is no 1.1.7 tag for app/UI source code because there is no diff with 1.1.6 tag.
VerificaC19 releases 1.1.6 & 1.1.7 for Android share indeed the same tag code for :

App/UI (release/1.1.6)

DGC-SDK (release/1.0.2)

Such releases differ only in the EU DCC Core Decoder (main) module code = 1.1.7 uses indeed the same EU DCC code used by 1.1.6 (updated until SEP 28) + 1 additional commit for EU DCC Decoder - in order to fix a minor Base45 decoding bug in the EU DCC decoder.


nmstatectl: Control the log level

Control the log level through an argument (--log-level) or an environment
variable (NMSTATE_LOG_LEVEL).
Usage example:
nmstatectl --log-level=INFO edit eth1
NMSTATE_LOG_LEVEL=INFO nmstatectl edit eth1

Just noticed, that there are no tests included in this PR.

Just noticed, that there are no tests included in this PR.

This is challenging, looking into this.

Tests added.


Restore from sqlite file into an in memory database for testing

Closes https://github.com/Actyx/Cosmos/issues/5725

I mean, basically writing the issue took longer than implementing it I suppose ;-)