Plugin id different from npm package name

When i install the plugin from npm it keep installing everytime i run cordova prepare:
Discovered plugin "cordova-fabric-plugin" in config.xml. Installing to the project Fetching plugin<EMAIL_ADDRESS>via npm Plugin "com.sarriaroman.fabric" already installed on android. Plugin "com.sarriaroman.fabric" already installed on ios.
I installed the plugin adding this in my config.xml:
    <plugin name="cordova-fabric-plugin" spec="~1.0.5">         <variable name="FABRIC_API_KEY" value="xxx" />         <variable name="FABRIC_API_SECRET" value="xxx" />     </plugin>
In plugin.xml i see the id is:
<plugin id="com.sarriaroman.fabric" version="1.0.5" xmlns="http://www.phonegap.com/ns/plugins/1.0">
I think this is because the plugin id is different from the npm package name.
Is it reasonable to change the plugin id to cordova-fabric-plugin?

Fixed on version 1.0.6. Feel free to close the issue once you made some try.

Solved with version 1.0.7


HasMany improvements

Setting a has many array with the same array must not trigger its observers
Loading collections with same element twice must not trigger observers

We solved this issues in our fork to avoid a huge Ember component from being re-drawn and also prevents the collections from being dirty when there have been no changes, which means less http requests.
Thanks for the lib!

Any way this can be reviewed?


[SUGGESTION] Add missing resources pop up (like LTN)

It would be nice if the feature parity with LTN would be increased. There is currently no message that indicates if a network does not contain a requested item. This is handy to know what resources need to be added to the train network.
example:

an actual gui manager instead is being worked on


Don't save evaluated current_timestamp into table meta mapping

create table t (ts as current_timestamp) created a
_meta.generated_columns mapping which contained the actual evaluated
timestamp instead of the function name.
This commit changes the ExpressionAnalyzer behavior to not eagerly
evaluate current_timestamp. Instead normalizeSymbol does that.
A new StatementContext is used to ensure multiple current_timestamp
occurrences within a statement all result in the same value.

@dobe please review

Igtm otherwise


Expand git urls using git remote get-url

I use insteadOf settings for all of my repositories to ensure that I clone over HTTPS, but push over SSH. It seems that citop is not expanding these.

Glancing at the go-git docs, it seems to be a limitation that isn't supported in the library at all. I've filed an issue for the library (linked above).

Thanks for reporting this and filing the issue for go-git. Until this gets fixed I'll probably call the local git executable to do the expansion. I don't have time to implement this right now but I'll work on it next week.

There is a fix for this on master. I also made a pre-release with pre-built binaries: https://github.com/nbedos/cistern/releases/tag/0.2.0dev0
Let me know if it fixes the issue or not.

This seems to fix it. Thanks!


Explore how we can make test discovery more automatic

Based on https://github.com/microsoft/vscode/issues/210152
Right now we require manual configuration for test discovery to be performed, but are there ways we can make it more automatic?
I believe there are currently a few challenges:
1- we don't know which framework the tests should be configured with, and there may be a lot of different configs and arguments that people need to pass so tests can successfully be discovered. If we tried to something automatically without requiring user config, most likely  we would show a failure on the test view.
2- pytest needs to be installed in user's environment for it to perform discovery. When people configure their tests to use pytest and it's not installed, we automatically install it on their behalf. We ofc can't do that automatically on load though, so we'd need to figure out a way to handle that part.
3- Some users who are running tests in the terminal are not using the same environment as the one we select for the workspace, which can also cause some confusion if we tried to do discovery automatically, as we'd likely fail due to the wrong environment being selected, even though running tests in the terminal succeeds. It's a problem that already exists, but since we don't open the test view by default nor try to perform discovery automatically, it's less noticeable
In any case, this is likely currently blocked by   https://github.com/microsoft/vscode-python/issues/21845 and potentially https://github.com/microsoft/vscode-python/issues/12075?

Thanks for creating this issue.

Could the test view show some "welcome experience" - so the user can choose the framework. Or could we detect the framework automatically based on workspace structure?
Could we do this from the test view? So not fully automatic, but to offer installing pytest to the user. Either via some contributed button (or if not possible, via a notification)

For #12075 is something needed from the VS Code side? Or you have all the testing api you need?
fyi @connor4312

One idea I had was to show an editor button (like the one we show in the launch.json, below) if the file matches the common test_*.py, *_test.py, etc. patterns and the user has not configured tests in their environment or dismissed the button.

Could the test view show some "welcome experience" - so the user can choose the framework. Or could we detect the framework automatically based on workspace structure?

Python does offer a welcome experience in that view when it's installed

One idea I had was to show an editor button (like the one we show in the launch.json, below) if the file matches the common test_*.py, *_test.py, etc. patterns and the user has not configured tests in their environment or dismissed the button.

Could the test view show some "welcome experience" - so the user can choose the framework. Or could we detect the framework automatically based on workspace structure?

Python does offer a welcome experience in that view when it's installed

I like this idea of the pop-up on a test file- would it be possible to introduce something so the user could dismiss?

Currently the editor button only supports a single action. But you could have a 'configure later' option in the quickpick, or PR in support for multiple actions there https://github.com/microsoft/vscode/blob/cf7f91d9bbdb4787de5b2828e1ec956d05790926/src/vs/workbench/browser/codeeditor.ts#L171


action from Microsoft Translator V3 on standard logic app designer freezes in a loading page

Describe the Bug with repro steps
add an action in logic app standard workflow, choose any action from connector "Microsoft Translator V3" and it just keeps loading and freezes there and doesn't give any details to configure .
if we use fallback url it works there in old designer
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
chrome
Additional context
No response

customer wants to know why they can’t access the connector using the normal\new portal URL and should they keep using fallback url?

Could you share any updates please?

Hi @swakMS, @valentina-vallalta is helping look into this, we don't have any updates yet but are currently investigating.
We will provide an update here as soon as we have one, thanks for your patience.

This change will be a part of our next release, which should be live in all regions by EOD February 2nd


The chilipie-kiosk-v1.2.1.img.zip file appears to be corrupted

when I download the chilipie-kiosk-v1.2.1.img.zip file and try to unzip it is appears to be corrupted.

Extracting to "C:\Users\XXXXX\Documents\"
Use Path: yes   Overlay Files: no
Extracting chilipie-kiosk-v1.2.1.img
Error: Unable to extract "C:\Users\XXXXX\Documents\chilipie-kiosk-v1.2.1.img".

The size of the extracted file<PHONE_NUMBER>) does not match the uncompressed size<PHONE_NUMBER>) recorded in the Zip file.
Severe Error:  File size doesn't match uncompressed size.

Also check with 7-zip and it reports a CRC error.

Oh, rats. I was under the impression it decompressed fine, as others definitely have done so... let me check.

Odd, I just tried downloading the zip file from GitHub, and inflating with:

The default macOS archive utility
The Unarchiver
unzip from Brew

...and all of them finished without reporting errors. 😕
Can you run the Windows equivalent of:
$ md5 chilipie-kiosk-v1.2.1.img.zip
MD5 (chilipie-kiosk-v1.2.1.img.zip) = 5b885b686b5f83d13003f02189e980a5

and check that you get the same result?

I ran the Windows equivalent on the zip file (powershell version):
Get-FileHash -Path .\chilipie-kiosk-v1.2.1.img -Algorithm MD5
Algorithm       Hash

MD5             BAD950CE0DCAA627C3FCC4932874ABD4

sorry that was the actually image, here is the zip file data, looks the same to me
Algorithm       Hash

MD5             5B885B686B5F83D13003F02189E980A5

Have you tried whether the resulting image works?

I was using Etcher and it was complaining, but I just tried it again and it seems to copy to the SD card.  But when I plug it into the PI, ti boots up and starts things up but I get lots of FAILED items
EXT4-fs errors  .... bad extra_isize ...
....
Failed to start Braille Device Support
...
etc...

OK, so you're definitely getting a corrupt image on the SD card. But I'm also getting a different hash on the uncompressed image file:
MD5 (chilipie-kiosk-v1.2.1.img) = f883e43dce3a0477555fa4444e1853a3

I've uploaded the uncompressed image, please try downloading that directly, since it looks like there's something in the ZIP file that prevents it being uncompressed successfully on Windows.
Let me know if that helps.

That image appears to work, so thanks.  Not sure what is going on with the compressed version.  If you do get a new compressed version that you want me to try let me know.

OK, I'll try to make sure the "official ZIP" decompresses fine on all platforms for the next release!

@matthewwicks there's now a repackaged release of v1.2.1 that should work better on Windows.


