ImageTextureEntry can't wait on the fence on Android < 33

What package does this bug report belong to?
camera
What target platforms are you seeing this bug on?
Android
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
  async:
    dependency: transitive
    description:
      name: async
      sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
      url: "https://pub.dev"
    source: hosted
    version: "2.11.0"
  boolean_selector:
    dependency: transitive
    description:
      name: boolean_selector
      sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  camera:
    dependency: "direct main"
    description:
      name: camera
      sha256: dfa8fc5a1adaeb95e7a54d86a5bd56f4bb0e035515354c8ac6d262e35cec2ec8
      url: "https://pub.dev"
    source: hosted
    version: "0.10.6"
  camera_android:
    dependency: transitive
    description:
      name: camera_android
      sha256: ca42d500c1b58c1ab90ef819909b4de769bcb388a643b692a639c36954a3dc78
      url: "https://pub.dev"
    source: hosted
    version: "0.10.9+5"
  camera_avfoundation:
    dependency: transitive
    description:
      name: camera_avfoundation
      sha256: "7d021e8cd30d9b71b8b92b4ad669e80af432d722d18d6aac338572754a786c15"
      url: "https://pub.dev"
    source: hosted
    version: "0.9.16"
  camera_platform_interface:
    dependency: transitive
    description:
      name: camera_platform_interface
      sha256: a250314a48ea337b35909a4c9d5416a208d736dcb01d0b02c6af122be66660b0
      url: "https://pub.dev"
    source: hosted
    version: "2.7.4"
  camera_web:
    dependency: transitive
    description:
      name: camera_web
      sha256: "9e9aba2fbab77ce2472924196ff8ac4dd8f9126c4f9a3096171cd1d870d6b26c"
      url: "https://pub.dev"
    source: hosted
    version: "0.3.3"
  characters:
    dependency: transitive
    description:
      name: characters
      sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  clock:
    dependency: transitive
    description:
      name: clock
      sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
      url: "https://pub.dev"
    source: hosted
    version: "1.1.1"
  collection:
    dependency: transitive
    description:
      name: collection
      sha256: ee67cb0715911d28db6bf4af1026078bd6f0128b07a5f66fb2ed94ec6783c09a
      url: "https://pub.dev"
    source: hosted
    version: "1.18.0"
  cross_file:
    dependency: transitive
    description:
      name: cross_file
      sha256: "55d7b444feb71301ef6b8838dbc1ae02e63dd48c8773f3810ff53bb1e2945b32"
      url: "https://pub.dev"
    source: hosted
    version: "0.3.4+1"
  cupertino_icons:
    dependency: "direct main"
    description:
      name: cupertino_icons
      sha256: ba631d1c7f7bef6b729a622b7b752645a2d076dba9976925b8f25725a30e1ee6
      url: "https://pub.dev"
    source: hosted
    version: "1.0.8"
  fake_async:
    dependency: transitive
    description:
      name: fake_async
      sha256: "511392330127add0b769b75a987850d136345d9227c6b94c96a04cf4a391bf78"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.1"
  ffi:
    dependency: transitive
    description:
      name: ffi
      sha256: "493f37e7df1804778ff3a53bd691d8692ddf69702cf4c1c1096a2e41b4779e21"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  flutter:
    dependency: "direct main"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_lints:
    dependency: "direct dev"
    description:
      name: flutter_lints
      sha256: "9e8c3858111da373efc5aa341de011d9bd23e2c5c5e0c62bccf32438e192d7b1"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.2"
  flutter_plugin_android_lifecycle:
    dependency: transitive
    description:
      name: flutter_plugin_android_lifecycle
      sha256: c6b0b4c05c458e1c01ad9bcc14041dd7b1f6783d487be4386f793f47a8a4d03e
      url: "https://pub.dev"
    source: hosted
    version: "2.0.20"
  flutter_test:
    dependency: "direct dev"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_web_plugins:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.0"
  leak_tracker:
    dependency: transitive
    description:
      name: leak_tracker
      sha256: "7f0df31977cb2c0b88585095d168e689669a2cc9b97c309665e3386f3e9d341a"
      url: "https://pub.dev"
    source: hosted
    version: "10.0.4"
  leak_tracker_flutter_testing:
    dependency: transitive
    description:
      name: leak_tracker_flutter_testing
      sha256: "06e98f569d004c1315b991ded39924b21af84cf14cc94791b8aea337d25b57f8"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.3"
  leak_tracker_testing:
    dependency: transitive
    description:
      name: leak_tracker_testing
      sha256: "6ba465d5d76e67ddf503e1161d1f4a6bc42306f9d66ca1e8f079a47290fb06d3"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.1"
  lints:
    dependency: transitive
    description:
      name: lints
      sha256: cbf8d4b858bb0134ef3ef87841abdf8d63bfc255c266b7bf6b39daa1085c4290
      url: "https://pub.dev"
    source: hosted
    version: "3.0.0"
  matcher:
    dependency: transitive
    description:
      name: matcher
      sha256: d2323aa2060500f906aa31a895b4030b6da3ebdcc5619d14ce1aada65cd161cb
      url: "https://pub.dev"
    source: hosted
    version: "0.12.16+1"
  material_color_utilities:
    dependency: transitive
    description:
      name: material_color_utilities
      sha256: "0e0a020085b65b6083975e499759762399b4475f766c21668c4ecca34ea74e5a"
      url: "https://pub.dev"
    source: hosted
    version: "0.8.0"
  meta:
    dependency: transitive
    description:
      name: meta
      sha256: "7687075e408b093f36e6bbf6c91878cc0d4cd10f409506f7bc996f68220b9136"
      url: "https://pub.dev"
    source: hosted
    version: "1.12.0"
  multi_image_capture:
    dependency: "direct main"
    description:
      name: multi_image_capture
      sha256: ec93a345792ebcf6af6f4f50cea6395dccebc67a2ca05b314eace135f3c1ec93
      url: "https://pub.dev"
    source: hosted
    version: "1.0.2"
  path:
    dependency: "direct main"
    description:
      name: path
      sha256: "087ce49c3f0dc39180befefc60fdb4acd8f8620e5682fe2476afd0b3688bb4af"
      url: "https://pub.dev"
    source: hosted
    version: "1.9.0"
  path_provider:
    dependency: "direct main"
    description:
      name: path_provider
      sha256: c9e7d3a4cd1410877472158bee69963a4579f78b68c65a2b7d40d1a7a88bb161
      url: "https://pub.dev"
    source: hosted
    version: "2.1.3"
  path_provider_android:
    dependency: transitive
    description:
      name: path_provider_android
      sha256: bca87b0165ffd7cdb9cad8edd22d18d2201e886d9a9f19b4fb3452ea7df3a72a
      url: "https://pub.dev"
    source: hosted
    version: "2.2.6"
  path_provider_foundation:
    dependency: transitive
    description:
      name: path_provider_foundation
      sha256: f234384a3fdd67f989b4d54a5d73ca2a6c422fa55ae694381ae0f4375cd1ea16
      url: "https://pub.dev"
    source: hosted
    version: "2.4.0"
  path_provider_linux:
    dependency: transitive
    description:
      name: path_provider_linux
      sha256: f7a1fe3a634fe7734c8d3f2766ad746ae2a2884abe22e241a8b301bf5cac3279
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  path_provider_platform_interface:
    dependency: transitive
    description:
      name: path_provider_platform_interface
      sha256: "88f5779f72ba699763fa3a3b06aa4bf6de76c8e5de842cf6f29e2e06476c2334"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  path_provider_windows:
    dependency: transitive
    description:
      name: path_provider_windows
      sha256: "8bc9f22eee8690981c22aa7fc602f5c85b497a6fb2ceb35ee5a5e5ed85ad8170"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  platform:
    dependency: transitive
    description:
      name: platform
      sha256: "9b71283fc13df574056616011fb138fd3b793ea47cc509c189a6c3fa5f8a1a65"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.5"
  plugin_platform_interface:
    dependency: transitive
    description:
      name: plugin_platform_interface
      sha256: "4820fbfdb9478b1ebae27888254d445073732dae3d6ea81f0b7e06d5dedc3f02"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.8"
  sky_engine:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.99"
  source_span:
    dependency: transitive
    description:
      name: source_span
      sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
      url: "https://pub.dev"
    source: hosted
    version: "1.10.0"
  stack_trace:
    dependency: transitive
    description:
      name: stack_trace
      sha256: "73713990125a6d93122541237550ee3352a2d84baad52d375a4cad2eb9b7ce0b"
      url: "https://pub.dev"
    source: hosted
    version: "1.11.1"
  stream_channel:
    dependency: transitive
    description:
      name: stream_channel
      sha256: ba2aa5d8cc609d96bbb2899c28934f9e1af5cddbd60a827822ea467161eb54e7
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  stream_transform:
    dependency: transitive
    description:
      name: stream_transform
      sha256: "14a00e794c7c11aa145a170587321aedce29769c08d7f58b1d141da75e3b1c6f"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.0"
  string_scanner:
    dependency: transitive
    description:
      name: string_scanner
      sha256: "556692adab6cfa87322a115640c11f13cb77b3f076ddcc5d6ae3c20242bedcde"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  term_glyph:
    dependency: transitive
    description:
      name: term_glyph
      sha256: a29248a84fbb7c79282b40b8c72a1209db169a2e0542bce341da992fe1bc7e84
      url: "https://pub.dev"
    source: hosted
    version: "1.2.1"
  test_api:
    dependency: transitive
    description:
      name: test_api
      sha256: "9955ae474176f7ac8ee4e989dadfb411a58c30415bcfb648fa04b2b8a03afa7f"
      url: "https://pub.dev"
    source: hosted
    version: "0.7.0"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  vm_service:
    dependency: transitive
    description:
      name: vm_service
      sha256: "3923c89304b715fb1eb6423f017651664a03bf5f4b29983627c4da791f74a4ec"
      url: "https://pub.dev"
    source: hosted
    version: "14.2.1"
  web:
    dependency: transitive
    description:
      name: web
      sha256: "97da13628db363c635202ad97068d47c5b8aa555808e7a9411963c533b449b27"
      url: "https://pub.dev"
    source: hosted
    version: "0.5.1"
  win32:
    dependency: transitive
    description:
      name: win32
      sha256: a79dbe579cb51ecd6d30b17e0cae4e0ea15e2c0e66f69ad4198f22a6789e94f4
      url: "https://pub.dev"
    source: hosted
    version: "5.5.1"
  xdg_directories:
    dependency: transitive
    description:
      name: xdg_directories
      sha256: faea9dee56b520b55a566385b84f2e8de55e7496104adada9962e0bd11bcff1d
      url: "https://pub.dev"
    source: hosted
    version: "1.0.4"