Incorrect register field definitions in soc/usb_reg.h (IDFGH-11591)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
It looks like a few of the endpoint register field definitions in components/soc/esp32s3/include/soc/usb_reg.h are likely incorrect:
USB_D_XFERSIZEn
USB_D_XFERSIZE1, USB_D_XFERSIZE2, USB_D_XFERSIZE3, USB_D_XFERSIZE4, USB_D_XFERSIZE5, and USB_D_XFERSIZE6 are all defined as 0x7F, but it looks like these values should probably be 0x7FFFF.  The associated USB_D_XFERSIZE1_V definitions appear to be the same.  The value 0x7F appears to be correct for endpoint 0, but it seems like this value should be larger for other endpoints.  I suspect the value from endpoint 0 was incorrectly copied to the other endpoints.
The ESP32-S3 Technical Reference Manual unfortunately does not provide documentation for these registers.  However, the tinyusb code provided for the ESP32-S3 is explicitly using a value of 0x7FFFF instead of using these definitions from soc/usb_reg.h for this value.  It seems like the ESP32 USB core is based on a Synopsys core, and other vendors using synposys cores document these values as 0x7F for endpoint 0 but 0x7FFFF for other endpoints.
The USB_XFERSIZEn definitions (without a _D_ in the name) appear to have the same issue.
USB_D_MPSx
This value similarly seems incorrect for endpoints 1 through 6, and the values for endpoint 0 appear to have been incorrectly copied to other endpoints.  USB_D_MPS0 is correctly defined as 3, but for the other endpoints it looks like this value should be 0x7FF.
The comments describing the values for this field also appear incorrect: this comment describes the values for endpoint 0, but for all other endpoints this field should be set to the literal maximum packet size value.
Again, the tinyusb code for the ESP32 appears to be doing the right thing here, and simply ignoring the incorrect values for from soc/usb_reg.h
Note that the USB_MPSx definitions do appear to be correct: 3 for endpoint 0 and 0x7FF for other endpoints.
USB_D_PKTCNTx
As above, this is defined as 3 for all endpoints, and I suspect that this value is correct for endpoint 0 but should be larger for other endpoints.  Other vendors using synopsys USB cores document this value as 3 for endpoint 0, but 0x3FF for other endpoints.
I suspect the same issue exists for the USB_PKTCNTx values.

Hello @simpkins , yes, you're right.
This header file is automatically generated to describe all USB-OTG registers. As you noted, we don't use this definitions in our TinyUSB DCD layer.
We will fix these inaccuracies, when we implement new (DMA based) DCD layer


Extract preprocessor define directives from project automatically

Currently, if you have preprocessor defines set in your project, you need to manually move those over to the "Compile Flags" field in the settings dialog.  I believe the settings dialog is also global, and not project specific, so if you have multiple projects with different preprocessor defines, you will need to frequently switch them back and forth.

Hi,
Project preprocessor defines should be automatically extracted from your *.vcxproj or VS property-sheets.
There is no need to configure them manually.
Can you provide a simple test case, reproducing the issue ?

I'll work on a reduced test case.  I threw the plugin at an existing, code generated vcproj that I had handy, and it isn't in a state that I can make the whole thing public.
Here's a portion of my .vcxproj though (with lots of paths and defines removed).  I don't know for sure if this is an unusual snippet or perfectly normal...
`
<ClCompile>

  <PreprocessorDefinitions>WIN32_LEAN_AND_MEAN</PreprocessorDefinitions>

  <AdditionalIncludeDirectories>./source;p:/perforce/ThirdPartyExports/boost/export/1.5/1.5.5f20/includes</AdditionalIncludeDirectories>

`

The snippet seems OK at first glance. Should work.
It would really help if you could take some time and produce a vcxproj file that you can share with us, reproducing the issue.
I think there's more to it (the bug) than the snippet above...

Also, using version 1.4 (latest) of "Clang Power Tools" you can debug configuration issues using our new Verbose Mode option that you can enable from Settings.

fail_import.zip
Here's a reduced test case.  This was using an MSVC-14.0 (2015) project.  I got the same kinds of failures when I upgraded it to an MSVC-15.0 (2017) project.
Output from verbose mode follows...
Start Clang Compile
VERBOSE: CPU logical core count = 8
VERBOSE: Detected LLVM at C:\Program Files (x86)\LLVM\bin
VERBOSE: [INFO] Source directory: P:\perforce\sa\group\bcraig\experiments\autoprojtest\temp
VERBOSE: Scanning for .vcxproj files
VERBOSE: Found 1 projects
[ INFO ] WILL PROCESS PROJECTS:
autoprojtest_msvc-14.0.vcxproj
[ INFO ] 1. PROCESSING PROJECT P:\perforce\sa\group\bcraig\experiments\autoprojtest\temp\autoprojtest_msvc-14.0.vcxproj
VERBOSE: PCH not enabled for this project!
VERBOSE: Preprocessor definitions:
VERBOSE: Platform toolset: v141
VERBOSE: Additional includes:
VERBOSE: Detected Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio 14.0
VERBOSE: WinSDK version : 8.1
VERBOSE: Include directories:
VERBOSE: P:\perforce\sa\group\bcraig\experiments\autoprojtest\temp
VERBOSE: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include
VERBOSE: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include
VERBOSE: C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt
VERBOSE: C:\Program Files (x86)\Windows Kits\8.1\Include\um
VERBOSE: C:\Program Files (x86)\Windows Kits\8.1\Include\shared
VERBOSE: C:\Program Files (x86)\Windows Kits\8.1\Include\winrt
VERBOSE:
VERBOSE:
VERBOSE: Force includes:
VERBOSE: Processing 1 cpps
1: P:\perforce\sa\group\bcraig\experiments\autoprojtest\temp\source\main.cpp
P:\perforce\sa\group\bcraig\experiments\autoprojtest\temp\source\main.cpp:2:10: fatal error: 'foo.h' file not found
#include <foo.h>
^~~~~~~
1 error generated.
Got errors.
Done Clang Compile

Thanks for the attached project.
I immediately spotted the issue causing your problems: you have custom names for your project configurations, eg. win32U_debug, win64U_debug, etc.
We currently assume they are called: "Debug", "Release" .... oops!
Will fix this issue as soon as possible.
Thank you for bringing it to our attention.

The same bug also affects your submitted issue: #74

This functionality was just implemented here

This issue was fixed in version 1.5
https://marketplace.visualstudio.com/items?itemName=vs-publisher-690586.ClangPowerTools
Thank you for your feedback!


[camera][android] takePicture not completed after pausePreview

Hi! I found a bug on my android device. If you call _cameraController.takePicture() before calling _cameraController.pausePreview(), then the takePicture function will not complete.
Device: Redmi Note 8 Pro, Android 11
Expected results: the snapshot was saved successfully
Actual results: the function takePicture is not completed.

Code sample
The example is taken from https://docs.flutter.dev/cookbook/plugins/picture-using-camera and supplemented with a line await _controller.pausePreview(); before final image = await _controller.takePicture();
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.
            await _controller.pausePreview();
            final image = await _controller.takePicture();

            if (!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)),
    );
  }
}

Logs
[        ] An Observatory debugger and profiler on Redmi Note 8 Pro is available at: http://<IP_ADDRESS>:62833/Db369jd81Ig=/
[ +836 ms] E/ion     ( 7463): ioctl c0044901 failed with code -1: Invalid argument
[  +29 ms] The Flutter DevTools debugger and profiler on Redmi Note 8 Pro is available at: http://<IP_ADDRESS>:9102?uri=http://<IP_ADDRESS>:62833/Db369jd81Ig=/
[+2168 ms] I/BufferQueueConsumer( 7463): [](id:1d2700000000,api:0,p:-1,c:7463) connect(): controlledByApp=true
[  +23 ms] V/PhoneWindow( 7463): DecorView setVisiblity: visibility = 0, Parent = android.view.ViewRootImpl@9d812f7, this = DecorView@8d18564[MainActivity]
[  +13 ms] I/BufferQueueConsumer( 7463): [](id:1d2700000001,api:0,p:-1,c:7463) connect(): controlledByApp=true
[        ] W/Camera  ( 7463): The selected imageFormatGroup is not supported by Android. Defaulting to yuv420
[        ] I/BufferQueueConsumer( 7463): [](id:1d2700000002,api:0,p:-1,c:7463) connect(): controlledByApp=true
[   +3 ms] E/libc    ( 7463): Access denied finding property "persist.vendor.camera.privapp.list"
[   +7 ms] E/CameraManagerGlobal( 7463): Camera 61 is not available. Ignore physical camera status change
[   +5 ms] W/CameraManagerGlobal( 7463): ignore the torch status update of camera: 21
[        ] W/CameraManagerGlobal( 7463): ignore the torch status update of camera: 22
[        ] W/CameraManagerGlobal( 7463): ignore the torch status update of camera: 61
[   +3 ms] I/Camera  ( 7463): startPreview
[  +87 ms] I/BufferQueueProducer( 7463): [SurfaceTexture-0-7463-0](id:1d2700000000,api:4,p:845,c:7463) connect(): api=4 producerControlledByApp=true
[        ] I/BufferQueueProducer( 7463): [ImageReader-640x480f100m1-7463-0](id:1d2700000001,api:4,p:845,c:7463) connect(): api=4
producerControlledByApp=false
[   +5 ms] I/Camera  ( 7463): CameraCaptureSession onConfigured
[        ] I/Camera  ( 7463): Updating builder settings
[        ] D/Camera  ( 7463): Updating builder with feature: ExposureLockFeature
[        ] D/Camera  ( 7463): Updating builder with feature: ExposurePointFeature
[        ] D/Camera  ( 7463): Updating builder with feature: ZoomLevelFeature
[        ] D/Camera  ( 7463): Updating builder with feature: AutoFocusFeature
[        ] D/Camera  ( 7463): Updating builder with feature: NoiseReductionFeature
[        ] I/Camera  ( 7463): updateNoiseReduction | currentSetting: fast
[        ] D/Camera  ( 7463): Updating builder with feature: FocusPointFeature
[        ] D/Camera  ( 7463): Updating builder with feature: ResolutionFeature
[        ] D/Camera  ( 7463): Updating builder with feature: SensorOrientationFeature
[        ] D/Camera  ( 7463): Updating builder with feature: FlashFeature
[        ] D/Camera  ( 7463): Updating builder with feature: ExposureOffsetFeature
[   +1 ms] D/Camera  ( 7463): Updating builder with feature: FpsRangeFeature
[        ] I/Camera  ( 7463): refreshPreviewCaptureSession
[ +400 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[  +66 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[  +83 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[  +66 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[  +66 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[  +66 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[ +451 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[ +586 ms] I/mali_config( 7463): @get_buffer_dataspace_setting: update dataspace (0x10020000 -> 0x08020000)
[+2107 ms] I/r_application_( 7463): ProcessProfilingInfo new_methods=0 is saved saved_to_disk=0 resolve_classes_delay=8000
[ +378 ms] I/Camera  ( 7463): runPictureAutoFocus
[        ] I/Camera  ( 7463): lockAutoFocus
[   +7 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +7 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +7 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: null | aeState: null
[  +21 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +6 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +8 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: null | aeState: null
[  +18 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[  +11 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +7 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: null | aeState: null
[  +18 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[  +12 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +5 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: null | aeState: null
[  +14 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +6 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
[   +8 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: null | aeState: null
[  +24 ms] D/CameraCaptureCallback( 7463): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2

flutter doctor -v
[✓] Flutter (Channel stable, 3.3.3, on macOS 12.6 21G115 darwin-arm, locale en-AU)
    • Flutter version 3.3.3 on channel stable at /Users/ssheromova/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18a827f393 (3 weeks ago), 2022-09-28 10:03:14 -0700
    • Engine revision 5c984c26eb
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/ssheromova/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_HOME = /Users/ssheromova/Library/Android/sdk
    • Java binary at: /Users/ssheromova/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8815526/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Users/ssheromova/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8815526/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

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

[✓] Connected device (4 available)
    • Redmi Note 8 Pro (mobile) • rkda597hcqdm7pfq                     • android-arm64  • Android 11 (API 30)
    • iPhone 13 mini (mobile)   • 0093DF38-785E-4BCF-B58C-6AE49ED2D75D • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-0 (simulator)
    • macOS (desktop)           • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)              • chrome                               • web-javascript • Google Chrome 106.0.5249.119

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

• No issues found!

Hi @SofiSheromova, out of curiosity, why do you need to call pausePreview before takePicture?

In our flow, the user photographs the image, and then it is processed. During these actions, the user should see a frozen preview of the camera.
If we first call takePicture, and then display the resulting image, then this leads to delays (the photo is taken in maximum quality), which we want to avoid.

Thanks for the context.
Issue is reproducible using the code sample provided above. This is only an issue on android. iOS and web work just fine.
If you attempt to capture another image while it is not complete, you get
CameraException(Previous capture has not returned yet., takePicture was called before the previous capture returned.)

Labeling for further investigation.

logs
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
I/CameraManagerGlobal( 5205): Connecting to camera service
I/Choreographer( 5205): Skipped 85 frames!  The application may be doing too much work on its main thread.
E/SurfaceSyncer( 5205): Failed to find sync for id=0
W/Parcel  ( 5205): Expecting binder but got null!
D/EGL_emulation( 5205): app_time_stats: avg=52.66ms min=2.71ms max=218.40ms count=25
D/EGL_emulation( 5205): app_time_stats: avg=35.18ms min=11.44ms max=158.93ms count=26
D/EGL_emulation( 5205): app_time_stats: avg=23.87ms min=2.31ms max=87.00ms count=36
D/EGL_emulation( 5205): app_time_stats: avg=12.24ms min=2.97ms max=44.60ms count=53
D/EGL_emulation( 5205): app_time_stats: avg=6.81ms min=1.44ms max=34.99ms count=58
D/EGL_emulation( 5205): app_time_stats: avg=16.37ms min=1.95ms max=112.69ms count=45
D/EGL_emulation( 5205): app_time_stats: avg=16.61ms min=4.00ms max=121.31ms count=50
D/EGL_emulation( 5205): app_time_stats: avg=20.28ms min=2.07ms max=164.58ms count=38
D/EGL_emulation( 5205): app_time_stats: avg=19.73ms min=2.15ms max=149.66ms count=42
D/CompatibilityChangeReporter( 5205): Compat change id reported: 78294732; UID 10160; state: DISABLED
D/EGL_emulation( 5205): app_time_stats: avg=30.54ms min=2.44ms max=145.12ms count=27
D/CompatibilityChangeReporter( 5205): Compat change id reported: 206033068; UID 10160; state: DISABLED
W/Camera  ( 5205): The selected imageFormatGroup is not supported by Android. Defaulting to yuv420
I/Camera  ( 5205): startPreview
D/EGL_emulation( 5205): app_time_stats: avg=25.54ms min=2.75ms max=149.09ms count=31
I/Camera  ( 5205): CameraCaptureSession onConfigured
I/Camera  ( 5205): Updating builder settings
D/Camera  ( 5205): Updating builder with feature: ExposureLockFeature
D/Camera  ( 5205): Updating builder with feature: ExposurePointFeature
D/Camera  ( 5205): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 5205): Updating builder with feature: AutoFocusFeature
D/Camera  ( 5205): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 5205): updateNoiseReduction | currentSetting: fast
D/Camera  ( 5205): Updating builder with feature: FocusPointFeature
D/Camera  ( 5205): Updating builder with feature: ResolutionFeature
D/Camera  ( 5205): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 5205): Updating builder with feature: FlashFeature
D/Camera  ( 5205): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 5205): Updating builder with feature: FpsRangeFeature
I/Camera  ( 5205): refreshPreviewCaptureSession
D/EGL_emulation( 5205): app_time_stats: avg=111.46ms min=14.22ms max=569.67ms count=9
D/EGL_emulation( 5205): app_time_stats: avg=35.85ms min=9.23ms max=61.77ms count=28
D/EGL_emulation( 5205): app_time_stats: avg=34.93ms min=17.11ms max=55.91ms count=29
D/EGL_emulation( 5205): app_time_stats: avg=39.79ms min=8.96ms max=130.20ms count=23
D/EGL_emulation( 5205): app_time_stats: avg=33.67ms min=13.93ms max=50.88ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.87ms min=28.47ms max=50.20ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.87ms min=29.08ms max=52.03ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.89ms min=18.69ms max=50.28ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.90ms min=26.43ms max=51.15ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.86ms min=28.71ms max=54.94ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.81ms min=17.73ms max=51.07ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.81ms min=17.22ms max=52.23ms count=30
I/com.example.hs( 5205): Background concurrent copying GC freed 32137(1807KB) AllocSpace objects, 3(60KB) LOS objects, 49% free, 2721KB/5442KB, paused 440us,93us total 235.518ms
D/EGL_emulation( 5205): app_time_stats: avg=37.37ms min=7.95ms max=71.92ms count=27
D/EGL_emulation( 5205): app_time_stats: avg=33.94ms min=11.04ms max=53.79ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=38.79ms min=16.51ms max=76.00ms count=26
D/EGL_emulation( 5205): app_time_stats: avg=34.31ms min=7.94ms max=57.02ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=33.78ms min=14.94ms max=50.76ms count=30
D/EGL_emulation( 5205): app_time_stats: avg=52.07ms min=30.53ms max=498.90ms count=25
I/Camera  ( 5205): runPrecaptureSequence
I/Camera  ( 5205): refreshPreviewCaptureSession
D/CameraCaptureCallback( 5205): CameraCaptureCallback | state: STATE_WAITING_PRECAPTURE_START | afState: 0 | aeState: 2
D/CameraCaptureCallback( 5205): CameraCaptureCallback | state: STATE_WAITING_PRECAPTURE_DONE | afState: 0 | aeState: 2
I/Camera  ( 5205): captureStillPicture
D/Camera  ( 5205): Updating builder with feature: ExposureLockFeature
D/Camera  ( 5205): Updating builder with feature: ExposurePointFeature
D/Camera  ( 5205): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 5205): Updating builder with feature: AutoFocusFeature
D/Camera  ( 5205): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 5205): updateNoiseReduction | currentSetting: fast
D/Camera  ( 5205): Updating builder with feature: FocusPointFeature
D/Camera  ( 5205): Updating builder with feature: ResolutionFeature
D/Camera  ( 5205): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 5205): Updating builder with feature: FlashFeature
D/Camera  ( 5205): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 5205): Updating builder with feature: FpsRangeFeature
I/Camera  ( 5205): sending capture request
D/CameraCaptureCallback( 5205): CameraCaptureCallback | state: STATE_CAPTURING | afState: 0 | aeState: 5
I/Camera  ( 5205): unlockAutoFocus
I/Camera  ( 5205): refreshPreviewCaptureSession
I/Camera  ( 5205): open | onDisconnected
I/Camera  ( 5205): close
I/Camera  ( 5205): CameraCaptureSession onClosed
W/MessageQueue( 5205): Handler (android.os.Handler) {1d9fae} sending message to a Handler on a dead thread
W/MessageQueue( 5205): java.lang.IllegalStateException: Handler (android.os.Handler) {1d9fae} sending message to a Handler on a dead thread
W/MessageQueue( 5205): 	at android.os.MessageQueue.enqueueMessage(MessageQueue.java:560)
W/MessageQueue( 5205): 	at android.os.Handler.enqueueMessage(Handler.java:778)
W/MessageQueue( 5205): 	at android.os.Handler.sendMessageAtTime(Handler.java:727)
W/MessageQueue( 5205): 	at android.os.Handler.sendMessageDelayed(Handler.java:697)
W/MessageQueue( 5205): 	at android.os.Handler.post(Handler.java:427)
W/MessageQueue( 5205): 	at android.hardware.camera2.impl.CameraDeviceImpl$CameraHandlerExecutor.execute(CameraDeviceImpl.java:2353)
W/MessageQueue( 5205): 	at android.hardware.camera2.utils.TaskDrainer.postDrained(TaskDrainer.java:202)
W/MessageQueue( 5205): 	at android.hardware.camera2.utils.TaskDrainer.checkIfDrainFinished(TaskDrainer.java:197)
W/MessageQueue( 5205): 	at android.hardware.camera2.utils.TaskDrainer.beginDrain(TaskDrainer.java:185)
W/MessageQueue( 5205): 	at android.hardware.camera2.utils.TaskSingleDrainer.beginDrain(TaskSingleDrainer.java:87)
W/MessageQueue( 5205): 	at android.hardware.camera2.impl.CameraCaptureSessionImpl$SequenceDrainListener.onDrained(CameraCaptureSessionImpl.java:946)
W/MessageQueue( 5205): 	at android.hardware.camera2.utils.TaskDrainer.lambda$postDrained$0$android-hardware-camera2-utils-TaskDrainer(TaskDrainer.java:207)
W/MessageQueue( 5205): 	at android.hardware.camera2.utils.TaskDrainer$$ExternalSyntheticLambda0.run(Unknown Source:2)
W/MessageQueue( 5205): 	at android.os.Handler.handleCallback(Handler.java:942)
W/MessageQueue( 5205): 	at android.os.Handler.dispatchMessage(Handler.java:99)
W/MessageQueue( 5205): 	at android.os.Looper.loopOnce(Looper.java:201)
W/MessageQueue( 5205): 	at android.os.Looper.loop(Looper.java:288)
W/MessageQueue( 5205): 	at android.os.HandlerThread.run(HandlerThread.java:67)
I/Camera  ( 5205): open | onClosed
D/EGL_emulation( 5205): app_time_stats: avg=1555.75ms min=12.81ms max=12020.17ms count=8
I/flutter ( 5205): CameraException(Previous capture has not returned yet., takePicture was called before the previous capture returned.)
D/EGL_emulation( 5205): app_time_stats: avg=428.47ms min=1.58ms max=4981.90ms count=13
I/flutter ( 5205): CameraException(Previous capture has not returned yet., takePicture was called before the previous capture returned.)

flutter doctor -v
[✓] Flutter (Channel stable, 3.3.4, on macOS 12.6 21G115 darwin-arm, locale en-GB)
    • Flutter version 3.3.4 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (13 days ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

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

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

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

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview 2.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9014738/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

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

[✓] Connected device (5 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 13 (API 33) (emulator)
    • Nexus (mobile)              • 00008020-001875E83A38002E            • ios            • iOS 16.0.2 20A380
    • iPhone 14 Pro (mobile)      • 4302007A-B132-4B89-887A-C5993FCA3284 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-0 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 106.0.5249.119
    ! Error: Nexus is busy: Fetching debug symbols for Nexus. Xcode will continue when Nexus is finished. (code -10)

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

! Doctor found issues in 2 categories.

[✓] Flutter (Channel master, 3.5.0-8.0.pre.31, on macOS 12.6 21G115 darwin-arm64, locale en-GB)
    • Flutter version 3.5.0-8.0.pre.31 on channel master at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0ad71e8727 (11 hours ago), 2022-10-18 10:06:30 +0800
    • Engine revision 465ccd2974
    • Dart version 2.19.0 (build 2.19.0-314.0.dev)
    • DevTools version 2.18.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

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

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

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

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview 2.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9014738/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

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

[✓] Connected device (5 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 13 (API 33) (emulator)
    • Nexus (mobile)              • 00008020-001875E83A38002E            • ios            • iOS 16.0.2 20A380
    • iPhone 14 Pro (mobile)      • 4302007A-B132-4B89-887A-C5993FCA3284 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-0 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 106.0.5249.119
    ! Error: Nexus is busy: Fetching debug symbols for Nexus. Xcode will continue when Nexus is finished. (code -10)

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

! Doctor found issues in 2 categories.

@camsim99

The same bug on Android 12 (Pixel 5a device)

@danagbemava-nc I ran into the same problem. My initial thought was that this method pausePreview should actually be used to preview the image before shooting, so that we don't have to worry about cleaning up the file if the user wants to retake the shot. Also it would help to avoid the delay while processing the image. So this is definitely a weird behaviour. I would appreciate if you could somehow prioritise this issue or at least provide some information that you are or are not going to work on it. Thank you in advance!

I can reproduce it with my Pixel 6. Are there any workarounds for this issue? 😢

This issue should be fixed in the CameraX implementation of the camera plugin. If you try it out and find a similar issue with that implementation, please file a separate issue!


Fixed a bug where Array columns were inconsistent in Expand.

What is the necessity of this update? What is updated?
Fixed a bug where Array columns were inconsistent in Expand.
I think this is a fatal bug because it does not allow data to be acquired properly.
How did you do the test? (Not required for updating documents)
Fixed unit tests and added patterns.
I confirmed that the unit test did not pass with the code before modification.
[ERROR] Failures:
[ERROR]   TestArrayColumn.T_load_withAllIndexWithNull:357 expected: <4> but was: <7>
[ERROR]   TestArrayColumn.T_load_withOddNumberIndexAndExpand:629->checkExpandArray:224 expected:  but was:
[ERROR]   TestArrayColumn.T_load_withOddNumberIndex:469->checkExpandArray:224 expected:  but was:
[ERROR]   TestArrayColumn.T_load_withOutOfBoundsIndexAndExpand:595 expected: <13> but was: <14>
[ERROR]   TestArrayColumn.T_load_withOutOfBoundsIndex:435 expected: <13> but was: <14>
[ERROR] Errors:
[ERROR]   TestArrayColumn.T_load_withLast2IndexAndExpand:577->checkExpandArray:224 NullPointer
[ERROR]   TestArrayColumn.T_load_withLast2Index:417->checkExpandArray:224 NullPointer

LGTM


hyprpm: add glaze dependency FetchContent fallback

Use FetchContent to retrieve glaze dependency if not available with find_package.
Allows to build hyprpm w/o installing glaze at system level (on some distros is not available in official repositories).
Inspired from glaze documentation (ref. https://github.com/stephenberry/glaze?tab=readme-ov-file#see-this-example-repository-for-how-to-use-glaze-in-a-new-project and https://github.com/stephenberry/glaze_example/blob/main/CMakeLists.txt), let me know if there's a better way to achieve that.

w/o QUIET this warning is printed:
CMake Warning at hyprpm/CMakeLists.txt:14 (find_package):
  By not providing "Findglaze.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "glaze", but
  CMake did not find one.

  Could not find a package configuration file provided by "glaze" with any of
  the following names:

    glazeConfig.cmake
    glaze-config.cmake

  Add the installation prefix of "glaze" to CMAKE_PREFIX_PATH or set
  "glaze_DIR" to a directory containing one of the above files.  If "glaze"
  provides a separate development package or SDK, be sure it has been
  installed.

imho the status message is enough, less verbose and similar to other msgs:
-- Checking for module 'hyprland-protocols>=0.4.0'
--   Package 'hyprland-protocols' not found
-- hyprland-protocols subproject set to subprojects/hyprland-protocols

...

-- glaze dependency not found, retrieving v4.2.3 with FetchContent

fair enough


General Issue: Numbered unit tests

Background Information
Numbering the test units so that it's consistent across all of the test.

Definition of Done
No response

I'm putting this issue into a discussion https://github.com/pharmaverse/admiral/discussions/2453 as it might be part of a larger update


[WIP] Move to Apache Commons Compress

Handles Zip64
DO NOT MERGE
fixes #1105

Decided against this. No need to change the core ZIP library for an edge case.


Remove final solc invocation from solc_download.sh

$GITHUB_PATH is updated, but that doesn't take effect in the same script that updates it.
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path
This probably works for people who already have e.g. $HOME/.local/bin on their $PATH, but that's not generally true.

It's exactly what I needed, thanks!
      - name: Setup Solc
        if: steps.changed-sol-files.outputs.any_changed == 'true'
        uses: pontem-network/get-solc@f67593db4487ac96b4bf8031123a6deefc399b2e
        with:
          version: v${{ env.SOLC_VERSION }}


Setup Cog CI/CD

Have to handle customized version of cog to allow more environment variables.

https://github.com/replicate/cog/pull/1288 merged in
Waiting for stablization/reelease


HTTP Send example fails with SEGV on connection refused

When running the program in samples/http/sender, if the sender gets connection refused from the sink, a SIGSEGV occurs.
❯ ./sender
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7d61fb]

goroutine 1 [running]:
main.main()
	/home/lanceball/src/github.com/cloudevents/sdk-go/samples/http/sender/main.go:48 +0x56b

The example code uses res.IsUndelivered() to check if the event has been delivered. Comments for IsUndelivered() say
// IsUndelivered true means the target result is not an ACK/NACK, but some other
// error unrelated to delivery not from the intended recipient. Likely target
// is an error that represents some part of the protocol is misconfigured or
// the event that was attempting to be sent was invalid.

It seems, client.Send() should be returning a plain error when getting connection refused, which is neither ACK nor NACK, but is not.

Maybe @n3wscott can help you with this one?

I noticed this too - the connection refused is wrapped in aReceipt here: https://github.com/cloudevents/sdk-go/blob/9f80fd3a004fcabea03987db1fdfcb324deef14e/v2/protocol/http/protocol_retry.go#L38
IsUndelivered checks if it's an ACK or NACK via errors.Is which checks the ACK boolean: https://github.com/cloudevents/sdk-go/blob/9f80fd3a004fcabea03987db1fdfcb324deef14e/v2/protocol/result.go#L103
Obviously bool can only be true or false, so any Receipt would always be detected as an ACK or NACK by IsUndelivered.
The doc for Receipt even says it's intended for ACK or NACK: https://github.com/cloudevents/sdk-go/blob/9f80fd3a004fcabea03987db1fdfcb324deef14e/v2/protocol/result.go#L78-L79
Therefore I believe the error shouldn't be a Receipt (Receipt should only be used if we get an actual HTTP status code back). If it's changes to any other instance of Result (which is just a type alias for error), then IsUndelivered would return true.


IsModal doesn't seem to have an effect

View:
<simpleChildWindow:ChildWindow x:Class="Views.InviteWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:system="clr-namespace:System;assembly=mscorlib"
        xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
        xmlns:simpleChildWindow="clr-namespace:MahApps.Metro.SimpleChildWindow;assembly=MahApps.Metro.SimpleChildWindow"
        Title="Invite New User" Height="200" Width="300" IsModal="True">

Calling code:
                var inviteWindow = new InviteWindow(emailAddress);
                var mainWindow = Application.Current.MainWindow as MainWindow;
                await mainWindow.ShowChildWindowAsync(inviteWindow);

With the above code I get the window appearing centered on the page. It does not cover the app with a translucent surface and mouse events are working fine so I can continue to interact with the application.

Nevermind, this was caused by me specifying Height and Width instead of ChildWindowHeight and ChildWindowWidth.


How to do a Sum of a field in multiple documents?

Is there an easy way to return a sum of a value from a document field based on certain criteria?  For example, let's say I have the following documents defined:
Id | Name | List | HasAttachments | AttachmentCount
I want to return a single value that represents the Sum of AttachmentCount of the above documents where List = 1 and HasAttachments = true.
Thanks!

Hi @softwareguy74, there is no internal group by function in LiteDB. In this case you need use Linq to Object to do this:
db.Find(Query.EQ(...)).Sum(x => x["ValueToSum"].AsInt)

That worked like a charm, thanks!


Web: How to do multi-page development

How do I configure to develop multiple Web pages, instead of just having one index html?

You have to use a router.

Is there an example or document for reference? I can't find relevant API in the project.

I haven't tried this yet.  I found it by doing a search the right keywords.
https://github.com/hfhbd/routing-compose

Decompose seems also promising https://arkivanov.github.io/Decompose

I could try using HashRouter from routing-compose or Decompose to solve this problem temporarily, but it's still a SPA project and required more configuration at deployment time if using the history model.

What other solution have you used @korilin to solve this problem?

What other solution have you used @korilin to solve this problem?

I didn't try any other solutions.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Grouped Light Bulbs not working via Switch Tile

Description
I created a group of lights in my configuration then created a switch tile to control the multiple lights and when you click the tile it throws an API error and does nothing.
Environment
<What version of HACC are you running?>
0.6.0
<What environment is it? Hass.io on a Raspberry Pi 3B+? AMD64 Docker on Alpine 3.10?>
Docker via Supervisor on Ubuntu 18.04
Steps to Reproduce

Create Group of Lights
Create Switch tile in HACC
Click tile

Screenshots
System.Exception: Unexpected response code 400 from Home Assistant API endpoint /api/services/switch/turn_on.
   at HADotNet.Core.BaseClient.Post[T](String path, Object body, Boolean isRawBody)
   at HADotNet.Core.Clients.ServiceClient.CallService(String domain, String service, Object fields)
   at HADotNet.CommandCenter.Models.Config.Tiles.SwitchTile.OnClick(ServiceClient serviceClient) in /src/HADotNet.CommandCenter/Models/Config/Tiles/SwitchTile.cs:line 57
   at HADotNet.CommandCenter.Hubs.TileHub.OnTileClicked(String tileName) in /src/HADotNet.CommandCenter/Hubs/TileHub.cs:line 91
   at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.ExecuteHubMethod(ObjectMethodExecutor methodExecutor, THub hub, Object[] arguments)
   at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.<>c__DisplayClass13_0.<<Invoke>g__ExecuteInvocation|0>d.MoveNext()

Thanks for reporting this - will be released with version 1.0.


Change the way to write the custom ranking rules

Currently, we have 2 settings rankingRules and rankingOrder. These two settings will be merged into only one /ranking/rules.
The new custom ranking rules has always have the possibility of being ascending and descending. But the format has changed from attribute:asc/attribute:dsc to asc(attribute)/ dsc(attribute).

closed by #441


STOP MERGING INTO STABLE!!!!!!

I'm TIRED OF SEEING IT! I was in a repo, right? And ALL OF THE PRs were merging into stable

so we merge into master when we make pr?

make the default branch master then
ez fix :trollface:


Elevate warnigns to errors on gcc and clang

Elevate warnigns to error on gcc and clang.
This sets our error level pretty high. CI will be an important part of this strategy working.

OK so @defiantnerd this makes the vst3 wrapper use all the warnings on mac and linux.
I think we should turn this on but it will mean broken CI sometimes since they warnings differ by platform. If you are comfy with that I am also. But I can see wanting to wait.
It would close #81 if we did it though, or at least close that then encourage someone to do same for MSVC.


Add sentry logging to Assessments app

Set up a project in sentry to catch errors from Assessments app.
Update UI to use project and environments.

@crablab have added you as an Admin in sentry so you can set up a Project for assessments app


https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/transformed_components

https://github.com/google/fonts/pull/4615
lists
“FAIL: Ensure component transforms do not perform scaling or rotation. (com.google.fonts/check/transformed_components)”
and the link is:
https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/transformed_components
but the link goes to a page where “transformed” is nowhere to be found

This was fixed recently (see https://github.com/googlefonts/fontbakery/commit/7ea27c8ea79a93bb45572d2b5215cd18b7bf04d6 and #3677) and the change will be included in the upcoming v0.8.9 release.
In the mean time, change latest to stable on the readthedocs URL:
https://font-bakery.readthedocs.io/en/stable/fontbakery/profiles/universal.html#com.google.fonts/check/transformed_components

This is also related, though, to a known bug still pending a proper fix: #3770


(four of five) Add mathjax and fix docstring templating for various functions

Closing - these changes are now absorbed into the omnibus PR #453


ServiceCatalogApi-  getAvailableServicesTree mothod，The "links" attribute in the returned result is empty

"links" has a value in the result returned by the listAvailableService method, but getAvailableServicesTree  does not

@swaroopar @baixinsui  Do we need to set values for 'links' uniformly here?

@jinyangyang222 yes, we will have to keep it uniform.

I will fix it.


Fallback on error in datetime() before year 1970

Describe the bug
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Anaconda\python3\envs\***\lib\site-packages\maya\core.py", line 250, in datetime
    dt = Datetime.utcfromtimestamp(self._epoch)
OSError: [Errno 22] Invalid argument

when MayaDT.datatime() (calls utcfromtimestamp) with negative epoch MayaDT object.
Environment and Version

OS (incl. terminal and shell used): Powershell with Microsoft Windows 10 Home 10.0.19042
Python Version: 3.7.9
maya Version: 0.6.1
Your timezone: Japan Time (+09:00)

To Reproduce
( note that occured on Windows environment , but maybe not on Linux environment )
import maya
maya.when("1949-01-01").datetime()

Expected behavior
>>> import maya
>>> maya.when("1949-01-01").datetime()
datetime.datetime(1949, 1, 1, 0, 0, tzinfo=<UTC>)

thanks!


Doesn't work on Android 12 while app is terminated or in background

While code works perfectly fine when with Android 11 or below using fcm in all conditions (foreground, background, terminated) but in Android 12 and 13 app crashes on tested on multiple devices same problem Android just crash the app in terminated and background state works fine while foreground and since it's Android os error it doesn't leave any logs with it

Errors always leave logs. Check Android Studio's LogCat to get all error messages from all apps on any Android device.

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!


[Q] Continue reading from PIPE when out-of-sync

Hi @lelegard ,
I want to use tsp with PIPE input for STSDIN. But the process that sends the TS data, sometimes will insert some corrupted data. So, what I want is to overcome this discarding garbage until the next SYNC data (0x47). Then my questions are:

Wich parameter I need to continue reading if the input sync is out?
And wich parameter I need to use if the first data from the pipe is not a TS packet?

Now, the processing stops if the first data is not a valid TS packet. So please help me.
Thank you.

Hi,
I list here different reasons to support the "safe running in case of spurious data" optional mode in tsp:

When an external producer process generates some data that it isn't part of the TS stream, but it writes in the buffer/pipe. In this case, we can discard the data and continue.
When the input data is not in TS format data. In this case in the debug print we can see the data to identify the problem.
When multiple sources write to the same pipe, and we want to process the mix discarding non TS data.
When the input source exits and restarts connecting to the same pipe. In this case, we want to continue running discarding the closing of the pipe, or and small chunk of data not related with the TS stream.

I see almost some scenarios where this have sense. So please, consider to implement it. I can't see any side effect. You agree @lelegard ?
Regards.

Hi @lelegard ,
You think it's sufficient with any-process | tsresync | tsp ... support?
From my point of view, the teresync functionality could be good to be introduced inside the tsp INPUTS as a generic support.
But, perhaps I'm wrong. So I appreciate if you can comment what's the best way to overcome non-TS-packets in the flow.
Thank you for your patience.

Sorry,
My suggestion is more or less to add one option to convert this block:
https://github.com/tsduck/tsduck/blob/1f5c70798940033c666b4feeed4b9dcc6f104c17/src/libtsduck/plugin/private/tstspInputExecutor.cpp#L282
Into an optional warning. And instead of // Ignore subsequent packets continue reading forever.
Then using the tsresync tool or something similar in the tsp input we can handle the case when non-TS-data is present in the flow and we want to continue reading.
I feel this is KISS compatible and not very complex.
Regards.

It is not as simple as it seems.
"Continuing reading" is not only reading, it is analyzing the structure of input. Normally, an input plugin is responsible for providing TS packets. The code you point out is at tsp-level and simply checks that the input looks like valid TS packets. Some input plugins extracts packets from a "binary magma". This is the case for file  (multiple formats, determined in initial phase only), pcap, ip and srt (extracting TS packets from UDP datagrams using various encapsulations formats such as RTP but not only), dvb on Windows (because of experiences corruption or desynchronization in DirectShow), etc.
So, simply adding some resynchronization layer inside tsp is not correct because it does not take into account the work that was done upstream in the input plugin. For instance, in the file plugin, if a part of an M2TS file is corrupted, trying to resynchronize in tsp would be hopeless since the file plugin skips 4 bytes every 192 bytes. If the input is desynchronized and the input plugin continues to skip 4 bytes every 192 bytes, you will never get a correct stream in tsp, even with a resynchronization layer inside tsp.
So, all resynchronization work shall be done inside each input plugin, one by one, depending in the global binary format from which TS packets are extracted. Some plugins already do that such as datagram-based plugins (ip, srt). For all others, this must be addressed one by one, with various levels of difficulties. I have no plan to enter this for now.

Hi @lelegard ,
Thank you for the explanation. Now I understand the complexity of implementing this in a general way. However, I'm happy if some of the input plugins have almost some protection over potential spureous data.
However, for the particular case of PIPE inputs, why not provide a simple enhancement (for sure, pure optional)? At time, if the first byte is not 0x47 then it's impossible to start the processing. And I want to overcome this. So, I prefer to disable this check, and in case of any other non-TS-data, advance until the next valid TS packet.
Please, can you almost target this particular case? Without it, it's very complex to integrate TSDuck with external tools that use non-reliable sources.
Thank you!

However, for the particular case of PIPE inputs,

There is no pipe input, just the file plugin which also transparently handles pipes when the standard input is a pipe.

why not provide a simple enhancement (for sure, pure optional)? At time, if the first byte is not 0x47 then it's impossible to start the processing. And I want to overcome this. So, I prefer to disable this check, and in case of any other non-TS-data, advance until the next valid TS packet.

If you look at the documentation of the file input plugin and section 2.1.2 of the TSDuck user's guide, you will see that the plugin already handles non pure TS input files (see option --format). So, the plugin already analyzes the input data, trying to guess the actual file format. If you add the constraint that the input can be desynchronized or corrupted, that makes a double guess.

Please, can you almost target this particular case? Without it, it's very complex to integrate TSDuck with external tools that use non-reliable sources.

Use or write an adapter to make it reliable (if tsresync is not enough).

Hi @lelegard ,
Thank you another time. After much reading I continue with some questions. So please help me to understand this:

With the current implementation of the file input, why if the first byte is not a 0x47 sync byte the tsp process exits? Any idea to overcome this?

And regarding the use of the tsresync tool previous to the tsp:

Why we need to instantiate two buffers, and fill the first to just output the data to the second one? This increases a lot the delay. So I prefer if the code of the tsresync will be included (optionally, of course) inside the file input. I feel the code will be the same, or not?

Regards.

Why don't you just look at the code to understand the complexity?

Why don't you just look at the code to understand the complexity?

Please don't think that I don't try to understand as much as I can.
My current problem is that I'm using this to overcome the exit of the TSDuck if some non-TS-data outputs from the ingest process: external_process | tsresync -c -m 1318 -p 188 -s 13180 | tsp --realtime ...
However, the problem here is how to determine the best -m and -s values.

For the -m parameter, perhaps it's best to use 564 bytes. This assumption is because in order to guarantee a consistent TS synchronization, a three consecutive marks at 188 bytes in between, is the objective. So, what's the best value for a realtime flow?
More complex it the -sparameter. As I want to reduce the latency to the minimun, then I use here 10 * 7 * 188 bytes. But this generates troubles with VBR streams. If the souce process lost some packets at one point, then the flush of the packets is not done based on time (the buffer of -s is size-based controlled). Then the problem is here that the tsp process only receives a chunk of packets.

I can understand that maintain the simplicity it's a must in this project (and in general too). However, compared with the UDP network input, the file input is less reliable. So, for this reason I prefer to use the network streaming input, even using the loopback for interconnect two local processes. But the lack of event-control of subprocess from TSDuck (i.e. #757) makes impossible to execute a reliable_multiprocess_execution. You pointed a lot of times that you don't think it's a good idea to implement a subprocess plugin event manager. And this is acceptable. But, now we don't have a reliable filtered communication using PIPES. So, what's the solution?
Please, try to see the specific scenario to resolve: run more than one process, including tsp in the chain, as one unique flow, and exit only if a severe error occurs. So in the event of spurious data, the processing continues. And if only one process dies, then all the others exit. You have any suggestion to solve this particular use case?
Thank you for taking the time to answer so patiently all these questions.
Regards.


pc_align issue applying translation?

Hi Scott,
I just noticed some weird behavior using pc_align/bundle_adjust when applying transformations to pinhole cameras... I'm not sure if you or Oleg changed something recently?
Basically, in the previous release (before 5th Dec build), when I computed the inverse transform between my ASP DEM and a reference DEM, I got this:
cat trans1-inverse-transform.txt
0.9999670806654368 -0.007804132501920781 -0.002221058583527107    -44439.16512991776
0.007781477405351556    0.9999193979741426  -0.01003225619249146     15910.73616510996
0.002299172618327889    0.0100146428200877    0.9999472089737308     61848.27153707921
0                     0                     0                     1
And when I applied it to my cameras (using bundle_adjust with --max-iterations 0 and --initial-transform trans1-inverse-transform.txt), I got adjust files like this:
cat ba3-guatemala_53.adjust.orig
-38.7933010918040964 28.7340960958972573 -53.1627361173741519
0.999949095451905356 0.00834329141440272315 0.00473620600724225342 0.00312479534491459654
(these are good, and all is well in this case).
... HOWEVER, using the 5th Dec 2018 build, and with the exact same input files and commands, I get the following:
cat trans1-inverse-transform.txt
0.9999670806654368 -0.007804132501920781 -0.002221058583527107    -44439.16512991776
0.007781477405351556    0.9999193979741426  -0.01003225619249146     15910.73616510996
0.002299172618327889    0.0100146428200877    0.9999472089737308     61848.27153707921
0                     0                     0                     1
...this is the same as before, BUT(!) the adjust files are totally different:
cat ba3-guatemala_53.adjust
-44567.2228254281654 15888.8807767241487 61821.1216514268162
0.999949095451905356 0.00834329141440272315 0.00473620600724225342 0.00312479534491459654
It looks like bundle_adjust is doing something strange when applying the translation. The rotation part looks ok though.
Any thoughts?... maybe it's related to the changes you've been doing with bundle_adjust? It looks like pc_align is behaving normally.
Cheers,
James

Hi James,
Oleg noticed something wrong with bundle_adjust in the latest build, and added a fix that should be available. Hopefully that will fix the issue,
Cheers,
Amaury
On Dec 6, 2018, at 01:54, jchollingsworth <notifications<EMAIL_ADDRESS>wrote:
It looks like bundle_adjust is doing something strange when applying the translation. The rotation part looks ok though.

Sorry for not responding earlier. I will look at this early next week.

Scott fixed this and the latest build should have the fix.


Hosting multiple builds is broken

Describe the bug
Cannot host multiple entries.
Minimal reproduction
Steps to reproduce the behavior:

Go to documentation: https://sli.dev/guide/hosting#multiple-builds

Edit your build command in Vercel

Verify that the build works locally

Verify that the build fails and that no index is created.

To reproduce with code, see here:
https://github.com/onefact/talks.onefact.org (and see the dist directory from vite to see an example of how there is no index page from which to access multiple slide decks!)
Environment

Slidev version: latest (https://github.com/onefact/talks.onefact.org has the package-lock.json file if needed for specifics)
Browser: chrome / safari / firefox
OS: Sonoma 14.5 MBP

In fact, currently, Slidev doesn't create an index page for your slides. slidev build a.md b.md is the same as slidev build a.md --out dist/a/ && slidev build b.md --out dist/b/. In your repo, it seems that the dist directory wasn't cleared after previous builds.
About how to host multiple slides, this discussion may help: https://github.com/slidevjs/slidev/discussions/1777#discussioncomment-10126886


ginkgo:  [FAILED] Test Report unavailable because a Ginkgo parallel process disappeared

action url: https://github.com/spidernet-io/spiderpool/actions/runs/4526421734

This occurs if a parallel process exits before it reports its results to the Ginkgo CLI. The issue cannot be replicated locally, and it should be harmless.
During parallel testing, if panic occurs in certain specs, this error may be reported. However, during local testing, no panic occurs. Therefore, I believe that our test case should be correct, which should be considered as a minor issue with ginkgo. Don't close this issue, maybe it will happen again.

BTW, we can use --output-interceptor-mode=none to disable ginkgo from capturing stdout/stderr output to avoid test suite failures due to missing reports from related processes, but we should not do this because we need ginkgo's reports to debug.

#2009


When multiple choices are made, the order of the tags of the selected data will sometimes change when the page is refreshed. As a result, when a tag is deleted, the deleted ID is different

Duplicate of #20928

请把我这个issue删除吧 @cs1707

可以帮忙删掉我发的这个issue吗 @cs1707


Convert BigDecimal to Double by "doubleValue()" method, get a wrong result

Describe the bug
Unit Test:
  @Test
  fun testToDouble() {
    val result = "29514.9598393574297189".toBigDecimal().doubleValue()
    assertEquals(29514.9598393574297189, result)
  }

Output
expected:<29514.95983935743> but was:<0.1693214221471333>
Expected :29514.95983935743
Actual   :0.1693214221471333

To Reproduce
Steps to reproduce the behavior:

Operation
Values to reproduce issue

Expected behavior
A clear and concise description of what you expected to happen.
Platform

[e.g. JVM, JS, Native, iOS, Linux]

If JS (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

If Smartphone (please complete the following information):

Device: [e.g. Google Pixel 3]
OS: [e.g. Android 9.0]
Browser [e.g. Chrome]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

lib version: 0.3.3

I have not come across this warning from my Android Studio Chipmunk ｜ 2021.2.1

In addition, the above unit test can be passed if it is reduced by one digit, e.g. 29514.959839357429718
Thanks for your response!

Hi @JesseWo, I've fixed this issue and the fix will be in build 0.3.6 that is currently rolling out. There was a API change in version 0.3.4 that made doubleValue() explicitly require that the exact result is returned, unless you specify that you don't need exact result with doubleValue(false). The reason why we are now requiring is that a lot of people are unaware of the limitations in IEEE 754 double/float (which java and kotlin use)
A simple example would be to run this and observe it finishes successfully even though the numbers are different:
assertEquals(29514.9598393574297189, 29514.9598393574297194)


river: remove branwright1 as maintainer

Motivation for this change
Removed myself from maintainers in river and nixpkgs itself, I can't maintain this package anymore because there is no Wayland on macOS.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Thanks for the notice!


Let users download profiles as vCards

Users can now download a simple vCard for profiles they visit. This is implemented as a new route.

Here's how it looks imported into GNOME Contacts:

And into iOS:

It uses VObject, the best Python vCard package I could find. Some work was required to make edge cases work, such as the legacy vCard "name" field.
Addresses #106.

I think I've addressed all comments!
I don't have permission to merge this myself. Happy to have you do it, or to get the permission to do so myself—whichever is easier for you.


Add the date to the Latest Box

In the latest datasets box would be good to have the date like we have for the most viewed.

done


Support for composable functions

fixes #402
fixes #404
Generate ODataPath for composable functions

Proposal of a fix for #402.
Now, ODataPath is not generated for composable functions
../operation/operation
Example from Graph API v1.0 metadata.xml
      <Function Name="lastCell" IsBound="true" IsComposable="true">
        <Parameter Name="bindparameter" Type="graph.workbookRange" />
        <ReturnType Type="graph.workbookRange" />
      </Function>

      <Function Name="visibleView" IsBound="true" IsComposable="true">
        <Parameter Name="bindparameter" Type="graph.workbookRange" />
        <ReturnType Type="graph.workbookRangeView" />
      </Function>

      <Action Name="unmerge" IsBound="true">
        <Parameter Name="bindparameter" Type="graph.workbookRange" />
      </Action>

If functions are composable, they can be chained
../operation/operation/../operation
I have a restriction that only one operation segment can be appended
It's not a fix for #404 which is a case when a navigation segment is added to the operation segment
I can add the navigation segment
...
AppendPath(newOperationPath);

foreach (var navProperty in bindingEntityType.NavigationProperties())
{
    ODataPath newNavigationPath = newOperationPath.Clone();
    newNavigationPath.Push(new ODataNavigationPropertySegment(navProperty));
    AppendPath(newNavigationPath);
}

but newNavigationPath.Kind is calculated as Operation and it will break the code in https://github.com/microsoft/OpenAPI.NET.OData/blob/aaa82b320fd99f5d93a716a032f72c01374bee07/src/Microsoft.OpenApi.OData.Reader/PathItem/OperationPathItemHandler.cs#L75

Added unit test and small changes to ensure that operations are appended to all composable functions, and navigation properties are appended to functions.

Wanted to add this diff screenshot for informational purposes.

The diff image above shows the current number of paths per API generated using the Kiota-based CSDL for v1.0.
Left is current production figures, right is with the changes in this PR.
Below is a similar diff but using the non Kiota-based CSDL (PowerShell and Graph Explorer)

Left is current production figures, right is with the changes in this PR.
drives API seem to have grown by quite a huge margin. We may need to investigate the accuracy of the operations bound to the drives API and and fix them in the metadata if necessary before merging this PR.

@MartinM85 do you mind updating the release notes and bumping up the version in the csproj file?

@irvinesunday Version and release notes updated

Wanted to add this diff screenshot for informational purposes.

The diff image above shows the current number of paths per API generated using the Kiota-based CSDL for v1.0. Left is current production figures, right is with the changes in this PR.
Below is a similar diff but using the non Kiota-based CSDL (PowerShell and Graph Explorer)

Left is current production figures, right is with the changes in this PR.
drives API seem to have grown by quite a huge margin. We may need to investigate the accuracy of the operations bound to the drives API and and fix them in the metadata if necessary before merging this PR.

Investigation to the growth in the drives API is tracked with this issue.

Tested this again, the changes are acceptable, and this PR can be merged.

v1.0

@irvinesunday, thanks for double checking. Did you have to make any changes to the metadata? Any changes we should make to the test CSDLs here considering the bigger increase in path items? (see the integration tests numbers)

@irvinesunday, thanks for double checking. Did you have to make any changes to the metadata? Any changes we should make to the test CSDLs here considering the bigger increase in path items? (see the integration tests numbers)

No, I didn't make any changes to the metadata. The integration file is probably falling behind the main metadata file in terms of annotations.

@irvinesunday would you mind having a quick look at those to check if something obvious comes up? (like a wrong contains target or a missing annotation) so we can keep those numbers down?

@baywet our biggest culprit was a containment for a directoryObject type navigation property that also had a collection of derived types. The integration file and our prod file are still not 100% a match but nothing else out of the ordinary stood out.
<NavigationProperty Name="deletedItems" Type="Collection(graph.directoryObject)" ContainsTarget="true">
  <Annotation Term="Org.OData.Validation.V1.DerivedTypeConstraint">
    <Collection>
      <String>microsoft.graph.user</String>
      <String>microsoft.graph.group</String>
      <String>microsoft.graph.application</String>
    </Collection>
  </Annotation>
  <Annotation Term="Org.OData.Core.V1.ExplicitOperationBindings">
    <Collection>
      <String>microsoft.graph.restore</String>
    </Collection>
  </Annotation>
</NavigationProperty>

Removing the containment (as we've done in our prod files) lowers the path numbers here significantly.
We can merge this.


Check failure when running tensorflow.python.ops.gen_math_ops.sparse_segment_sum

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
No
Source
binary
Tensorflow Version
2.11.0
Custom Code
Yes
OS Platform and Distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Check failure due to dimension mismatch.

Standalone code to reproduce the issue
import tensorflow as tf
import numpy as np
from tensorflow.python.ops import gen_math_ops
try:
  try:
    with tf.device('/CPU'):
      data_tensor = tf.random.uniform([1], dtype=tf.float16)
      data = tf.identity(data_tensor)
      indices = []
      segment_ids = []
      out = gen_math_ops.sparse_segment_sum(data=data,indices=indices,segment_ids=segment_ids,)
  except Exception as e:
    print("Error:"+str(e))
  try:
    with tf.device('/GPU:0'):
      data = tf.identity(data_tensor)
      data = tf.cast(data, tf.float16)
      indices = []
      segment_ids = []
      gen_math_ops.sparse_segment_sum(data=data,indices=indices,segment_ids=segment_ids,)
  except Exception as e:
    print("Error:"+str(e))
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

```shell
2023-01-09 16:51:20.530035: E tensorflow/compiler/xla/stream_executor/cuda/cuda_driver.cc:1159] failed to enqueue async memcpy from device to host: CUDA_ERROR_INVALID_VALUE: invalid argument; host dst: 0x7f9efea00000; GPU src: 0xfffffffffffffffc; size: 4=0x4
Error:{{function_node __wrapped__SparseSegmentSum_device_/job:localhost/replica:0/task:0/device:GPU:0}} SparseSegmentSum: failed to copy last_segment_id from device [Op:SparseSegmentSum]
2023-01-09 16:51:20.531363: F tensorflow/core/common_runtime/gpu/gpu_util.cc:386] CPU->GPU Memcpy failed
Aborted

</details>

@learning-to-play

Hi, We are looking to fix these types of issues in a generic way than fixing it in a OP/API specific.
This issue is happening due to the GPU kernel launch when the input Tensors are empty, which we are trying to address. Thanks for creating the issue.

Tested the code on Ubuntu VM and the results attached below.
With TF 2.11v: Got the error replicated by user but not getting the log F:CPU->GPU Memcpy failed in my environment.
(tf2.11) suryanarayanay@surya-ubuntu-22-04:~$ python 59200.py
2023-02-08 14:21:00.476074: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-02-08 14:21:00.601540: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2023-02-08 14:21:01.353366: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/home/suryanarayanay/miniconda3/envs/tf2.11/lib/
2023-02-08 14:21:01.353470: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/home/suryanarayanay/miniconda3/envs/tf2.11/lib/
2023-02-08 14:21:01.353486: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2.11.0
2023-02-08 14:21:06.263172: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-02-08 14:21:07.603565: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1613] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 38235 MB memory:  -> device: 0, name: NVIDIA A100-SXM4-40GB, pci bus id: 0000:00:04.0, compute capability: 8.0
2023-02-08 14:21:07.605257: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1613] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 38235 MB memory:  -> device: 1, name: NVIDIA A100-SXM4-40GB, pci bus id: 0000:00:05.0, compute capability: 8.0
2023-02-08 14:21:08.336235: E tensorflow/compiler/xla/stream_executor/cuda/cuda_driver.cc:1159] failed to enqueue async memcpy from device to host: CUDA_ERROR_INVALID_VALUE: invalid argument; host dst: 0x7f3cabc00000; GPU src: 0xfffffffffffffffc; size: 4=0x4
Error:{{function_node __wrapped__SparseSegmentSum_device_/job:localhost/replica:0/task:0/device:GPU:0}} SparseSegmentSum: failed to copy last_segment_id from device [Op:SparseSegmentSum]
(tf2.11) suryanarayanay@surya-ubuntu-22-04:~$

With 2.12.0-dev20230201: Same as Tf2.11v mentioned above.
(tf) suryanarayanay@surya-ubuntu-22-04:~$ python 59200.py
2023-02-08 14:21:16.067182: I tensorflow/core/util/port.cc:110] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2023-02-08 14:21:16.118403: E tensorflow/tsl/lib/monitoring/collection_registry.cc:81] Cannot register 2 metrics with the same name: /tensorflow/core/bfc_allocator_delay
2023-02-08 14:21:16.134727: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-02-08 14:21:16.983324: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2.12.0-dev20230201
2023-02-08 14:21:23.533153: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1635] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 38201 MB memory:  -> device: 0, name: NVIDIA A100-SXM4-40GB, pci bus id: 0000:00:04.0, compute capability: 8.0
2023-02-08 14:21:23.534970: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1635] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 38201 MB memory:  -> device: 1, name: NVIDIA A100-SXM4-40GB, pci bus id: 0000:00:05.0, compute capability: 8.0
2023-02-08 14:21:24.271504: E tensorflow/compiler/xla/stream_executor/cuda/cuda_driver.cc:1160] failed to enqueue async memcpy from device to host: CUDA_ERROR_INVALID_VALUE: invalid argument; host dst: 0x7f8d5fa00000; GPU src: 0xfffffffffffffffc; size: 4=0x4
Error:{{function_node __wrapped__SparseSegmentSum_device_/job:localhost/replica:0/task:0/device:GPU:0}} SparseSegmentSum: failed to copy last_segment_id from device [Op:SparseSegmentSum]
(tf) suryanarayanay@surya-ubuntu-22-04:~$


Defaulting in Expressions

Describe the problem you are trying to solve
Defaulting, or the option to ensure that certain fields are present and if not give them a default value.
Today this can be solved with a construct like:
merge default with event;

where default is the struct holding the default values. However, while this may be elegant it is not something that's easy to understand (nor is it fast, but that's a secondary concern).
This also touches on a somewhat related concern: looking up into structs that do not exist.
a.b.c + d.e.f

where b for example does not exist as a key in a.
Describe the solution you'd like
filling a struct with default values
There are a number of possible approaches however they all have their advantages and problems.
patch
default with struct
a new patch keyword default could be used to specify a default structure for a record.
patch event of
  default {"key": "value"}
end

this would effectively be the same as merge default of event end; just in a more verbose but easier to understand syntax.
default with k/v
a default keyword for each value could be used
patch event of
  default "key1" => "value1",
  default "key2" => "value2",
  # ...
end

This would be very clear on what we set but quite verbose, it could be combined with  default {...}
a default operator
This is fairly simple, provide a struct as default values and have them fill the event as it passes through.
a default infix operator
# (could clash with default for path)
let event = event default {"key": "value"};
# or (could cause gramer conflicts)
let event = event default merge {"key": "value"};
# or (could cause gramer conflicts)
let event = event merge {"key": "value"};
# or (uses up new keyword)
let event = event ensure {"key": "value"};
# or (uses up new keyword)
let event = event put_if_absent {"key": "value"};

The second example here is since we'll discuss default for path lookups later and the second option might get around issues but create new ones.
default for lookups
sometimes we want to lookup a value in a nested structure and the path doesn't exist.
return null
This is an option but it comes with serious issues, it would equate null with absent that makes it very hard to distinguish if a value is set to null or absent moving the problem from "What do we do when the value isn't set?" to "is the value set?"
default as a keyword
a.b.c default 7
# or (would burn up a new keyword, also somewhat not as clear ensure might mean we ensure it's always 7)
a.b.c ensure 7

would allow being explicit to when we lookup and replace a default value.
an option type
yes please, but this is a lot of work, would extend the type system, introduce error handling and struct functions so there isn't even a proposed syntax for this
a function
struct::get(struct, key, default)

quite hard given how our functions are implemented would require reworking that, also would be problematic with nested keys. Upside we could do this today in tremor script (slow but doable)
Notes
This will require an RFC before implementation.

My 2 cents for the lookups:
Defaulting only applies to nested paths, that is paths like a.b or a["b"] or a[42].b. And it is the nesting that can fail at each level if the specified nested key or element is not there. This applies to both arrays and records.
I would love to have a means to express an optional nesting step, including a default value in case the nesting step fails.
From that perspective the best candidates seem to be:

base["nesting"] default <DEFAULT> but with this having multiple nesting steps is hard: (base[0] default {}).b default {} (this is currently not possible syntax-wise and needs some more work, also it is cumbersome). Maybe we allow the default to apply to any nested path of arbitrary long nesting, so users get the default if anything along that path fails. For more granular control users need to extract nesting by using multiple steps.
a function like std::path::get(base, "nested", <DEFAULT>) Maybe we could use the second argument to express something like a jsonpath e.g. "a.b.c" as triple nesting. Or have it accept an array of path segments: std::path::get(base, ["nest1", 1, "nest2"], <DEFAULT>).

When it comes to filling a struct with default values the approach that appeals to me the most is the patch operation default which works with both single keys and full records. It transports the intent to modify the given record much better than the standalonedefault operators. And we don't add another operator/language construct/additional tool, but work with what we have and keep the complexity of the language low (in terms of number of constructs/operators etc)

PR to follow - we discussed this on community chat and explored alternatives with the disposition:

The default fn alternative is the most useful variant, and does not need an RFC
Changing the grammar to support default expressions results in LALR disambiguity - which we are avoiding for cost/benefit
A try/catch/throw mechanism was explored, and is viable - but, needs an RFC and further discussion - it would also make a good mentorship project


[Monitor OpenTelemetry] Update Web Snippet

Packages impacted by this PR
@azure/monitor-opentelemetry
Describe the problem that is addressed by this PR
Updates the @microsoft/applicationinsights-web-snippet package to the latest version.
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

The related issue is still open https://github.com/microsoft/ApplicationInsights-JS/issues/2369


Added Glyphfriend under Community Extensions

This is a fork. You should send the PR to https://github.com/Microsoft/extendvs

Sorry Mads, totally didn't realize it was a fork.


Remove redundant constraints

There were quite a few redundant constraints, especially in the volatile
DB, and it was making it difficult to see which constraints were
redundant due to refactoring of the resource registry. This PR literally
does nothing but remove those redundant constraints.

bors r+