sdks:
  dart: ">=3.4.1 <4.0.0"
  flutter: ">=3.22.0"

Steps to reproduce
I was following this guide: https://docs.flutter.dev/cookbook/plugins/picture-using-camera
I changed minSdk to 21 as mentioned.
Error on Emulator: Pixel 7a API 31
Expected results
Expected Results:
Emulator: Pixel 3a API 34
W/Camera  ( 8156): The selected imageFormatGroup is not supported by Android. Defaulting to yuv420
D/EGL_emulation( 8156): app_time_stats: avg=103.60ms min=15.34ms max=545.18ms count=10
I/Camera  ( 8156): startPreview
D/EGL_emulation( 8156): app_time_stats: avg=31.33ms min=8.93ms max=63.82ms count=30
I/Camera  ( 8156): CameraCaptureSession onConfigured
I/Camera  ( 8156): Updating builder settings
D/Camera  ( 8156): Updating builder with feature: ExposureLockFeature
D/Camera  ( 8156): Updating builder with feature: ExposurePointFeature
D/Camera  ( 8156): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 8156): Updating builder with feature: AutoFocusFeature
D/Camera  ( 8156): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 8156): updateNoiseReduction | currentSetting: fast
D/Camera  ( 8156): Updating builder with feature: FocusPointFeature
D/Camera  ( 8156): Updating builder with feature: ResolutionFeature
D/Camera  ( 8156): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 8156): Updating builder with feature: FlashFeature
D/Camera  ( 8156): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 8156): Updating builder with feature: FpsRangeFeature
I/Camera  ( 8156): refreshPreviewCaptureSession
D/EGL_emulation( 8156): app_time_stats: avg=208.43ms min=11.06ms max=569.48ms count=5
D/EGL_emulation( 8156): app_time_stats: avg=35.69ms min=13.88ms max=111.84ms count=25
D/EGL_emulation( 8156): app_time_stats: avg=34.70ms min=14.97ms max=58.31ms count=28
I/Camera  ( 8156): runPictureAutoFocus
I/Camera  ( 8156): lockAutoFocus
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/EGL_emulation( 8156): app_time_stats: avg=42.14ms min=15.22ms max=178.49ms count=25
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 5 | aeState: 2
I/Camera  ( 8156): captureStillPicture
D/Camera  ( 8156): Updating builder with feature: ExposureLockFeature
D/Camera  ( 8156): Updating builder with feature: ExposurePointFeature
D/Camera  ( 8156): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 8156): Updating builder with feature: AutoFocusFeature
D/Camera  ( 8156): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 8156): updateNoiseReduction | currentSetting: fast
D/Camera  ( 8156): Updating builder with feature: FocusPointFeature
D/Camera  ( 8156): Updating builder with feature: ResolutionFeature
D/Camera  ( 8156): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 8156): Updating builder with feature: FlashFeature
D/Camera  ( 8156): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 8156): Updating builder with feature: FpsRangeFeature
I/Camera  ( 8156): sending capture request
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
I/Camera  ( 8156): unlockAutoFocus
I/Camera  ( 8156): refreshPreviewCaptureSession
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
D/CameraCaptureCallback( 8156): CameraCaptureCallback | state: STATE_CAPTURING | afState: 5 | aeState: 2
I/Camera  ( 8156): onImageAvailable

Actual results
It works on API34 but doesn't in API31. The app I'm building targets from API29 onward.
Error I got:
Emulator: Pixel 7a API 31
I/CameraManagerGlobal( 3629): Connecting to camera service
W/Camera  ( 3629): The selected imageFormatGroup is not supported by Android. Defaulting to yuv420
I/Camera  ( 3629): startPreview
I/Camera  ( 3629): CameraCaptureSession onConfigured
I/Camera  ( 3629): Updating builder settings
D/Camera  ( 3629): Updating builder with feature: ExposureLockFeature
D/Camera  ( 3629): Updating builder with feature: ExposurePointFeature
D/Camera  ( 3629): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 3629): Updating builder with feature: AutoFocusFeature
D/Camera  ( 3629): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 3629): updateNoiseReduction | currentSetting: fast
D/Camera  ( 3629): Updating builder with feature: FocusPointFeature
D/Camera  ( 3629): Updating builder with feature: ResolutionFeature
D/Camera  ( 3629): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 3629): Updating builder with feature: FlashFeature
D/Camera  ( 3629): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 3629): Updating builder with feature: FpsRangeFeature
I/Camera  ( 3629): refreshPreviewCaptureSession
W/ImageReaderSurfaceProducer( 3629): ImageTextureEntry can't wait on the fence on Android < 33
D/EGL_emulation( 3629): app_time_stats: avg=218.84ms min=10.24ms max=1784.16ms count=11
D/EGL_emulation( 3629): app_time_stats: avg=182.34ms min=15.25ms max=325.74ms count=6
D/EGL_emulation( 3629): app_time_stats: avg=202.74ms min=33.12ms max=334.96ms count=6
D/EGL_emulation( 3629): app_time_stats: avg=191.33ms min=18.71ms max=326.59ms count=6
D/EGL_emulation( 3629): app_time_stats: avg=148.94ms min=14.81ms max=298.36ms count=7
D/EGL_emulation( 3629): app_time_stats: avg=276.47ms min=125.66ms max=516.41ms count=4
I/Camera  ( 3629): runPrecaptureSequence
I/Camera  ( 3629): refreshPreviewCaptureSession
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_WAITING_PRECAPTURE_START | afState: 0 | aeState: 2
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_WAITING_PRECAPTURE_DONE | afState: 0 | aeState: 2
I/Camera  ( 3629): captureStillPicture
D/Camera  ( 3629): Updating builder with feature: ExposureLockFeature
D/Camera  ( 3629): Updating builder with feature: ExposurePointFeature
D/Camera  ( 3629): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 3629): Updating builder with feature: AutoFocusFeature
D/Camera  ( 3629): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 3629): updateNoiseReduction | currentSetting: fast
D/Camera  ( 3629): Updating builder with feature: FocusPointFeature
D/Camera  ( 3629): Updating builder with feature: ResolutionFeature
D/Camera  ( 3629): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 3629): Updating builder with feature: FlashFeature
D/Camera  ( 3629): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 3629): Updating builder with feature: FpsRangeFeature
I/Camera  ( 3629): sending capture request
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 2
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 2
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
I/Camera  ( 3629): unlockAutoFocus
I/Camera  ( 3629): refreshPreviewCaptureSession
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/EGL_emulation( 3629): app_time_stats: avg=189.53ms min=101.74ms max=313.10ms count=5
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 3629): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
I/Camera  ( 3629): open | onError
I/Camera  ( 3629): close
I/Camera  ( 3629): open | onClosed

Code sample
Code sample
import 'dart:async';
import 'dart:io';

import 'package:camera/camera.dart';
import 'package:flutter/material.dart';

Future<void> main() async {
  // Ensure that plugin services are initialized so that `availableCameras()`
  // can be called before `runApp()`
  WidgetsFlutterBinding.ensureInitialized();

  // Obtain a list of the available cameras on the device.
  final cameras = await availableCameras();

  // Get a specific camera from the list of available cameras.
  final firstCamera = cameras.first;

  runApp(
    MaterialApp(
      theme: ThemeData.dark(),
      home: TakePictureScreen(
        // Pass the appropriate camera to the TakePictureScreen widget.
        camera: firstCamera,
      ),
    ),
  );
}

// A screen that allows users to take a picture using a given camera.
class TakePictureScreen extends StatefulWidget {
  const TakePictureScreen({
    super.key,
    required this.camera,
  });

  final CameraDescription camera;

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

class TakePictureScreenState extends State<TakePictureScreen> {
  late CameraController _controller;
  late Future<void> _initializeControllerFuture;

  @override
  void initState() {
    super.initState();
    // To display the current output from the Camera,
    // create a CameraController.
    _controller = CameraController(
      // Get a specific camera from the list of available cameras.
      widget.camera,
      // Define the resolution to use.
      ResolutionPreset.medium,
    );

    // Next, initialize the controller. This returns a Future.
    _initializeControllerFuture = _controller.initialize();
  }

  @override
  void dispose() {
    // Dispose of the controller when the widget is disposed.
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Take a picture')),
      // You must wait until the controller is initialized before displaying the
      // camera preview. Use a FutureBuilder to display a loading spinner until the
      // controller has finished initializing.
      body: FutureBuilder<void>(
        future: _initializeControllerFuture,
        builder: (context, snapshot) {
          if (snapshot.connectionState == ConnectionState.done) {
            // If the Future is complete, display the preview.
            return CameraPreview(_controller);
          } else {
            // Otherwise, display a loading indicator.
            return const Center(child: CircularProgressIndicator());
          }
        },
      ),
      floatingActionButton: FloatingActionButton(
        // Provide an onPressed callback.
        onPressed: () async {
          // Take the Picture in a try / catch block. If anything goes wrong,
          // catch the error.
          try {
            // Ensure that the camera is initialized.
            await _initializeControllerFuture;

            // Attempt to take a picture and get the file `image`
            // where it was saved.
            final image = await _controller.takePicture();

            if (!context.mounted) return;

            // If the picture was taken, display it on a new screen.
            await Navigator.of(context).push(
              MaterialPageRoute(
                builder: (context) => DisplayPictureScreen(
                  // Pass the automatically generated path to
                  // the DisplayPictureScreen widget.
                  imagePath: image.path,
                ),
              ),
            );
          } catch (e) {
            // If an error occurs, log the error to the console.
            print(e);
          }
        },
        child: const Icon(Icons.camera_alt),
      ),
    );
  }
}

// A widget that displays the picture taken by the user.
class DisplayPictureScreen extends StatelessWidget {
  final String imagePath;

  const DisplayPictureScreen({super.key, required this.imagePath});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Display the Picture')),
      // The image is stored as a file on the device. Use the `Image.file`
      // constructor with the given path to display the image.
      body: Image.file(File(imagePath)),
    );
  }
}

Screenshots or Videos

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.22.1, on Ubuntu 24.04 LTS 6.8.0-31-generic, locale en_US.UTF-8)
    • Flutter version 3.22.1 on channel stable at /home/mohit-marfatia/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a14f74ff3a (5 weeks ago), 2024-05-22 11:08:21 -0500
    • Engine revision 55eae6864b
    • Dart version 3.4.1
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/mohit-marfatia/Android/Sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /snap/android-studio/157/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✗] Linux toolchain - develop for Linux desktop
    ✗ clang++ is required for Linux development.
      It is likely available from your distribution (e.g.: apt install clang), or can be downloaded from https://releases.llvm.org/
    ✗ CMake is required for Linux development.
      It is likely available from your distribution (e.g.: apt install cmake), or can be downloaded from https://cmake.org/download/
    ✗ ninja is required for Linux development.
      It is likely available from your distribution (e.g.: apt install ninja-build), or can be downloaded from https://github.com/ninja-build/ninja/releases
    • pkg-config version 1.8.1
    ✗ GTK 3.0 development libraries are required for Linux development.
      They are likely available from your distribution (e.g.: apt install libgtk-3-dev)

[✓] Android Studio (version 2023.3)
    • Android Studio at /snap/android-studio/157
    • Flutter plugin version 80.0.1
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)

[✓] VS Code (version 1.90.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.90.0

[✓] VS Code (version 1.90.2)
    • VS Code at /snap/code/current/usr/share/code
    • Flutter extension version 3.90.0

[✓] Connected device (2 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64 • Android 12 (API 31) (emulator)
    • Linux (desktop)              • linux         • linux-x64   • Ubuntu 24.04 LTS 6.8.0-31-generic

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

! Doctor found issues in 2 categories.

Hi @Mohit-Marfatia,
W/ImageReaderSurfaceProducer( 3629): ImageTextureEntry can't wait on the fence on Android < 33 is just a warning and should not affect the application. What happens when you try to use the camera? I just tested on an emulator running android 31 and the camera seems to work just fine.

We should probably downgrade from a warning in any case, there isn't anything a user can do about the log.

The log messages themselves will be quite expensive ... I would consider dropping it altogether, or only printing in unopt modes.

@danagbemava-nc The camera opens just fine for me too. The issue is when I try to capture the image!
final image = await _controller.takePicture();
The camera freezes after this showing this:
I/Camera  ( 4116): runPrecaptureSequence
I/Camera  ( 4116): refreshPreviewCaptureSession
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_WAITING_PRECAPTURE_START | afState: 0 | aeState: 2
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_WAITING_PRECAPTURE_DONE | afState: 0 | aeState: 2
I/Camera  ( 4116): captureStillPicture
D/Camera  ( 4116): Updating builder with feature: ExposureLockFeature
D/Camera  ( 4116): Updating builder with feature: ExposurePointFeature
D/Camera  ( 4116): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 4116): Updating builder with feature: AutoFocusFeature
D/Camera  ( 4116): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 4116): updateNoiseReduction | currentSetting: fast
D/Camera  ( 4116): Updating builder with feature: FocusPointFeature
D/Camera  ( 4116): Updating builder with feature: ResolutionFeature
D/Camera  ( 4116): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 4116): Updating builder with feature: FlashFeature
D/Camera  ( 4116): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 4116): Updating builder with feature: FpsRangeFeature
I/Camera  ( 4116): sending capture request
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 2
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 2
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
I/Camera  ( 4116): unlockAutoFocus
I/Camera  ( 4116): refreshPreviewCaptureSession
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
D/CameraCaptureCallback( 4116): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
I/Camera  ( 4116): open | onError
I/Camera  ( 4116): close
I/Camera  ( 4116): open | onClosed

When I click capture again: I/flutter ( 4116): CameraException(Previous capture has not returned yet., takePicture was called before the previous capture returned.)
So I think it's not returning the image?  (I also tried running the code in Windows as well)

Hey, @matanlurey @danagbemava-nc, Can you please look into this problem that I'm facing?


[Hotfix][ENG-1674][WIP] Fix Permmissions for Daft Nodes.

Purpose
Fix 403s for legacy draft registration that resulted from a bugged migration.
Changes

adds one-off script with test.

QA Notes
All permissions for draft registrations should be tested.
Documentation
🐞 fix no doc.
Ticket
https://openscience.atlassian.net/browse/ENG-1674

Squashed into 468011ba50c5a6abd4866586b2155256bed277de , consider this merged 🌐


Separate documentation page for each target

A separate page for each target would make it easier to browse through the documentation.
These pages could show more information about the target, such as:

A longer description
Which theming items it supports (wallpaper, colors, fonts, opacity, etc)
Which platforms it supports (Home Manager / NixOS / Darwin)
Options for each platform
Whether manual setup is required for the module to work (see the Firefox module for example)

I have a few ideas for how this documentation could be generated:

A hidden list which each target adds an item to:
{
  stylix.documentationItems = [{
    targetName = "GNOME";
    targetDescription = ''
      This themes the status bar at the top of the screen, the app launcher,
       and the GDM login screen. For theming GNOME applications, see the GTK target.
    '';
    supportedItems = [ "fonts" "colors" ];
  }];
}

{
  stylix.documentationItems = [{
    targetName = "Firefox";
    supportedItems = [ "fonts" ];
    extraDocumentation = ''
      For this target to work, you need to fill in your profile name(s) using the option provided.
    '';
  }];
}

A hidden option called targets.«name».metadata, with the same format as above

A separate Nix or JSON file, with the same format as above

New suggestion: the extra documentation for each target could be a README.md in that folder, so it also shows up when browsing the source code


gulp build => mising ionic-timepicker.templates

Hello,
After running gulp build on master (no local changes), I get a 404 on the ionic-timepicker.html template. The ionic-timepicker.bundle.min.js is not generated exactly the same as the one in your repository. One difference is shown below - the ionic-timepicker.templates module is no longer present.
From master:
angular.module("ionic-timepicker",["ionic-timepicker.provider","ionic-timepicker.templates"]),angular.module("ionic-timepicker.provider",[]).provider("ionicTimePicker",function(){

After running gulp build on master:
angular.module("ionic-timepicker",["ionic-timepicker.provider"]),angular.module("ionic-timepicker.provider",[]).provider("ionicTimePicker",function(){

It looks like ng-html2js npm module is responsible for this maniplation. I get 2.0.2 when doing npm install. Maybe you have a different version?
Or should I not use gulp build, but instead some other command? Obviously without making any changes there is no point. But I plan to make changes including #73 and then allow changing date +/- a few as well.

The solution is to open src/ionic-timepicker.module.js and to uncomment line 3 with 'ionic-timepicker.templates'. Then when running gulp make-build  the resulting js file import the templates module correctly and there is no 404 for the template.

Yes, You are right @trivector-se.


Any guidance on how to implement custom operations with x10?

Is there a minimal example on how one can introduce a custom layer for shiny new x10 backend? I know we can enforce lazy tensor barrier, do whatever we want with tensor's memory and then schedule other x10 operations, but that will introduce performance hiccups because CPU/GPU sync and memory transfer. I'm looking for a way to be able to write arbitrary logic that would be compiled and run within the same pass with other built-in ops.
I would appreciate any help on this!
Edit: In case it might help by bringing a little context: I'm trying to implement a learnable look-up table. From what I can see it is not possible to implement any sampling operations using a composition of current ops in swift-api.

Thank you for the question!
As long as what you're trying to implement can be expressed in terms of XLA operations as described by https://www.tensorflow.org/xla/operation_semantics, it's possible. We just need to expose them as tensor methods, like we did for several operations already (check https://github.com/tensorflow/swift-apis/blob/master/Sources/x10/xla_tensor/ops/xla_avg_pool.h for example).

@asuhan thank's for such a quick answer. I will examine this one! Am I correct all those things have to be implemented in C++? Can one create custom ops for XLA? I want to implement some learnable pixel-level operators mostly based on sampling (like LUT, warping etc) but completely lost on where to start

Will XLA custom calls headers be exposed?
Like the ones stated in their tutorial
#include "tensorflow/compiler/xla/client/xla_builder.h"
#include "tensorflow/compiler/xla/service/custom_call_target_registry.h"

@s1ddok Currently they have to be manually implemented in XLA, but they're very simple wrappers over the XLA builder interface. They're simple enough that we plan to auto-generate them in the future, all the way to Swift.
Creating a completely custom operator is possible, but it'd require writing CUDA C++ (or C++, for CPU). We already use eager TF kernels running on CPU for a handful of operations which can't be expressed well in XLA. We haven't documented that in detail, but it's basically using copy to device operations to transfer the operands to CPU memory and the result back to the device. You can get a sense of how this is done by looking at https://github.com/tensorflow/swift-apis/blob/master/Sources/TensorFlow/Bindings/RawOpsDispatching.swift and https://github.com/tensorflow/swift-apis/blob/master/Sources/TensorFlow/Bindings/RawOpsGenerated.swift.
XLA itself offers a mechanism for custom calls (https://www.tensorflow.org/xla/custom_call), but it's quite similar in principle to what I've described and more difficult to deploy for our system.
Also, note that there's a performance penalty associated with doing such operators, since they'll break the trace into multiple, shorter traces and materialize intermediate results. Depending on how much you're leaning on custom operators vs regular ones, this might matter a lot or not at all.

@asuhan So basically even if you do custom CUDA stuff inside XLA custom calls that is basically the same as force tensor barrier and do whatever you want in user-space?

@s1ddok Correct, on GPU and CPU at least. For TPU there's the additional aspect of shipping data over network (a very fast one, to be fair) because of 2-VM design, which an XLA CustomCall can avoid.

I think this answers my question fully. Thanks for such a quick response!

@asuhan My knowledge is definitely dated, but I thought on GPU that XLA custom calls didn't force the equivalent of a lazy tensor barrier, but could instead be folded into the program. Do you know if that's true? If so, it sounds like there might be a performance benefit if we could eventually figure out how to plumb through custom calls (bearing in mind that these would only work on {CPU|GPU} and not TPU, but that seems reasonable). Or alternatively, have this sort of capability fold into @pschuh 's ideas for blending in eager-mode?

@saeta I can't imagine, conceptually, how could you fold CUDA C++ code into code generated by the XLA GPU backend. A custom call in XLA could avoid the overhead of an additional kernel launch, so it's not strictly the same thing. But, roughly speaking, we should be able to offer that functionality on our end without losing a lot of performance vs a custom call in XLA.

@saeta Note how a custom GPU call is done in XLA: https://www.tensorflow.org/xla/custom_call#custom-call_on_gpu. It's essentially a CPU stub, which subsequently calls a GPU kernel, so it doesn't look it'd even save a kernel launch.


chore(main): release 0.10.2

:robot: I have created a release beep boop
0.10.2 (2023-07-11)
Bug Fixes

swimmercost: fix 'SwimmerCost' unpickle bug (#195) (47d2d48)

Documentation

improve 'CartPoleCost' documentation. (#193) (16e3236)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rickstaa/stable-gym/releases/tag/v0.10.2 :sunflower:


Highlight unused components

I find that the number of components I use can increase quite a bit with more complex layouts and sometimes components become "unused" when I change something. I would like to have a visual indication (I use Atom) for components that are unused. Is there an Atom plugin that does that?

ESLint has an option where you can see unused variables. You can use that for components as well.
http://eslint.org/docs/rules/no-unused-vars and https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-uses-vars.md

Maybe I'm missing something, but I think @mschipperheyn is looking for something that highlights unused components in his project.
If you're using webpack, this might work for you
https://github.com/tomchentw/unused-files-webpack-plugin

I was thinking more something visual. Like I used to have using Eclipse for Java development. It gives a yellow underline under unused members

I use WebStorm and it supports this out of the box. Definitely worth trying
out, imo.
On Fri, 14 Apr 2017 at 8:10 am Marc Schipperheyn<EMAIL_ADDRESS>wrote:

I was thinking more something visual. Like I used to have using Eclipse
for Java development. It gives a yellow underline under unused members
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/690#issuecomment-294034910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABa4OC1No4P3RB0j3UuIW0CxnG695fhks5rvp1pgaJpZM4M8r6b
.

I am using lint-eslint package and eslint-plugin-react to get this in my atom:

Works for vanilla JS as well as react / styled-components


feat(nx-plugin): Replace vsc jest extension

Orta.vscode-jest is much more fully featured, including things like taking advantage of the "testing" panel and automatically running tests in test files and running them inline

Need to do some additional testing here to address usage in the monorepo environment - it's not actually working as I expected

Couple of comments on this:

I'm using npm run instead of nx run-many for a couple reasons. The immediate issue is https://github.com/jest-community/vscode-jest/issues/621 (or more specifically, https://github.com/nrwl/nx/issues/3450) seems to still be an issue, so jest crashes if trying to use it with this extension. The other is that what we would be asking is for all projects to be built, since builds are a dependency on tests. If using Nx cloud (see #83) that may be reasonable since we'd typically start with cached builds by default. But as-is, maybe we don't want to require a full build of everything?
If we take that a step farther, even if we do run an initial build, this extension is running jest in watch mode - changes to source files won't be reflected in the test results until a rebuild is done (unless of course you're already running a build in watch mode for whatever you're working on, which is admittedly probably common for most of what we're doing ie webapps). We could theoretically setup nx-spawn to handle a "run-many" scenario to run all tests and also run all dependent builds in watch mode... but I'm not convinced if we really want that performance hit.
Regardless, using this new extension means we're always running tests for all projects in watch mode - with a large number of packages/expensive tests, this could mean a performance hit - that's why Nx didn't suggest this by default, per https://github.com/nrwl/nx/issues/3868.

I'd like to hear feedback about the tradeoffs here, and whether or not we should even make this change.

After discussing this, we've opted not to make this change. This may be a handy extension people want to use (I probably will!), but having tests run in watch mode automatically is too heavy for us to recommend by default (on top of the potential confusion around needing to build).


How to Build A Swipe Application with React and MongoDB

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
This closes #6709

@jumamiller I have added more on the functionality of the route. The code should work well now! Thank you.

Hello @bhanjibrilliant -Please go through the changes I have made to help improve the quality of your future articles.
cc: @jumamiller


ak.Array should have a convenience method to_numpy

It would just pass through to ak.to_numpy, but it's much more convenient if it's a method, both for typing and so that third party libraries can check for its existence and call it (without import awkward!). @tacaswell suggested this and pointed out that it's like Pandas:
https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.to_numpy.html#pandas-dataframe-to-numpy
and almost like xarray:
http://xarray.pydata.org/en/stable/generated/xarray.Dataset.to_array.html#xarray-dataset-to-array
(which is unfortunately spelled differently: to_numpy vs to_array; I like to_numpy better).
The ak.Array.tolist method was spelled without the underscore because of the precedent set by np.ndarray.tolist, but maybe it should have a second spelling (a synonym!) with an underscore, for symmetry. It has an underscore in ak.to_list.

be aware that a better name for xarray.Dataset.to_array would probably be to_dataarray: it tries to combine all data variables into a single DataArray. Dataset itself doesn't have something like to_numpy (you would have to use to_array first), but for DataArray the values property can be used. I think we're open to adding something like to_numpy, though, see pydata/xarray#3245.


Add target for PRMS catchments

The code changes here add two targets to the data pipeline:

Download the geospatial fabric files; For this target I modified the function get_national_gf.R within the delaware-model-prep pipeline (here). To save storage space and download time I've set up the target to only download the data from region 2 as opposed to the national data.
Load the catchments ("HRU's") from the downloaded GF and subset to the PRMS segments within the DRB

This looks great! Works for me and pipeline runs.


Ability to submit themes using a specific branch, so I can support a version with and without exampleSite

Hi
I'd prefer that my main repo did not use the exampleSite folder. I think it makes the initial installation more complicated. So I'd prefer to just place all the example content in the root of the theme.
But to submit the theme to hugoThemes I need to use the exampleSite folder architecture. And of course I want to submit my theme here :)
I was wondering if it was possible to achieve both outcomes.
My first idea was that I would create a branch of my theme just for hugoThemes. master would contain the version which is ready for people to install easily, containing no exampleSite folder. branch hugoThemes would contain the version which contains the exampleSite.
Would it be possible for hugoThemes submissions to use a specific repo branch?
Rob

Hi Rob,
themes are added as Git submodules that follow the master branch by default. However, it's possible to track a different branch of a remote repository, in your case hugoThemes.
You can alter your theme repository accordingly and let me know if the hugoThemes branch should be used as a source for the theme demo.

Interesting idea, @JugglerX!
Curious if you managed to get a separate branch working well with Hugo Theme Site based on @digitalcraftsman's feedback?
Perhaps this has the potential to become a best practice. It could lead to improving the experience of users (less irrelevant files/folders causing confusion for the end users) whilst satisfying the requirements for Hugo Theme Site.
I suppose there might be slight additional effort for maintainers to maintain duplicate Readme across branches (using rebase/branch file checkout to keep in sync)?

I created a new branch hugoThemes and I made a new theme submission in a seperate issue. https://github.com/gohugoio/hugoThemes/issues/912
@digitalcraftsman please let me know If i've misunderstood and need to do something else to facilitate using the hugoThemes branch.

As stated in #912 it looks like everything went smoothly. Are there any questions remaining regarding this issue?

I've just updated my master branch and removed the exampleSite folder from it. Let's make sure that doesn't cause any problems (maybe the submodule was still using something from master and we didnt realise because master and hugoThemes branches were exactly the same code until today) and I think we can close it. I'm so glad this was an option.


Hands Sliding

Hands should be able to freely move around the grip volume if they are being held somewhere else.

Careful with volumes that support inverted hands. Use the ScoredSnapPose provided by the initial grab to ensure it is maintained also when regrabbing


[NuGet.org Bug]: If package has no dependencies than you can't see which framework it references

Impact
It bothers me. A fix would be nice
Describe the bug
If package has no dependencies than you can't see which framework it references
For example: https://www.nuget.org/packages/NReco.PdfGenerator/
Fuget has net45 correctly listed
Repro Steps
Open https://www.nuget.org/packages/NReco.PdfGenerator/
Go to dependencies tab
No dependencies is listed
Expected Behavior
It should say net45 in the above case
Screenshots

Additional Context and logs
No response

I think it's fixed, because my package show the framework that I used :

or :

Unfortunately it's not fixed, found another library https://www.nuget.org/packages/Select.HtmlToPdf/
Seems issue is with full framework packages

Hi. The issue looks like a duplicate of https://github.com/NuGet/NuGetGallery/issues/4843. There is work planned for coming weeks to start surfacing this information in a better way on package details page.


Make extractResult fail-fast when there's no content type

This is a breaking change, it's probably a starting point. Probably a configuration is needed to opt-in for the feature.

Hi @IvanVas, Can you explain the rational behind this? I've not read the spec or looked to see what happens with a null value, but I'd just like to understand it.

@jamezp Thanks for looking into this!
If the server doesn't send the Content-Type header, the client gets null with no explanation. AFAIU, the only way to troubleshoot is debugging.

@jamezp What do you think?

Hi @IvanVas. Sorry for the very long delay on this. I do think this makes sense. I filed https://issues.redhat.com/browse/RESTEASY-3178.
Do you know how/when the media type is null? I'm just looking for a way to reproduce it is all. However, I do agree returning null does not seem correct. I think, per the documentation, the [ResponseProcessingException](https://jakarta.ee/specifications/restful-ws/3.1/apidocs/jakarta.ws.rs/jakarta/ws/rs/client/ResponseProcessingException.html) might be the correct exception to throw.

Do you know how/when the media type is null? I'm just looking for a way to reproduce it is all
The scenario:
The server returns a response without Content-Type. Which is incorrect ofc, but we have to spend some time debugging in order to discover the problem. Having a fail-fast mechanism (exception) would help a lot!

If you can point me to the correct level of tests I can try to create a test which would reproduce this.

I think, per the documentation, the [ResponseProcessingException](https://jakarta.ee/specifications/restful-ws/3.1/apidocs/jakarta.ws.rs/jakarta/ws/rs/client/ResponseProcessingException.html) might be the correct exception to throw.

Great! Will update this once we have a consensus on the approach.

Do you know how/when the media type is null? I'm just looking for a way to reproduce it is all

The scenario: The server returns a response without Content-Type. Which is incorrect ofc, but we have to spend some time debugging in order to discover the problem. Having a fail-fast mechanism (exception) would help a lot!
If you can point me to the correct level of tests I can try to create a test which would reproduce this.

In that case I'd almost say throwing the exception is correct. If users start seeing an issue then they could just create a ClientResponseFilter to set a content-type header.

Do you know how/when the media type is null? I'm just looking for a way to reproduce it is all

The scenario: The server returns a response without Content-Type. Which is incorrect ofc, but we have to spend some time debugging in order to discover the problem. Having a fail-fast mechanism (exception) would help a lot!
If you can point me to the correct level of tests I can try to create a test which would reproduce this.

In that case I'd almost say throwing the exception is correct. If users start seeing an issue then they could just create a ClientResponseFilter to set a content-type header.

I'll change the exception type then.
Will I be able to create an appropriate test with moderate effort?

@IvanVas This would be my suggestion #3176. I'm not sure how to create a test, but I'll try to come up with one.

I'm gonna close this in favor of #3176. Thank you @IvanVas!


Improve source maps

First of, thanks for adding source map support! I've been trying to use nyc@4 with the project that lead to my code coverage article from last week. I got it working but had to make some changes. This is the second PR which covers the source map handling.

I'm now caching a source map if a file is added, even if the dependency wasn't loaded via a custom require hook. This helps with cases where the file was compiled using say a watcher.
nyc now also loads source maps that are merely referenced by the source file.
Finally, if the covered file came from a single source (according to its source map), the path is rewritten to the original source. Subsequent reports that include the file content, like the HTML report, will now show the correct content.
Without rewriting the path the HTML report will show compiled output highlighted using the remapped coverage information.
If there are two or more sources the compiled output will be shown, with the wrong coverage information. I'm not sure how to split coverage over multiple source files. Hopefully that's an edge-case.
It's getting late in the day in my timezone so I haven't had a chance to update the tests to cover this new behavior. The coverage report for my own project looks the same as it did previously with my more custom setup so that's encouraging.

@novemberborn these changes are looking great \o/
I've added you as a collaborator to the project, it's great to have another set of eyes from someone who's dived so deep into the codebase.
I'll code-review your work more thoroughly after the work day. It's all looking good, but we need to be careful to test nyc in a bunch of hostile environments: babel, no babel, subprocess, no subprocess, Windows, not Windows:
I'd also like to have this issue in mind as we work on sourcemap support:
https://github.com/sindresorhus/ava/issues/185

I tested this on several of my projects and it works wonderfully, great job :star:
Before we merge, would you mind adding tests for _rewritePath() :+1: otherwise, it's looking great.

I've added you as a collaborator to the project, it's great to have another set of eyes from someone who's dived so deep into the codebase.

Thanks!

I'll code-review your work more thoroughly after the work day. It's all looking good, but we need to be careful to test nyc in a bunch of hostile environments: babel, no babel, subprocess, no subprocess, Windows, not Windows:

I wonder if Travis can help with that?

Before we merge, would you mind adding tests for _rewritePath()  otherwise, it's looking great.

Sure. Looks like I need to add a fixture file with a source map that doesn't have sources, and another that has more than one source. For which I then need to generate coverage. Could you tell me how test/fixtures/coverage-to-map.json is generated?

Could you tell me how test/fixtures/coverage-to-map.json is generated?

Is this how?
rm -rf .nyc_output test/fixtures/.nyc_output
rm -rf coverage
npm test
$(npm bin)/nyc report --reporter=json
cp coverage/coverage-final.json test/fixtures/coverage-to-map.json
# And now prettify the coverage-to-map.json file

The diff is a little different though, and the source-map-cache > branches > maps all branches back to their original loc test now fails. The branchMap object ends up empty.
I'm not quite sure about the relationship between code-with-map.js and es6-not-loaded.js. The latter is quite a lot shorter! Where did the extra code in code-with-map.js go?
It seems like maybe the fixtures in https://github.com/bcoe/nyc/commit/c6a23b99c5632250f675df166bcc279a8f8d0882 happen to work but aren't actually reproducible?
Please let me know how to regenerate the coverage map so I can make the current tests pass again with a new map, and then I can add the three new source-map permutations I need to complete test coverage.

@novemberborn my secret is out, I generated the fixtures against code that is no longer checked into the codebase -- the approach I used to generate the fixtures was a little bit wonky too, rather than taking the files output in /.nyc_output, I hacked in a couple lines of code to output the fixtures and ran the code with these hacks once. Adding a line here:
https://github.com/bcoe/nyc/blob/master/lib/source-map-cache.js#L14
if (sourceMap) require('fs').writeFileSync('./test/fixtures/my-awesome-fixture.js', source, 'utf-8')

And here:
https://github.com/bcoe/nyc/blob/master/lib/source-map-cache.js#L21
require('fs').writeFileSync('./test/fixtures/my-awesome-fixture.json', JSON.stringify(coverage, null, 2), 'utf-8').

I then created a little testing file that required the specific modules I wanted to create fixtures out of, and ran it with ./bin/nyc -- sorry about how manual and painful this is.

@novemberborn great work. I'm going to publish this in a minor relese, which will be followed shortly with a major bump when we pull in the in @Lalem001's exclude improvements.


PSS: add container_engine_t to allowed list of selinux types

follow up of https://github.com/kubernetes/kubernetes/pull/126165#issuecomment-2245401925

/lgtm
/approve


#!/usr/bin/env: No such file or directory

I'm testing the package name changing script in appcenter, but I get an error
appcenter-pre-build.sh
/Users/vsts/agent/2.136.1/work/1/s/mobileapp/appcenter-pre-build.sh: line 1: #!/usr/bin/env: No such file or directory

Hi @palbordoy, thats weirds, don't makes sense return an error in the first line of the script.
Can you share your script with us?

@palbordoy can you exclude an encoding issue for the provided appcenter-pre-build.sh file? Have you created it with Windows?

It was the encodig that was wrong. Changed it to ANSI, and now appcenter is running the script. Anyway, the script is actually not doing anything. I placed it in the project root folder, and added the packagename variable to appcenter. The package name remains the same :(
======================================
Task         : Shell Script
Description  : Run a shell script using bash
Version      : 2.1.3
Author       : Microsoft Corporation
Help         : More Information
[command]/bin/bash /Users/vsts/agent/2.136.1/work/1/s/Testapp/appcenter-pre-build.sh
##[section]Finishing: Pre Build Script
##[section]Starting: Build Xamarin.Android project
I was expecting somethink like: "Updating package name to $PACKAGE_NAME in AndroidManifest.xml"


feat: access text fields using hint text

Android accessibility API has a way to set and get hints for components like Text Field or Input Field.
https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#getHintText()
As per the latest Flutter 3.7, they have started using hint text as per this https://github.com/flutter/flutter/issues/114511.
Reference: https://github.com/flutter/flutter/issues/119326
If possible, can we get this feature to access text fields using hint text?

This section to access text field is breaking with Flutter 3.7
https://maestro.mobile.dev/platform-support/flutter#example-tap-on-textformfield

Any updates to this issue? This issue still persists on 3.7.7


upgrade spartan and navstar to improve the logging

High Level Description
This commit fixes following issues.

navstar failure in 1k nodes cluster
corruption of crypto cluster id
Improves logging by including pid, module, function and line number in log message

Related Issues

DCOS_OSS-796 navstar unhealthy in 1k node cluster.
DCOS_OSS-720 Cryptographic Cluster ID is longer than ~50chars
DCOS_OSS-804 Improve logging of networking component

Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[x] Test Results: [link to CI job test results for component]
[x] Code Coverage (if available): [link to code coverage report]

https://github.com/dcos/navstar/pull/56
https://github.com/dcos/lashup/pull/31
https://github.com/dcos/minuteman/pull/94
https://github.com/dcos/navstar/pull/57
https://github.com/dcos/minuteman/pull/96
https://github.com/dcos/navstar/pull/58
https://github.com/dcos/spartan/pull/33

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@spahl @alberts this is ready to be reviewed and ship for 1.9 rc4


Missing documentation for using the Dataset API in combination with image summaries

The Dataset API is now the recommended input pipeline, however I am missing some guidance on how to include summaries of my images.
def get_data():
  dataset = FixedLengthRecordDataset(...)
  dataset = dataset.map(parse_dataset, ...)
  if is_training:
    dataset = dataset.map(preprocess_for_train, ...)
  # Do shuffling, batching...
  return dataset

def preprocess_for_train(image, label):
  # Do preprocessing...
  image = tf.image.random_flip_left_right(image)
  # Add summary
  tf.summary.image('preprocessed_image', tf.expand_dims(image, 0))
  return image, label

This is what I would do intuitively, but since map() uses a different thread and therefore a different tf.Graph instance (?), the summaries are lost.
What is the recommended way of adding image summaries when using the Dataset API? I would like to request a comment / example on that in the official docs.

Hi,
afaik you can run the summary, but only after you created the iterator and fetched the next element:
dataset = get_data(is_training=True)
t_example = dataset.make_one_shot_iterator().get_next()
tf.summary.image('preprocessed_image', t_example['image'])

@marcoadurno That's true, but it comes with a drawback. Assume the training loop looks like this:
image_batch, label_batch = sess.run(t_example)
_, summary = sess.run([train_op, summary_op],
                      feed_dict={image: image_batch, label: label_batch})

This will invoke the iterator's get_next twice, once you run t_example and once you request the summary since you introduced a dependency.

@stecklin I'm not sure I fully understand the reason why image_batch and label_batch have be be fetched using sess.run to then fed back in using placeholders. If doing so, I think the summary_op should use the image placeholder, same as train_op does but I struggle to see why mixing the Data api with placeholders.
If things can be shuffled around:
dataset = get_data(is_training=True)
t_example = dataset.make_one_shot_iterator().get_next()
t_logits = infer_fn(t_example['image'])
loss_op = loss_fn(t_example['labels'], t_logits)
train_op = train_fn(loss_op)
summary_op = tf.summary.image('preprocessed_image', t_example['image'])
for i in xrange(n_steps):
  fetches = [loss_op, train_op]
  if i%100:
    fetches += [summary_op]
  sess.run(fetches)

Or alternatively you can use a monitored session and specify summary hooks. But the basic idea is that if you have a canonical training loop there is no reason why summaries can't be written using the Data api.

@MarkDaoust maybe we need more docs.
/CC @mrry

@marcoadurno Thank you so much for pointing that out. You made me realize that I am not using the Dataset API as it is meant to be used, that there is no need for placeholders.
Summaries can be added as you suggested, works like a charm.


create_test_video fails if pillow version is greater 4.1

I tried to set up the tool on Ubuntu 16.04
When generating the test content, without changing the script, it fails Generating the video.
Problem is the version of pillow, which was 4.2, downgrading to 4.1 is a workaround.
See also here
https://github.com/python-pillow/Pillow/issues/2614
The stacktrace of the error is:
Generating video images... Traceback (most recent call last):   File "./src/generate.py", line 424, in <module>     for frame in frames:   File "/home/dvbcss/sync_accurcy_test/dvbcss-synctiming/test_sequence_gen/src/video.py", line 321, in genFrameImages     w,h = font.getsize(text)   File "/usr/local/lib/python2.7/dist-packages/PIL/ImageFont.py", line 156, in getsize     size, offset = self.font.getsize(text, direction, features) SystemError: error return without exception set Error during creation of wav/png/metadata. Aborting

Good news, https://github.com/python-pillow/Pillow/issues/2614 has been fixed in this week's Pillow 4.3.0 release.
pip install -U pillow should sort it for you.


Fixed to recognize domains with only one character

Fixed this issue.

https://github.com/santa112358/detectable_text_field/issues/49#issue-1861710140

@all-contributors please add @furukaze-akane for code


Several Live Demos are missing

The docs say that "Click here to see live demos" which points to a page listing examples, including:
/one-chat-room/
/many-chat-rooms/
But these example does not appear to have a live demos - they only contain instructions to  manually download, build, and run locally.
This is also the case for the file sharing example, though I guess a live demo wouldn't be practical there because it's a CLI tool.
This is not the case for e.g. the streaming example, which does have a live demo. However, the listed example "Collaborative Machine Learning" actually just links to the simple streaming example, not something with a frontend resembling the demo GIF.

Thanks for creating this issue.
There are three live demos right now deployed, but only 1 had the actual link available in the README as you have noticed.
I added all the links just now to respective examples
One chat room
https://chat.dao.xyz   (Create a room in one tab and copy the link and open it in another tab)
ML Demo
https://mldemo.dao.xyz
Live stream
https://stream.dao.xyz/
The rest of the demos have to clone the repo and run the frontend app locally.
Working continuously on making the examples better. There will be a release in a few days simplifying some of the example code and adding more examples.

Those work, thanks!


Add serial checker

There is a merge conflict on this PR, also not sure how up to date this data is. I think we normally recommend people to check out the GBATemp thread as it's constantly being updated. Also we probably don't want people posting their serial number in Discord.


Skip loading behavior when behavior_timeout=0

The user may set behavior_timeout=0. This means that they don't want
to run the behavior. As it is now, Brozzler will invoke
brozzler.behavior_script to load the script and self.run_behavior
to execute it.
We will run the behavior using Runtime.evaluate but then it will be
terminated immediately because of timeout=0.
It is better to skip behavior loading and running when
behavior_timeout=0.

behavior_timeout is an existing parameter for Browser.browse_page, which is used directly by other code.


Rails 4.2.0beta1 : undefined method `merge!' for #ActionDispatch::Routing::Mapper::Scope:0x007fe4b8dfd7f8

Updated Rails to 4.2.0.beta1.  Received the following stack trace when launching rails s :
/Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:457:in `ensure in with_devise_exclusive_scope': undefined method `merge!' for #<ActionDispatch::Routing::Mapper::Scope:0x007fe4b8dfd7f8> (NoMethodError)
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:457:in `with_devise_exclusive_scope'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:248:in `block (2 levels) in devise_for'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:351:in `block in devise_scope'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/actionpack-4.2.0.beta1/lib/action_dispatch/routing/mapper.rb:932:in `block in constraints'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/actionpack-4.2.0.beta1/lib/action_dispatch/routing/mapper.rb:808:in `scope'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/actionpack-4.2.0.beta1/lib/action_dispatch/routing/mapper.rb:932:in `constraints'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:350:in `devise_scope'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:247:in `block in devise_for'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:223:in `each'
	from /Users/aantix/.rvm/gems/ruby-2.1.1/gems/devise-3.3.0/lib/devise/rails/routes.rb:223:in `devise_for'
	from /Users/aantix/dev/followup/config/routes.rb:6:in `block in <top (required)>'

Here's the offending line in my routes file.
devise_for :users, controllers: {registrations: "users/registrations", sessions: "users/sessions", passwords: "users/passwords", omniauth_callbacks: "users/omniauth_callbacks"}, skip: [:sessions, :registrations]

Still need to investigate this.

You can use devise 3.4.1.


Apply autolayout to workspace's JSON

Hello,
I have a JSON representation of a workspace and I would like to automatically fill the x and y attributes of the view's components (for example with Graphviz). Is it possible to do that with the cli or do I need to use https://github.com/structurizr/java-extensions/tree/master/structurizr-graphviz directly?
(Ideally, an option to the export command could do this)

You could do something like this:

Create yourself a new DSL file (e.g. graphviz.dsl), that extends your JSON workspace, and applies graphviz.

workspace extends workspace.json {

    !script groovy {
        new com.structurizr.graphviz.GraphvizAutomaticLayout().apply(workspace);
    }

}

Use the CLI to export to a new JSON file.

./structurizr.sh export -workspace graphviz.dsl -format json

Awesome! Thank you.


atomicops: Remove Acquire_Store / Release_Load

gperftools' internal atomicops library included atomic
Release Load and Acquire Store operations; those operations
were unused and expressed ordering constraints that aren't
expressible in the C++ standard memory model.
Remove them, to make a transition to C++11 atomics easier
and to avoid confusing use of them.

Thank you! Applied.


bitcoin address can contain amount which needs to be paid

We can also have a amount linked with bitcoin address. We don't currently support that.

the bip for reference https://en.bitcoin.it/wiki/BIP_0021

Found this library but it takes account addresses for only mainnet https://github.com/dart-bitcoin-lib/dart-bip21

it is not right if support only mainet


Adds cmp

Very similar to partial_cmp, primary difference is that cmp is used for the comparison instead of partial_cmp and as such the code was changed to accommodate that (Item's implement Ord instead of PartialOrd, Ordering is returned instead of Option), etc

cc/ @montekki can I ask you to review this? :blush:

@assemblaj @yoshuawuyts generally LGTM, but it would be super great to explore in the future some single  generic version of these comparison combinators and implement them all with it. Does the regular std do something of this kind? Probably we need to take a look.

@montekki  For the most part std just uses duplicate code for all of the comparison functions, I think. But those implementations are more simple in nature.
https://doc.rust-lang.org/1.3.0/src/core/iter.rs.html#3229-3243
https://github.com/rust-lang/rust/blob/master/src/libcore/iter/traits/iterator.rs
Do you think it would be feasible to use (or build) something like Zip that could just iterate both streams at once, and then compare the values?

it looks like partial_cmp is implemented with partial_cmp_by https://github.com/rust-lang/rust/blob/master/src/libcore/iter/traits/iterator.rs#L2630, this also goes for cmp which is implemented with cmp_by. It looks like there is no way to make a silver bullet generic comparator because of different order operations and types, but at least for cases like cmp and cmp_by code can probably be re-used.

partial_cmp_by and cmp_by seem to be helper functions that are only used by partial_cmp and cmp, respectively. The rest of the comparison functions (lt, gt, ne, etc)  are built with partial_cmp, cmp, and eq though. Using that approach seems like a good idea, if feasible.  What's the syntax for using a Future within another Future?  Would you just use '.await'?

What's the syntax for using a Future within another Future?

You would need to store the future internally, and then manually poll it to completion in a new future. A good example of this would be @montekki's recent series of patches in #262.


chore: Update Weaviate default version to v1.25.5

This is just a small PR that updates Weaviate default version to v1.25.5

I need to re-test it and then will open the PR once again


Add gradle command that auto detects user's OS and builds the project accordingly

@championswimmer
This will fix the
"Error: CreateProcess error=2, The system cannot find the file specified" that happens with Windows users while building the project.
Built it on both Windows and Linux and the project builds perfectly fine.

@mananwason Could you have a look here?
I have discussed this issue with Arnav and he acknowledged the issue while building the project on Windows.
This script will auto detect user's OS and build accordingly.
Cheers.

@the-dagger Again this issue is not with the project. If you have git in your environment path variable, this will build fine.

Ok, I'll recheck this and will let you know.

:+1: Closing this for now then.

@mananwason @championswimmer I have added git to the environment path variable and the problem persists.
I have even checked if I did it properly by running git --version in CMD and it returns git version 2.6.4.windows.1
Which means I do have git in my path.
The error that i get on gradle sync is
Error:(4, 0) CreateProcess error=2, The system cannot find the file specified

@mananwason, a slight Change in the command is needed for Windows, even if
git is in path. @the-dagger is right on that
On 02-Apr-2016 5:42 pm, "Harshit Dwivedi"<EMAIL_ADDRESS>wrote:

@mananwason https://github.com/mananwason @championswimmer
https://github.com/championswimmer I have added git to the environment
path variable and the problem persists.
I have even checked if I did it properly by running git --version in CMD
and it returns git version 2.6.4.windows.1
Which means I do have git in my path.
The error that i get on gradle sync is
Error:(4, 0) CreateProcess error=2, The system cannot find the file
specified
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/fossasia/open-event-android/pull/305#issuecomment-204704371

@championswimmer this PR looks good or are there some changes to be made?

I tried building the project in windows but I didn't get any errors and the build was successful. Are your SDKs are updated one?

@opticod Yep they are.

@championswimmer @the-dagger @opticod I also tried building on 2 windows machines and I didn't face any errors :confused:

@mananwason Reverted back to the stable build of windows 10 and it builds correctly.
Installed the beta build again and the build fails.
Maybe its because of that.
Cheers.

Cool :+1


chore(perf): protorev tracker coin array

Closes: #XXX
What is the purpose of the change
This is Part 2/2 in protorev tracking perf changes.
This PR utilizes a new key store and tracks by denom key, which prevents us from having to serialize every coin whenever taker fees are tracked.
Side note: There were three proto rev trackers:

Tx fees: Is now removed
Taker Fees: Modified to coin array here
Cyclic Arb: We dont modify this logic, because it is called once at time of initialization, and then compared to the cyclic arb profits that protorev tracks and the difference is taken. It is not called on its own after every action like the taker fee and tx fee trackers

Testing and Verifying
Ran the query in E2E after the upgrade and noted that:

The count resets
The block height changes to the upgrade height as expected

Its not really the array that makes it more performant. Its storing the value of a single Coin object in the kvstore, and then when updating that denom we only have to retrieve that single coin rather than all coins. Then when retrieving all of them to display, we retrieve as an array of Coin rather than the single Coins value stored previously.

@p0mvn should be good for a second review now, appreciate it


test: use precompiled statements in examples

Prepared statements improve performance by caching the execution plan for a query after the query optimizer has found the best plan.
If the query doesn't have a complicated plan (such as simple selects/inserts with no joins), then prepared statements won't give you a big improvement since the optimizer will quickly find the best plan.
SQLite helpers has been renamed in test examples.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 94.348%

Totals

Change from base Build<PHONE_NUMBER>:
0.6%

Covered Lines:
651

Relevant Lines:
690

💛  - Coveralls


[Tests] EAS RFC test crashes if used with rebooting and kernel update feature

Reported by: Morten Rasmussen
rfc.py:EAS test crashes if used on TC2 with rebooting feature if the kernel has been updated.
The 60s waiting time appears to be insufficient time for TC2 to reboot if a new kernel has to be loaded into flash by the bootloader.
Maybe have a more flexible approach poking the target ip-address every 5s to see if it is up and ssh login is possible instead of a fixed wait period?
TestEnv.reboot() is currently not useable on TC2 due to the short time-out.

Should have been properly fixed by PR #33


Seems to complete successfully, but site has no SSL

After enabling a Hobby account and http-sni, I was able to run sabayon for my node app. I've also added the express code.
user@users-Mac ~/D/d/mywebsite>
heroku run sabayon --force --app mywebsite-encryptor

Running sabayon --force on ⬢ mywebsite-encryptor... up, run.7453
2016/06/25 23:38:02 cert.create<EMAIL_ADDRESS>domains='[mywebsite.com]'
2016/06/25 23:38:02 [INFO] acme: Registering account for<EMAIL_ADDRESS>2016/06/25 23:38:03 [INFO][mywebsite.com] acme: Obtaining bundled SAN certificate
2016/06/25 23:38:03 [INFO][mywebsite.com] acme: Could not find solver for: dns-01
2016/06/25 23:38:03 [INFO][mywebsite.com] acme: Could not find solver for: tls-sni-01
2016/06/25 23:38:03 [INFO][mywebsite.com] acme: Trying to solve HTTP-01
2016/06/25 23:38:03 cert.validate
2016/06/25 23:38:23 cert.validated
2016/06/25 23:38:24 [INFO][mywebsite.com] The server validated our request
2016/06/25 23:38:24 [INFO][mywebsite.com] acme: Validations succeeded; requesting certificates
2016/06/25 23:38:25 [INFO] acme: Requesting issuer cert from https://acme-v01.api.letsencrypt.org/acme/issuer-cert
2016/06/25 23:38:25 [INFO][mywebsite.com] Server responded with a certificate.
2016/06/25 23:38:25 cert.created
2016/06/25 23:38:26 cert.added

However, my site is not encrypted. Did I miss a step?

What if you add https to the URI instead of http?
Sabayon will not force-redirect http requests to their https equivalent. This is something you need to handle within your app's code.
What is your app's domain?

@dmathieu When I add https to the URL, I get a certificate error that there is a domain mismatch. The cert comes from DigiCert for *.herokuapp.com. So that seems like the default that Heroku adds.
I will email you privately the apps' domain.

Moved this to email.

Created https://github.com/dmathieu/sabayon/pull/16 if that's helpful.


Mapping terminated before handling trigger: oneshot canceled, code: SubgraphSyncingFailure

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Successfully calling a contract method produces Mapping terminated before handling trigger: oneshot canceled, code: SubgraphSyncingFailure in my local graph node.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
I've deployed a simple subgraph to my local graph node. Calling a contract method succeeds with an emitted event but causes this error on the node and gives no further details.
What is the expected behavior?
The node should succeed in handling the contract event.
My contract is simple and emits an event from the method I'm calling. The mapping function is simply setting event parameters as fields in a new entity object and saving it, nothing more. I'm guessing maybe there's some issue with the mapping function -- is there any other log the node provides?
Only other thing to note is the event has some indexed parameters. I'm not sure if that makes a difference.

Please run with GRAPH_LOG=trace in the environment and post a link to the complete logs. Having the subgraph source available might also help.

Through trial and error I found the offending line was this:
entity.created = (Date.now() / 1000) as i32

I changed the schema's created field to a BigInt and changed the mapping to this and it now works:
entity.created = event.block.timestamp

Is this considered the proper way of getting a rough time for an entity's creation?


Remote IPs get truncated in the internet view

It's not terribly useful, as you can't select them. The column should probably be wide enough for an IP.

It seems odd to me that it is truncating these strings when there is loads of white space to the right of them.


SyntaxError: invalid syntax

transcrypt -b -m -n hello.py
File "/usr/local/bin/transcrypt", line 7, in
from transcrypt.main import main
File "/usr/local/lib/python3.5/dist-packages/transcrypt/main.py", line 77
with tokenize.open (f'{modulesDir}/org/transcrypt/envir.js') as envirFile:
SyntaxError: invalid syntax

Which version of Transcrypt are you using?

If you have to deliver tomorrow, you may also install the TS version you were  using before under Python 3.5.
See:
https://stackoverflow.com/questions/5226311/installing-specific-package-versions-with-pip
All old versions are still available.

You don't want to know the kind of mistakes I make.
Yesterday I've been bug hunting for 3 hours.
Turned out to be a missing underscore...

lol

By the way, in dutch the word 'lol' means fun, literally, not as an abbreviation.

Let me know if it works.

@JdeH This really wants to be the very first thing people read in a 'how-to'. I've spent all afternoon trying to resolve an
uncaught referenceError
that was due to the missing
window.hello = hello
Just the kind of thing to snare a C++ guy.
Documentation lag apart this is really nifty stuff. Thank you.

@g40:
Turned out that all the examples on the site were still done with the old version of Transcrypt without modules, it's corrected now.
If you still encounter problems like this, please let us know.
Such things are crucial to newcomers to Transcrypt.
By the way, it's a pleasure to encounter someone who's into C++.
Have been using that language ever since its birth.
Still a solid powerhouse comparable to nothing.

@JdeH Thanks for the update. I am still working through my web 'application', which uses W2UI  and  websockets to talk to various servers. It might make for a useful end-to-end example. Would that be of interest? Please feel free to contact me offline (g4 at novadsp dot com) if so. Thanks again for listening.

Closing since no further comments for a while now.


Failing to connect to objects.githubusercontent.com

I'm using a Docker build for deploys, happily based on hexpm/elixir tags.
Was working fine until this afternoon when our builds started failing with the following:
20:05:41.171 [notice] TLS :client: In state :hello_middlebox_assert at ssl_gen_statem.erl:736 generated CLIENT ALERT: Fatal - Unexpected Message
 - {:unexpected_msg, {:internal, {:encrypted_extensions, %{sni: {:sni, []}}}}}
** (RuntimeError) couldn't fetch https://objects.githubusercontent.com/github-production-release-asset-2e65be/72474275/7945012e-ed08-429b-a243-f203131fe2b5?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220826%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220826T200541Z&X-Amz-Expires=300&X-Amz-Signature=faa383efd5b17a3e0633ad2104fa4086232ba172d03c49e068aab33682ba4032&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=72474275&response-content-disposition=attachment%3B%20filename%3Ddart-sass-1.54.5-linux-x64.tar.gz&response-content-type=application%2Foctet-stream:
      {:error, {:failed_connect, [{:to_address, {'objects.githubusercontent.com', 443}}, {:inet, [:inet], {:tls_alert, {:unexpected_message, 'TLS client: In state hello_middlebox_assert at ssl_gen_statem.erl:736 generated CLIENT ALERT: Fatal - Unexpected Message\n {unexpected_msg,{internal,{encrypted_extensions,\#{sni => {sni,[]}}}}}'}}}]}}
    (dart_sass 0.5.0) lib/dart_sass.ex:384: DartSass.fetch_body!/1
    (dart_sass 0.5.0) lib/dart_sass.ex:231: DartSass.install/0
    (dart_sass 0.5.0) lib/dart_sass.ex:210: DartSass.install_and_run/2
    (dart_sass 0.5.0) lib/mix/tasks/sass.ex:47: Mix.Tasks.Sass.install_and_run/1
    (mix 1.13.4) lib/mix/task.ex:397: anonymous fn/3 in Mix.Task.run_task/3
    (mix 1.13.4) lib/mix/task.ex:455: Mix.Task.run_alias/5
    (mix 1.13.4) lib/mix/cli.ex:84: Mix.CLI.run_task/2

Docker image tag is hexpm/elixir:1.13.4-erlang-<IP_ADDRESS>-ubuntu-focal-20211006.
Update to add: may be related to https://elixirforum.com/t/github-ci-down-is-it-working-for-you/49661 ?

@jamesvl Thanks for the report!
I pushed a commit to restrict the TLS version to 1.2 on OTP releases < 25. I will publish a new release but in the meantime you can pull from GitHub:
def deps do
  [
    {:dart_sass, github: "CargoSense/dart_sass", branch: "mc-tls", override: true},
    ...
  ]
end

v0.5.1 has been released :)

FYI, this fix may no longer be needed once this fix is present in OTP 24: https://github.com/erlang/otp/issues/6241

Good to note, thank you!


Compiling with RTX 2070 Super

when i try to compile the with DLIB_USE_CUDA=ON
i have the following issue:
Found cuDNN: /usr/lib/x86_64-linux-gnu/libcudnn.so
Building a CUDA test project to see if your compiler is compatible with CUDA...

*** CUDA was found but your compiler failed to compile a simple CUDA program so dlib isn't going to use CUDA.
*** The output of the failed CUDA test compile is shown below:
***   Change Dir: /home/luiz/Libraries/CPP/dlib/build/dlib/cuda_test_build

***   Run Build Command:"/usr/bin/make"
***   [ 50%] Building NVCC (Device) object CMakeFiles/cuda_test.dir/cuda_test_generated_cuda_test.cu.o
***   In file included from /usr/include/host_config.h:50:0,
***                    from /usr/include/cuda_runtime.h:78,
***                    from :0:
***   /usr/include/crt/host_config.h:121:2: error: #error -- unsupported GNU version! gcc versions later than 6 are not supported!
***    #error -- unsupported GNU version! gcc versions later than 6 are not supported!
***     ^~~~~
***   CMake Error at cuda_test_generated_cuda_test.cu.o.cmake:215 (message):
***     Error generating
***     /home/luiz/Libraries/CPP/dlib/build/dlib/cuda_test_build/CMakeFiles/cuda_test.dir//./cuda_test_generated_cuda_test.cu.o

***   CMakeFiles/cuda_test.dir/build.make:63: recipe for target 'CMakeFiles/cuda_test.dir/cuda_test_generated_cuda_test.cu.o' failed
***   make[2]: *** [CMakeFiles/cuda_test.dir/cuda_test_generated_cuda_test.cu.o] Error 1
***   CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/cuda_test.dir/all' failed
***   make[1]: *** [CMakeFiles/cuda_test.dir/all] Error 2
***   Makefile:83: recipe for target 'all' failed
***   make: *** [all] Error 2

I'm using libcudnn 8 and cuda 11

i fix it, i only downgrade my cudnn version and my cuda version.
now i'm using libcudnn 7.6 and cuda 10.1


Every command, same error - "Should not be run as root, please retry without sudo."

hotel shows on Linux (Ubuntu) the following message, independent of the command typed:
Should not be run as root, please retry without sudo.
However, it's not running as root, nor is it started with sudo. Also all NPM and .hotel files belog to the normal user, not root.
The log file daemon.log contains no useful hints.
Any idea what else could I try ?
Thank you.

Try this which hotel or install hotel locally.

@indrakaw Thanks for your help. It seems this problem is present only in zsh+oh-my-zsh . Reverting back to classical bash makes the problem disappear. I looks like oh-my-zsh breaks just too many applications :( .

Okay then.
I'm using zsh + oh-my-zsh and having no problem. It seems there is a conflict on oh-my-zsh plug-ins. Try to disable it.


Assignment of license under MIT license

@cybik @salamanderrake, I'm trying to make sure this code is under the mit license.
Can you reaffirm that what both of you wrote as assigned to me under mit license?

Yes I can affirm what I wrote to you is under the MIT license.
On 04/07/2015 09:31 PM, K. S. Ernest (iFire) Lee wrote:

@cybik https://github.com/cybik @salamanderrake
https://github.com/salamanderrake, I'm trying to make sure this code
is under the mit license.
Can you reaffirm that what both of you wrote as assigned to me under mit
license?
—
Reply to this email directly or view it on GitHub
https://github.com/fire/QtCreatorSourceCodeAccess/issues/7.

I hereby affirm it.

Closed.


Cannot login after run command "npm run preview"

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Framework version: vue : 3.2.31
Browser: chrome104.0.5112.81

Extra info
When run command "npm run dev" there is able to login, but  command build and preview is cannot to login.
运行命令“npm run dev”时可以登录，但运行命令构建和预览无法登录。

@EricDoZen hi ~ 构建和预览是需要调用真实接口的。如果你仅仅是想看打包效果，你得判断环境把mock数据加入进去。

@EricDoZen hi ~ 构建和预览是需要调用真实接口的。如果你仅仅是想看打包效果，你得判断环境把mock数据加入进去。

If so, which file do I need to add mock data to? Do you have an example? which files need to be edited and where to edit or what code to add?
如果是这样，我需要将模拟数据添加到哪个文件？ 你有一个例子吗？ 哪些文件需要编辑，在哪里编辑或添加什么代码？

@EricDoZen You can try to refer to this issue. link

@EricDoZen You can try to refer to this issue. link

I try the link But I don't quite understand what to do with the setup-mock.ts file. What am I going to do with this part of the code?
if (mock !== false && debug) setup();
我试试链接 但我不太明白如何处理 setup-mock.ts 文件。 我应该如何处理这部分代码？
if (mock !== false && debug) setup();

@EricDoZen You can try to refer to this issue. link

From this

@AlienegraGeek hi 。如果你只想单纯打包部署看看。那你就要把
https://github.com/arco-design/arco-design-pro-vue/blob/1cdd29a8f731bc86303fa0c32f25626eab103ab5/arco-design-pro-vite/src/utils/setup-mock.ts#L4
这部分给修改一下。否则mock在生成环境不会生效。如果你有自己的接口，你就要在nginx做一层proxy，代理到自己接口所在的地址。

好的，感谢，已经解决了，我发现是由于.env.production内没有定义VITE_API_BASE_URL，我定义之后，再将.env.development中的VITE_API_BASE_URL去掉，就可以调通自己的接口了

The .env.development file defaults is VITE_API_BASE_URL= 'http://localhost:8080/'.
and I went to edit the file .env.production by adding
VITE_API_BASE_URL= 'http://localhost:8080/' but still unable to login.

@EricDoZen If you just want to pack mock data. if (mock !== false && debug) setup();  >>>if (mock !== false) setup();

@EricDoZen If you just want to pack mock data. if (mock !== false && debug) setup();  >>>if (mock !== false) setup();

It work, Thanks!


Potential Security Issue

👋 Hello, we've received a report for a potential critical severity security issue in your repository.
Next Steps
1⃣  Visit https://huntr.dev/bounties/1-other-OWASP/RiskAssessmentFramework for more advisory information.
2⃣  Sign-up to validate or speak to the researcher for more assistance.
3⃣ Propose a patch or outsource it to our community.

Confused or need more help?

Join us on our Discord and a member of our team will be happy to help! 🤗

Speak to a member of our team: @JamieSlome

This issue was automatically generated by huntr.dev - a bug bounty board for securing open source code.

I am willing to work the fix, is this repo alive?


What is the 4th column?

In the data, what's the 4th column for? I mean the the lorem one.
['2002', '09/2002', 'A freaking awesome time', 'lorem'],
May be good to add it to the readme
Thanks for making this fun visualization tool!

It is class that is added to bubble, in that case it is bubble-lorem.

Thanks!


Check if recaptcha messes with Apple Pay

And if so, figure out what we need to do to compensate for it.

I think this is good now, but let's watch the logs and make sure. Hopefully there'll be fewer recaptcha errors

Well it wasn't fixed, but after f0e33416ca387707f238d54888710a065c4be920 hopefully it is.


Remove mutability requirement from SubsystemHandle::start

Start doesn't require mutability so we can remove that restriction. This way the subsystem handle can
be shared by cloning it directly without having to wrap it in a type that provides mutability.

In code that already uses this crate with the wildcard "0.4" version, this will now produce warnings that weren't there before. Nonetheless it is well-defined and not an actual error, it will just warn about unnecessary "mut"s.
I don't think this already counts as an API-breaking change, so I would release this as 0.4.4.
Do you agree, or do you think this should be a 0.5?

I think releasing it as 0.4.4 is fine. I think those warnings can be seen as deprecation hints so semver is fulfilled.


Leverage builder_params for assigning ems_id to each relevant object

Leverage builder_params for assigning ems_id to each relevant object

@miq-bot assign @agrare

@miq-bot add_label enhancement

@mansam something that can cause failure in OpenStack graph refresh, you should leverage this instead of assigning :ext_management_system in the parser

@Ladas I've been using :builder_params => {:ext_management_system => manager}. Is that still permissible, or do I need to change that?

@mansam that will work now, but we are working now on serialize/deserialize the data, so the collector+parser can be separated from a persistor and we can have multiple persistors just reading data from a queue.
And the current to_yaml/from_yaml can't deal with the AR objects. Which is something we could add in the future though. The to_yaml, from_yaml methods are on a persitor object now.

Got it. I'll use this pattern going forward, and when I have a chance I'll redo the existing openstack graph refresh stuff to use it as well.


riscv64

Part of https://github.com/iree-org/iree/issues/9855

This could use a more descriptive PR title ;P

This could use a more descriptive PR title ;P

Whoops, done


Text cardinality for section:lab-no-subsections

From Description & Constraints of section:lab-no-subsections "Variant 1: EU Laboratory Report section with text and entry" it seams that the text must be present but text is indicated as optional. Is it correct?

I agree we need to make description and rules coherent


 elements no longer styled by default in v3 when used in expression

Describe the bug In nextra@2, the native
 elements and its associated nodes, e.g.
,
, ,  have opinionated styles, which allows us to use the actual
 tags in MDX and still get the same appearance as the markdown table.
However, in nextra@3, the
 element is no longer styled if and only if it is generated as a JSX expression:
// This works

      Column 1
      Column 2

      Row 1
      Lorem
      ipsum

      Row 2
      Dolor
      sit

// This doesn't
{

      Column 1
      Column 2

      Row 1
      Lorem
      ipsum

      Row 2
      Dolor
      sit

}

This is potentially problematic as we have dynamically generated tables in our documentation, which appear unstyled after the upgrade to v3.
To Reproduce Steps to reproduce the behavior:
Create a HTML table using JSX expression:
{

  // Rest of the table content here

}

Expected behavior A
 inside curly brackets should render just like a regular
 in the MDX file.
Screenshots

Desktop (please complete the following information):

OS: macO
Browser Google Chrome
Version 130.0.6723.70

this is a new MDX3.1 behaviour, a place to complain https://github.com/mdx-js/mdx/issues/2549

Thanks for the reply @dimaMachina :)

Feel free to send a PR