Unable to install using composer

Describe the bug
I'm using Laravel 8.7.1 and want to add warehouse-framework to my project using composer.
After using composer require mvdnbrk/warehouse-framework command i got errors
Problem 1     - Installation request for mvdnbrk/warehouse-framework ^0.12.0 -> satisfiable by mvdnbrk/warehouse-framework[v0.12.0].     - Conclusion: remove laravel/framework v8.7.1     - Conclusion: don't install laravel/framework v8.7.1     - mvdnbrk/warehouse-framework v0.12.0 requires illuminate/support ^6.0 || ^7.0 -> satisfiable by illuminate/support[6.x-dev, 7.x-dev, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.12, v6.18.13, v6.18.14, v6.18.15, v6.18.16, v6.18.17, v6.18.18, v6.18.19, v6.18.2, v6.18.20, v6.18.21, v6.18.22, v6.18.23, v6.18.24, v6.18.25, v6.18.26, v6.18.27, v6.18.28, v6.18.29, v6.18.3, v6.18.30, v6.18.31, v6.18.32, v6.18.33, v6.18.34, v6.18.35, v6.18.36, v6.18.37, v6.18.38, v6.18.39, v6.18.4, v6.18.40, v6.18.41, v6.18.42, v6.18.43, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.19.0, v6.19.1, v6.2.0, v6.20.0, v6.20.1, v6.20.10, v6.20.11, v6.20.12, v6.20.13, v6.20.14, v6.20.15, v6.20.16, v6.20.17, v6.20.18, v6.20.19, v6.20.2, v6.20.20, v6.20.21, v6.20.22, v6.20.23, v6.20.24, v6.20.25, v6.20.26, v6.20.27, v6.20.28, v6.20.29, v6.20.3, v6.20.30, v6.20.4, v6.20.5, v6.20.6, v6.20.7, v6.20.8, v6.20.9, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.30.2, v7.30.3, v7.30.4, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2], laravel/framework[6.x-dev, 7.x-dev].     - don't install illuminate/support 6.x-dev|don't install laravel/framework v8.7.1     - don't install illuminate/support 7.x-dev|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.0.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.0.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.0.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.0.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.0.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.1.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.10.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.11.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.12.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.13.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.13.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.14.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.15.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.15.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.16.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.17.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.17.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.10|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.11|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.12|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.13|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.14|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.15|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.16|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.17|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.18|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.19|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.20|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.21|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.22|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.23|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.24|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.25|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.26|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.27|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.28|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.29|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.30|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.31|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.32|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.33|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.34|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.35|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.36|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.37|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.38|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.39|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.40|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.41|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.42|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.43|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.5|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.6|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.7|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.8|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.18.9|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.19.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.19.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.2.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.10|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.11|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.12|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.13|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.14|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.15|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.16|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.17|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.18|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.19|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.20|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.21|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.22|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.23|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.24|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.25|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.26|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.27|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.28|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.29|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.30|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.5|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.6|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.7|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.8|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.20.9|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.3.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.4.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.5.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.5.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.5.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.6.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.6.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.6.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.7.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v6.8.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.5|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.6|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.7|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.0.8|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.1.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.1.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.1.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.1.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.10.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.10.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.10.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.10.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.11.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.12.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.13.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.14.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.14.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.15.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.16.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.16.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.17.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.17.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.17.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.18.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.19.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.19.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.2.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.2.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.2.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.20.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.21.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.22.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.22.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.22.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.22.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.22.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.23.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.23.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.23.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.24.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.25.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.26.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.26.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.27.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.28.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.28.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.28.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.28.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.28.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.29.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.29.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.29.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.29.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.3.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.30.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.30.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.30.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.30.3|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.30.4|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.4.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.5.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.5.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.5.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.6.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.6.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.6.2|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.7.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.7.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.8.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.8.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.9.0|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.9.1|don't install laravel/framework v8.7.1     - don't install illuminate/support v7.9.2|don't install laravel/framework v8.7.1     - Can only install one of: laravel/framework[6.x-dev, v8.7.1].     - Can only install one of: laravel/framework[7.x-dev, v8.7.1].     - Installation request for laravel/framework (locked at v8.7.1, required as ^8.0) -> satisfiable by laravel/framework[v8.7.1].
Here is my composer.json file:
{     "name": "laravel/laravel",     "type": "project",     "description": "The Laravel Framework.",     "keywords": [         "framework",         "laravel"     ],     "license": "MIT",     "require": {         "php": "^7.3",         "ext-json": "*",         "danielme85/laravel-log-to-db": "^2.4",         "fideloper/proxy": "^4.2",         "fruitcake/laravel-cors": "^2.0",         "guzzlehttp/guzzle": "^7.0.1",         "laravel/framework": "^8.0",         "laravel/jetstream": "^1.3",         "laravel/sanctum": "^2.6",         "laravel/tinker": "^2.0",         "livewire/livewire": "^2.0",         "spatie/laravel-permission": "^4.2",         "telegram-bot/api": "^2.3",         "torann/geoip": "^3.0"     },     "require-dev": {         "facade/ignition": "^2.3.6",         "fzaninotto/faker": "^1.9.1",         "mockery/mockery": "^1.3.1",         "nunomaduro/collision": "^5.0",         "phpunit/phpunit": "^9.3"     },     "config": {         "optimize-autoloader": true,         "preferred-install": "dist",         "sort-packages": true     },     "extra": {         "laravel": {             "dont-discover": []         }     },     "autoload": {         "psr-4": {             "App\\": "app/",             "Database\\Factories\\": "database/factories/",             "Database\\Seeders\\": "database/seeders/"         },         "files": [             "app/Helpers/helpers.php"         ]     },     "autoload-dev": {         "psr-4": {             "Tests\\": "tests/"         }     },     "minimum-stability": "dev",     "prefer-stable": true,     "scripts": {         "post-autoload-dump": [             "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",             "@php artisan package:discover --ansi"         ],         "post-root-package-install": [             "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""         ],         "post-create-project-cmd": [             "@php artisan key:generate --ansi"         ]     } }

Warehouse Framework Version: latest
Laravel Version: 8.7.1
PHP Version: 7.4

Installation on fresh clean laravel install also not working, any chance to get help with it? seems this package is very usefull

This packages requires Laravel v8.24 or higher.


[Share] Sharing of the temporary file works on Android but doesn't work on iOS

Steps to Reproduce

Run flutter create bug.
Update the files as follows:

dependencies
  path_provider: ^2.0.1
  share: ^2.0.4

main.dart
import 'dart:io';

import 'package:flutter/material.dart';
import 'package:share/share.dart';
import 'package:path_provider/path_provider.dart';

import 'package:path/path.dart' as path;

void main() {
  runApp(DemoApp());
}

class DemoApp extends StatefulWidget {
  @override
  DemoAppState createState() => DemoAppState();
}

class DemoAppState extends State<DemoApp> {
  String text = 'text to share';
  String fileName = 'test.txt';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Share Plugin Demo',
      home: Scaffold(
          appBar: AppBar(
            title: const Text('Share Plugin Demo'),
          ),
          body: SingleChildScrollView(
            child: Builder(
              builder: (BuildContext context) {
                return ElevatedButton(
                  child: const Text('Share'),
                  onPressed: () => _onShare(context),
                );
              },
            ),
          )),
    );
  }

  _onShare(BuildContext context) async {
    var dir = await getTemporaryDirectory();
    String filePath = path.join(dir.path, fileName);
    File renamedFile = await new File(filePath).writeAsString(text);
    await Share.shareFiles([renamedFile.path]);
    await renamedFile.delete(); // doesn't work for iOS
  }
}

Run the app, it will share the file on Android devices and won't share on iOS devices. If you comment file deleting it will work on both systems. Looks like iOS sharing doesn't lock or copy the file.

Expected results: work in the same way on both OS

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.0, on Mac OS X 10.15.7 19H524 darwin-x64, locale en-CA)
        • Flutter version 2.2.0 at /Users/nadiaivanova/development/flutter
        • Framework revision b22742018b (13 days ago), 2021-05-14 19:12:57 -0700
        • Engine revision a9d88a4d18
        • Dart version 2.13.0

[✗] Android toolchain - develop for Android devices
        ✗ Unable to locate Android SDK.
            Install Android Studio from: https://developer.android.com/studio/index.html
            On first launch it will assist you in installing the Android SDK components.
            (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
            If the Android SDK has been installed to a custom location, please use
            `flutter config --android-sdk` to update to that location.

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

[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
        ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[!] Android Studio (not installed)
        • Android Studio not found; download from https://developer.android.com/studio/index.html
            (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2021.1.1)
        • IntelliJ at /Applications/IntelliJ IDEA.app
        • Flutter plugin version 56.0.5
        • Dart plugin version 211.7233

[!] Connected device
        ! Error: Nadia’s iPad is not connected. Xcode will continue when Nadia’s iPad is connected. (code -13)

! Doctor found issues in 4 categories.

@YuriHeiko share is deprecated mate

@iapicca Oh! I didn't notice that. Thank you!

@iapicca share_plus has the same issue

@iapicca share_plus has the same issue
issue for share_plus should be open here

Hi @YuriHeiko
As @iapicca mentioned, share_plus issues needs to be filed in its repository
Closing, thank you


Unable to load flutterwave payment modal

got this error  Unable to load flutterwave payment modal while loading flutterwave on sandbox, while using hooks.

Same here. I used flutterwave over a year ago and it worked fine then.
But now the payment modal doesn't even load.


Typescript support?

Wondering if this plugin can parse .vue files with typescript, classes, and less styles?
e.g:
<template>
  <div>
    demo
  </div>
</template>

<script
  lang="ts">

  import { Component, Vue } from 'vue-property-decorator';

  @Component
  export default class Demo extends Vue{

  }
</script>

<style
   lang="less"
   scoped>

</style>

Yes, this feature is being developed.

@HcySunYang  nice!

@HcySunYang yes, I want to support, I'd like to contribute a $100 bounty.

@davidmoshal
Sorry, this label may make you misunderstand what I mean. I mean: I am willing to support this feature. I have modified this tag, of course, thank you for your support if you wish. (BTW: I will definitely implement this feature)

@HcySunYang sorry, yes I misunderstood.
Is this a good email for me to use with PayPal<EMAIL_ADDRESS>


🚧 💚 Add pycodestyle in CI

Let's add pycodestyle in CI !

I notice that the ouput of pycodestyle here is really close to the one in https://github.com/pyvista/pyvistaqt/pull/46#issuecomment-667146436

Most of it (E501) can be resolved by a convention in the number of characters by line and allow whitespace after : or not (E203).
Finally, I think (E731) can be solved by using a local function instead of a lambda.

Most of it (E501) can be resolved by a convention for the number of characters by line and whether to allow whitespace after : or not (E203).

You are abosolutly right. But Black doesn't allow it and it is the most inflexible checker that we ultimately need to follow it. So let's add ignore option about it.
--max-line-length=88 --ignore="E203"

Finally, I think (E731) can be solved by using a local function instead of a lambda.

You are right thanks.

Hmm. pycodestyle doesn't recognize ignore error :confused:

Even without the "?

Oh. It work! Thanks @GuillaumeFavelier :+1:

It is ready for merge :rocket:

@GuillaumeFavelier Thanks😇

Thank you @tkoyama010 !


Card components jump on page refresh

Current Behavior
Two simple and practically empty cards on a freshly created project. They both sort of 'jump down' on page refresh.  See the gif

I got a feeling that it's not something too common as people would already mention it.
What am I doing wrong, I'm not sure if it's actually an issue. Thanks
repo
stackblitz
Expected Behavior
no position change or 'jumping' on page refresh
Steps To Reproduce
Component - Card
See the link to the code and the gif with the card code
Thanks
Link to Reproduction / Stackblitz (reproduction template)
https://sveltekitcoursethisdotmedia-ywhm--5173--95086023.local-corp.webcontainer.io/
More Information
No response

Closing. I see it's an illegal move to use  in the card's header or  in description.


Adding a string Data Element to a data group

Whne I tested adding a string Data Element to a data group, I started typing string and the Data Type (Primitive) appeared, as below.

I am trying to add NHS NUMBER to:

When I start typing string, Data Type (Primitive) does not appear. Why is this please?

Data sets are Mauro data models. Each data model contains it's own set of data types, as viewed under the "Types" tab:

Data sets that have been ingested already have this type defined. If an existing "String" type does not appear (e.g. because you have created a new data set), you can add one:

Instead of searching for a data type, click on "Create a new Data Type"
Select "Primitive" as the type.
Under "Data Type Label", enter the word "String".
Continue filling in the rest of the details of the Data Element.

This has changed since we were told how to do this so will retest this.


Fix notes from R CMD check

Hi Noriaki,
I downloaded the package and performed a R CMD check. There are some issues you need to fix to remove all the Notes.

In DESCRIPTION file, the License field, change it to MIT + file LICENSE.
You have many notes of "compareWordNet: no visible global function definition". It is because you forgot to add "Imports" directive in the roxygen documents for corresponding functions. Please check every function which uses functions from non-base packages.
sysdata.rda is not suggested to be directly put under R/ folder. You can put it in inst/extdata folder, and in the code you can load it by system.file("extdata", "sysdata.rda", package = "wcGeneSummary"). Also note when saving the .rda file, also specify compress = "xz" to maximally reduce the file size.
Improve the vignette. Currently the vignette is too simple. You can add examples from the readme.md file also to the vignette.

* using log directory ‘/Users/guz/project/development/wcGeneSummary.Rcheck’
* using R version 4.2.0 (2022-04-22)
* using platform: x86_64-apple-darwin17.0 (64-bit)
* using session charset: UTF-8
* checking for file ‘wcGeneSummary/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘wcGeneSummary’ version ‘0.99.0’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘wcGeneSummary’ can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
License components which are templates and need '+ file LICENSE':
  MIT
* checking top-level files ... NOTE
File
  LICENSE
is not mentioned in the DESCRIPTION file.
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... NOTE
compareWordNet: no visible global function definition for
  ‘geom_mark_hull’
compareWordNet: no visible binding for global variable ‘x’
compareWordNet: no visible binding for global variable ‘y’
compareWordNet: no visible global function definition for
  ‘colorRampPalette’
compareWordNet: no visible binding for global variable ‘name’
getWordsOnDendro: no visible binding for global variable ‘x’
makeBar: no visible binding for global variable ‘freq’
pathviewText: no visible global function definition for ‘download.kegg’
pathviewText: no visible global function definition for ‘node.info’
pathviewText: no visible global function definition for ‘node.map’
pathviewText: no visible global function definition for
  ‘colorRampPalette’
pathviewText: no visible global function definition for
  ‘keggview.native’
pathviewText: no visible global function definition for ‘readPNG’
pathviewText: no visible binding for global variable ‘query’
pathviewText: no visible global function definition for ‘summarise’
pathviewText: no visible global function definition for ‘group_by’
pathviewText: no visible binding for global variable ‘X1’
pathviewText: no visible global function definition for ‘n’
pathviewText: no visible global function definition for ‘reorder’
pathviewText: no visible binding for global variable ‘X3’
pathviewText: no visible binding for global variable ‘stack’
pathviewText: no visible binding for global variable ‘X2’
plotDynamic: no visible binding for global variable ‘Freq’
plotDynamic: no visible binding for global variable ‘name’
plotORA: no visible binding for global variable ‘freq’
plotORA: no visible binding for global variable ‘p’
plotORA: no visible global function definition for ‘geom_text_repel’
retUdpipeNet: no visible global function definition for ‘summarise’
retUdpipeNet: no visible global function definition for ‘group_by’
retUdpipeNet: no visible binding for global variable ‘term’
retUdpipeNet: no visible binding for global variable ‘ID’
retUdpipeNet: no visible binding for global variable ‘sentence_id’
retUdpipeNet: no visible binding for global variable ‘token_id’
retUdpipeNet: no visible binding for global variable ‘name’
returnPyramid: no visible binding for global variable ‘ME’
returnPyramid: no visible binding for global variable ‘Word’
returnPyramid: no visible binding for global variable ‘Label’
returnPyramid: no visible binding for global variable ‘Count’
returnPyramid: no visible binding for global variable ‘plotID’
returnPyramid: no visible binding for global variable ‘value’
returnPyramid: no visible binding for global variable ‘plotCol’
returnQuanteda: no visible global function definition for ‘corpus’
returnQuanteda: no visible global function definition for
  ‘tokens_remove’
returnQuanteda: no visible global function definition for
  ‘tokens_ngrams’
returnQuanteda: no visible global function definition for ‘dfm’
returnQuanteda: no visible global function definition for ‘dfm_tfidf’
textORA: no visible binding for global variable ‘Gene_ID’
wcAbst: no visible global function definition for ‘boot.strength’
wcAbst: no visible global function definition for ‘averaged.network’
wcAbst: no visible binding for global variable ‘weight’
wcAbst: no visible binding for global variable ‘Freq’
wcAbst: no visible binding for global variable ‘name’
wcBSDB: no visible binding for global variable ‘Title’
wcBSDB: no visible binding for global variable ‘ID’
wcBSDB: no visible binding for global variable ‘orgDb’
wcBSDB: no visible binding for global variable ‘weight’
wcBSDB: no visible binding for global variable ‘Freq’
wcBSDB: no visible binding for global variable ‘name’
wcGeneSummary: no visible global function definition for
  ‘enrichPathway’
wcGeneSummary: no visible global function definition for ‘enrichKEGG’
wcGeneSummary: no visible binding for global variable ‘Gene_ID’
wcGeneSummary: no visible global function definition for ‘setReadable’
wcGeneSummary: no visible global function definition for
  ‘boot.strength’
wcGeneSummary: no visible global function definition for
  ‘averaged.network’
wcGeneSummary: no visible binding for global variable ‘weight’
wcGeneSummary: no visible binding for global variable ‘Freq’
wcGeneSummary: no visible binding for global variable ‘name’
wcGeneSummary: no visible global function definition for
  ‘geom_mark_hull’
wcMan: no visible global function definition for ‘boot.strength’
wcMan: no visible global function definition for ‘averaged.network’
wcMan: no visible binding for global variable ‘weight’
wcMan: no visible binding for global variable ‘Freq’
wcMan: no visible binding for global variable ‘name’
wcMan: no visible binding for global variable ‘redo’
plot,osplot-ANY: no visible global function definition for
  ‘colorRampPalette’
plot,osplot-ANY: no visible global function definition for ‘brewer.pal’
plot,osplot-ANY: no visible global function definition for
  ‘adjustcolor’
show,osplot: no visible global function definition for ‘object.size’
Undefined global functions or variables:
  Count Freq Gene_ID ID Label ME Title Word X1 X2 X3 adjustcolor
  averaged.network boot.strength brewer.pal colorRampPalette corpus dfm
  dfm_tfidf download.kegg enrichKEGG enrichPathway freq geom_mark_hull
  geom_text_repel group_by keggview.native n name node.info node.map
  object.size orgDb p plotCol plotID query readPNG redo reorder
  sentence_id setReadable stack summarise term token_id tokens_ngrams
  tokens_remove value weight x y
Consider adding
  importFrom("grDevices", "adjustcolor", "colorRampPalette")
  importFrom("stats", "reorder")
  importFrom("utils", "object.size", "stack")
to your NAMESPACE file.
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking R/sysdata.rda ... NOTE

  Note: significantly better compression could be obtained
        by using R CMD build --resave-data
              old_size new_size compress
  sysdata.rda    1.4Mb    311Kb       xz
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... OK
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘testthat.R’
 OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ...
  ‘basic_usage.Rmd’ using ‘UTF-8’... OK
 NONE
* checking re-building of vignette outputs ... OK
* checking PDF version of manual ... OK
* DONE

Status: 4 NOTEs
See
  ‘/Users/guz/project/development/wcGeneSummary.Rcheck/00check.log’
for details.

Dear Dr. Zuguang Gu,
Thank you very much for taking the time to check the codes. I fixed the codes so that R CMD check does not produce errors, warnings and notes, after addressing your comments.

I changed the License line.
I have checked the function definitions and added necessary packages to "Imports".
I have moved the sysdata.rda to inst/extdata, and made the changes to the codes loading the dataset. Also, I have re-compressed the file in xz format.
As you stated, the vignette is too simple and I have improved the vignette for including more contents like comparing networks and summarization of enrichment analysis results.

Sincerely,
Noriaki Sato


Live Stitch

Hello,
Thanks for this nice and usefull stitching project
I am able to stitch my microscopic images, but I have a question:
Is it possible to stitch the images when scanning the tissue ? Because my images are high resolution (5Mp) and there are a lot of them(Sometimes 2000 - 3000 tiles). Stitching these tiles after scanning takes much time
Thanks again

Hm maybe. Can you provide a little more detail about your process?  Or are you hoping to be able to see the image as it's being stitched together?

Hello, first of all thank you for your interest
Normally, when scanning, I can both save the images to disk or send the images to a different process with a multiprocessing queue mechanism and process the images in this different process.
Simply I do this ;
import queue # In my code this is multiprocessing queue
import numpy as np

frames = queue.Queue()

def feed():
    while 1:
        frames.put(get_frame())

stitched = None
while 1:
    frame = frames.get()
    stitched = stitch2d.stitch(stitched, frame)

While scanning, the focused image comes from the camera, I want to do the stitching process as these images come in and save the stitched image to the file when the scan is finished

I can help you with the coding, where should we start when we want to do this?

Here's a potential approach you can try. For each iteration, the script builds a mosaic, then copies the tile position from the mosaic created during the previous iteration, which means that it should only place the new tiles. When no more tiles are found, it stops.
import shutil
import time
from pathlib import Path

from stitch2d import create_mosaic

prev_mosaic = None
prev_tiles = []

while True:

    # Get tiles from the working directory
    tiles = [str(t) for t in Path("working").glob("*.tif")]
    print(f"Found {len(tiles)} tiles")

    # Stop processing if no new tiles have been added
    if tiles == prev_tiles:
        break

    # Wait a few seconds to make sure the last tile has finished saving
    time.sleep(5)

    # Copy tile data from the previous iteration
    mosaic = create_mosaic(tiles, dim=11)
    if prev_mosaic is not None:
        prev_tiles = {t.source: t for t in prev_mosaic.tiles if isinstance(t.source, str)}
        for tile in mosaic.tiles:
            try:
                prev_tile = prev_tiles[tile.source]
            except (KeyError, TypeError):
                pass
            else:
                for attr in ("id", "y", "x"):
                    setattr(tile, attr, getattr(prev_tile, attr))

    # Align the mosaic. Tiles that were previously processed are skipped.
    mosaic.downsample(0.6)
    mosaic.align()
    mosaic.reset_tiles()
    mosaic.save("mosaic.jpg")

    # Update the previous iteration
    prev_mosaic = mosaic
    prev_tiles = tiles

Anecdotally, I've found that this approach generally works but seems to have a somewhat higher likelihood of a bad tile placement, especially early on. You might consider waiting until you've accumulated some tiles or even a whole row before aligning.

First of all thank you so much @adamancer
I am trying to stitch my images with the code you shared, I will experiment with new images to correct the results I get, I will also experiment by increasing the overlap amount and see how the result changes and then I will share it with you here
It's great that your project can be quickly adapted for live stitch
Thanks again

Hello,
I tried to stitch my images normally before trying live stitching, I was able to successfully stitch some images, but my other images was not stitched. I got RuntimeError: Tiles could not be aligned error Normally there is a 10% overlap between the images, I changed it to 15% but I got the same error. If you have time you can run the code I shared on the dataset
I also disabled downsampling, but it still give error
This is drive link to download images
Thank you very much


Fix heap-use-after-free errors found by AddressSanitizer

The errors are found  by running RUSTFLAGS="-Z sanitizer=address" sh run_tests.sh:
There are 4 errors in total. The error happens when running:

test_switch_device
test_destroy_duplex_stream_after_unplugging_a_nondefault_input_device
test_destroy_duplex_stream_after_unplugging_a_default_input_device
test_destroy_duplex_stream_after_unplugging_a_default_output_device

test_switch_device
Run RUSTFLAGS="-Z sanitizer=address" cargo test test_switch_device -- --ignored --nocapture to see
...

test backend::tests::device_change::test_switch_device ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 183 filtered out

==4253==ERROR: AddressSanitizer: heap-use-after-free on address 0x6160000129db at pc 0x00010a5c5793 bp 0x7000004b91c0 sp 0x7000004b91b8
READ of size 1 at 0x6160000129db thread T6

test_destroy_duplex_stream_after_unplugging_a_nondefault_input_device
Run RUSTFLAGS="-Z sanitizer=address" cargo test test_destroy_duplex_stream_after_unplugging_a_nondefault_input_device -- --ignored --nocapture to see
...

running 1 test
Device change callback. data @ 0x603000011ff0
=================================================================
test backend::tests::device_change::test_destroy_duplex_stream_after_unplugging_a_nondefault_input_device ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 183 filtered out

==4268==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000010bdb at pc 0x000103ffe793 bp 0x700007cee1c0 sp 0x700007cee1b8
READ of size 1 at 0x616000010bdb thread T5

test_destroy_duplex_stream_after_unplugging_a_default_input_device
Run RUSTFLAGS="-Z sanitizer=address" cargo test test_destroy_duplex_stream_after_unplugging_a_default_input_device -- --ignored --nocapture to see:
...

running 1 test
Device change callback. data @ 0x603000013820
=================================================================
test backend::tests::device_change::test_destroy_duplex_stream_after_unplugging_a_default_input_device ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 183 filtered out

==4292==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000010bdb at pc 0x00010cc31793 bp 0x70000cd961c0 sp 0x70000cd961b8
READ of size 1 at 0x616000010bdb thread T6

test_destroy_duplex_stream_after_unplugging_a_default_output_device
Run RUSTFLAGS="-Z sanitizer=address" cargo test test_destroy_duplex_stream_after_unplugging_a_default_output_device -- --ignored --nocapture to see:
...

running 1 test
Device change callback. data @ 0x603000012110
=================================================================
test backend::tests::device_change::test_destroy_duplex_stream_after_unplugging_a_default_output_device ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 183 filtered out

==4315==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000010bdb at pc 0x0001082cf793 bp 0x7000031ef1c0 sp 0x7000031ef1b8
READ of size 1 at 0x616000010bdb thread T6

Got a more detail log for running RUSTFLAGS="-Z sanitizer=address" cargo test test_switch_device -- --ignored --nocapture with adding a delay on the end of the test (otherwise the stacktraces won't be printed, don't know why)
running 1 test

Switch default device for Output while the stream is working.

Output devices
--------------------
 204: AppleGFXHDAEngineOutputDP:10001:0:{C315-2684-05BF0E12}
	uid: EV2750
 194: AppleHDAEngineOutput:1F,3,0,1,1:0
	uid: Headphones
  41: SoundflowerEngine:0
	uid: Soundflower (2ch)
  52: SoundflowerEngine:1
	uid: Soundflower (64ch)

Switch device for Output: 194 -> 41
Switch device for Output: 41 -> 52
Switch device for Output: 52 -> 204
Switch device for Output: 204 -> 194
=================================================================
==7236==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000010bdb at pc 0x000106410723 bp 0x7000029fa1c0 sp 0x7000029fa1b8
READ of size 1 at 0x616000010bdb thread T6
    #0 0x106410722 in core::sync::atomic::atomic_load::h4dc415c6a3ce79a6 atomic.rs:2277
    #1 0x10647185c in core::sync::atomic::AtomicBool::load::hd6d654f0922c62d7 atomic.rs:404
    #2 0x1063fb16c in cubeb_coreaudio::backend::AudioUnitStream::reinit_async::_$u7b$$u7b$closure$u7d$$u7d$::hbea024c63054739e mod.rs:3270
    #3 0x1063082e2 in coreaudio_sys_utils::dispatch::create_closure_and_executor::closure_executer::haff5ead75c17e7a3 dispatch.rs:59
    #4 0x106c87441 in asan_dispatch_call_block_and_release (librustc_rt.asan.dylib:x86_64+0x41441)
    #5 0x7fff6e3f850d in _dispatch_client_callout (libdispatch.dylib:x86_64+0x350d)
    #6 0x7fff6e3fdacd in _dispatch_lane_serial_drain (libdispatch.dylib:x86_64+0x8acd)
    #7 0x7fff6e3fe451 in _dispatch_lane_invoke (libdispatch.dylib:x86_64+0x9451)
    #8 0x7fff6e407a9d in _dispatch_workloop_worker_thread (libdispatch.dylib:x86_64+0x12a9d)
    #9 0x7fff6e6526fb in _pthread_wqthread (libsystem_pthread.dylib:x86_64+0x26fb)
    #10 0x7fff6e651826 in start_wqthread (libsystem_pthread.dylib:x86_64+0x1826)

0x616000010bdb is located 91 bytes inside of 608-byte region [0x616000010b80,0x616000010de0)
freed by thread T1 here:
    #0 0x106c88ad6 in wrap_free (librustc_rt.asan.dylib:x86_64+0x42ad6)
    #1 0x10669c57a in alloc::alloc::dealloc::h2a46682b3fd1fcd4 alloc.rs:103
    #2 0x1063cbbc0 in alloc::alloc::box_free::h85e777566b08c76d alloc.rs:217
    #3 0x1062af623 in core::ptr::drop_in_place::he4a20f3e32dba16b mod.rs:174
    #4 0x10643c62b in cubeb_backend::capi::capi_stream_destroy::h504649dfea752dec capi.rs:173
    #5 0x1064e0a09 in cubeb_coreaudio::backend::tests::utils::test_ops_stream_operation::_$u7b$$u7b$closure$u7d$$u7d$::hbc15cf636f0b150a utils.rs:1091
    #6 0x1064c795a in cubeb_coreaudio::backend::tests::utils::test_ops_context_operation::hfab4167c5af0e787 utils.rs:1035
    #7 0x1064cd09f in cubeb_coreaudio::backend::tests::utils::test_ops_stream_operation::haaacc9c4ff9c81b0 utils.rs:1056
    #8 0x1061f95ca in cubeb_coreaudio::backend::tests::device_change::test_get_started_stream_in_scope::hcd049a2a814dc689 device_change.rs:165
    #9 0x1064049cc in cubeb_coreaudio::backend::tests::device_change::test_switch_device_in_scope::hb0894f5959915bd4 device_change.rs:60
    #10 0x10640dfa8 in cubeb_coreaudio::backend::tests::device_change::test_switch_device::hf2026957a4208330 device_change.rs:31
    #11 0x1061ffa70 in cubeb_coreaudio::backend::tests::device_change::test_switch_device::_$u7b$$u7b$closure$u7d$$u7d$::h7e363590f88f7d2c device_change.rs:29
    #12 0x10627e643 in core::ops::function::FnOnce::call_once::h0da49dbfb7e04f06 function.rs:232
    #13 0x10676d5ed in _$LT$alloc..boxed..Box$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$A$GT$$GT$::call_once::h09f25e49c6b2dde5 boxed.rs:1016
    #14 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #15 0x106787363 in test::run_test::run_test_inner::_$u7b$$u7b$closure$u7d$$u7d$::he7e26757f8f77360 lib.rs:539
    #16 0x10676058a in std::sys_common::backtrace::__rust_begin_short_backtrace::h1ec69ba5fcb050d2 backtrace.rs:129
    #17 0x1067652da in std::panicking::try::do_call::h3f0071cc5ab7da00 panicking.rs:303
    #18 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #19 0x106765df5 in core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h059274226e6540b3 mod.rs:474
    #20 0x10684fd7d in _$LT$alloc..boxed..Box$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$A$GT$$GT$::call_once::h9d68ab0c0b6f49ed boxed.rs:1016
    #21 0x10686212d in std::sys::unix::thread::Thread::new::thread_start::h18be3f46590c0640 boxed.rs:1016
    #22 0x7fff6e655e64 in _pthread_start (libsystem_pthread.dylib:x86_64+0x5e64)
    #23 0x7fff6e65183a in thread_start (libsystem_pthread.dylib:x86_64+0x183a)

previously allocated by thread T1 here:
    #0 0x106c8898d in wrap_malloc (librustc_rt.asan.dylib:x86_64+0x4298d)
    #1 0x10669c3c4 in alloc::alloc::alloc::hf6ad4692150492f5 alloc.rs:81
    #2 0x10669c16b in alloc::alloc::exchange_malloc::h873d61ec2e163377 alloc.rs:203
    #3 0x10654c166 in _$LT$cubeb_coreaudio..backend..AudioUnitContext$u20$as$u20$cubeb_backend..traits..ContextOps$GT$::stream_init::h174f9c68d49e1f3b mod.rs:2159
    #4 0x10643bbef in cubeb_backend::capi::capi_stream_init::h354e09e23cca1513 capi.rs:155
    #5 0x1064e0163 in cubeb_coreaudio::backend::tests::utils::test_ops_stream_operation::_$u7b$$u7b$closure$u7d$$u7d$::hbc15cf636f0b150a utils.rs:1072
    #6 0x1064c795a in cubeb_coreaudio::backend::tests::utils::test_ops_context_operation::hfab4167c5af0e787 utils.rs:1035
    #7 0x1064cd09f in cubeb_coreaudio::backend::tests::utils::test_ops_stream_operation::haaacc9c4ff9c81b0 utils.rs:1056
    #8 0x1061f95ca in cubeb_coreaudio::backend::tests::device_change::test_get_started_stream_in_scope::hcd049a2a814dc689 device_change.rs:165
    #9 0x1064049cc in cubeb_coreaudio::backend::tests::device_change::test_switch_device_in_scope::hb0894f5959915bd4 device_change.rs:60
    #10 0x10640dfa8 in cubeb_coreaudio::backend::tests::device_change::test_switch_device::hf2026957a4208330 device_change.rs:31
    #11 0x1061ffa70 in cubeb_coreaudio::backend::tests::device_change::test_switch_device::_$u7b$$u7b$closure$u7d$$u7d$::h7e363590f88f7d2c device_change.rs:29
    #12 0x10627e643 in core::ops::function::FnOnce::call_once::h0da49dbfb7e04f06 function.rs:232
    #13 0x10676d5ed in _$LT$alloc..boxed..Box$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$A$GT$$GT$::call_once::h09f25e49c6b2dde5 boxed.rs:1016
    #14 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #15 0x106787363 in test::run_test::run_test_inner::_$u7b$$u7b$closure$u7d$$u7d$::he7e26757f8f77360 lib.rs:539
    #16 0x10676058a in std::sys_common::backtrace::__rust_begin_short_backtrace::h1ec69ba5fcb050d2 backtrace.rs:129
    #17 0x1067652da in std::panicking::try::do_call::h3f0071cc5ab7da00 panicking.rs:303
    #18 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #19 0x106765df5 in core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h059274226e6540b3 mod.rs:474
    #20 0x10684fd7d in _$LT$alloc..boxed..Box$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$A$GT$$GT$::call_once::h9d68ab0c0b6f49ed boxed.rs:1016
    #21 0x10686212d in std::sys::unix::thread::Thread::new::thread_start::h18be3f46590c0640 boxed.rs:1016
    #22 0x7fff6e655e64 in _pthread_start (libsystem_pthread.dylib:x86_64+0x5e64)
    #23 0x7fff6e65183a in thread_start (libsystem_pthread.dylib:x86_64+0x183a)

Thread T6 created by T4 here:
    <empty stack>

Thread T4 created by T1 here:
    #0 0x106c82b8a in wrap_pthread_create (librustc_rt.asan.dylib:x86_64+0x3cb8a)
    #1 0x7fff6e402742 in _dispatch_root_queue_poke_slow (libdispatch.dylib:x86_64+0xd742)
    #2 0x7fff366deaf5 in HALB_DispatchQueue::InstallMIGServer(unsigned int, unsigned int, unsigned int (*)(mach_msg_header_t*, mach_msg_header_t*)) (CoreAudio:x86_64+0x3f9af5)
    #3 0x7fff3660e26a in HALC_ProxySystem::HALC_ProxySystem() (CoreAudio:x86_64+0x32926a)
    #4 0x7fff3661e0af in HALC_ProxyObjectMap::_CreateSystemObject() (CoreAudio:x86_64+0x3390af)
    #5 0x7fff3661d48a in HALC_ProxyObjectMap::CopyObjectByObjectID(unsigned int) (CoreAudio:x86_64+0x33848a)
    #6 0x7fff362e7812 in HALSystem::InitializeDevices() (CoreAudio:x86_64+0x2812)
    #7 0x7fff362e686c in HALSystem::CheckOutInstance() (CoreAudio:x86_64+0x186c)
    #8 0x7fff362ec390 in AudioObjectGetPropertyDataSize (CoreAudio:x86_64+0x7390)
    #9 0x106619685 in cubeb_coreaudio::backend::tests::utils::test_get_all_devices::hfc2293ff551a6aa8 utils.rs:255
    #10 0x10661a9b1 in cubeb_coreaudio::backend::tests::utils::test_get_devices_in_scope::hc73873ced910c1db utils.rs:291
    #11 0x1064046b0 in cubeb_coreaudio::backend::tests::device_change::test_switch_device_in_scope::hb0894f5959915bd4 device_change.rs:41
    #12 0x10640dfa8 in cubeb_coreaudio::backend::tests::device_change::test_switch_device::hf2026957a4208330 device_change.rs:31
    #13 0x1061ffa70 in cubeb_coreaudio::backend::tests::device_change::test_switch_device::_$u7b$$u7b$closure$u7d$$u7d$::h7e363590f88f7d2c device_change.rs:29
    #14 0x10627e643 in core::ops::function::FnOnce::call_once::h0da49dbfb7e04f06 function.rs:232
    #15 0x10676d5ed in _$LT$alloc..boxed..Box$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$A$GT$$GT$::call_once::h09f25e49c6b2dde5 boxed.rs:1016
    #16 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #17 0x106787363 in test::run_test::run_test_inner::_$u7b$$u7b$closure$u7d$$u7d$::he7e26757f8f77360 lib.rs:539
    #18 0x10676058a in std::sys_common::backtrace::__rust_begin_short_backtrace::h1ec69ba5fcb050d2 backtrace.rs:129
    #19 0x1067652da in std::panicking::try::do_call::h3f0071cc5ab7da00 panicking.rs:303
    #20 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #21 0x106765df5 in core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h059274226e6540b3 mod.rs:474
    #22 0x10684fd7d in _$LT$alloc..boxed..Box$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$A$GT$$GT$::call_once::h9d68ab0c0b6f49ed boxed.rs:1016
    #23 0x10686212d in std::sys::unix::thread::Thread::new::thread_start::h18be3f46590c0640 boxed.rs:1016
    #24 0x7fff6e655e64 in _pthread_start (libsystem_pthread.dylib:x86_64+0x5e64)
    #25 0x7fff6e65183a in thread_start (libsystem_pthread.dylib:x86_64+0x183a)

Thread T1 created by T0 here:
    #0 0x106c82b8a in wrap_pthread_create (librustc_rt.asan.dylib:x86_64+0x3cb8a)
    #1 0x106861dd7 in std::sys::unix::thread::Thread::new::h586ae1a3fbb68ccd thread.rs:68
    #2 0x106786cba in test::run_test::run_test_inner::h41a17006bde78306 mod.rs:492
    #3 0x1067852dd in test::run_test::hc2b0fa225f1cdfde lib.rs:503
    #4 0x10678127c in test::run_tests::hf9fe773408722b8d lib.rs:301
    #5 0x1067733a5 in test::console::run_tests_console::h257d38a897830738 console.rs:280
    #6 0x10677e9a2 in test::test_main::h0ece35b24fdccd5b lib.rs:122
    #7 0x10677f9ae in test::test_main_static::h03d43955d3e6f66b lib.rs:141
    #8 0x106733dd7 in cubeb_coreaudio::main::ha80bf2604bb83103 (cubeb_coreaudio-8efcc4bcc1a06d9a:x86_64+0x100564dd7)
    #9 0x1066c5a1d in std::rt::lang_start::_$u7b$$u7b$closure$u7d$$u7d$::h46ca11651ad8e411 rt.rs:67
    #10 0x10685bc07 in std::panicking::try::do_call::hd7d5ebb621afe41a panicking.rs:303
    #11 0x1068627ea in __rust_maybe_catch_panic lib.rs:86
    #12 0x10685c4fb in std::rt::lang_start_internal::hf660b1f8d8c56d9b panicking.rs:281
    #13 0x1066c5985 in std::rt::lang_start::hdcbaaa8cfc30d74d rt.rs:67
    #14 0x106733e01 in main (cubeb_coreaudio-8efcc4bcc1a06d9a:x86_64+0x100564e01)
    #15 0x7fff6e4517fc in start (libdyld.dylib:x86_64+0x1a7fc)

SUMMARY: AddressSanitizer: heap-use-after-free atomic.rs:2277 in core::sync::atomic::atomic_load::h4dc415c6a3ce79a6
Shadow bytes around the buggy address:
  0x1c2c00002120: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c2c00002130: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c2c00002140: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c2c00002150: fd fd fd fd fa fa fa fa fa fa fa fa fa fa fa fa
  0x1c2c00002160: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x1c2c00002170: fd fd fd fd fd fd fd fd fd fd fd[fd]fd fd fd fd
  0x1c2c00002180: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c2c00002190: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c2c000021a0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x1c2c000021b0: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa
  0x1c2c000021c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:           00
  Partially addressable: 01 02 03 04 05 06 07
  Heap left redzone:       fa
  Freed heap region:       fd
  Stack left redzone:      f1
  Stack mid redzone:       f2
  Stack right redzone:     f3
  Stack after return:      f5
  Stack use after scope:   f8
  Global redzone:          f9
  Global init order:       f6
  Poisoned by user:        f7
  Container overflow:      fc
  Array cookie:            ac
  Intra object redzone:    bb
  ASan internal:           fe
  Left alloca redzone:     ca
  Right alloca redzone:    cb
  Shadow gap:              cc
==7236==ABORTING
error: test failed, to rerun pass '--lib'

Caused by:
  process didn't exit successfully: `/Users/cchang/Work/cubeb-coreaudio-rs/target/debug/deps/cubeb_coreaudio-8efcc4bcc1a06d9a test_switch_device --ignored --nocapture` (signal: 6, SIGABRT: process abort signal)

Got a more detail log for running RUSTFLAGS="-Z sanitizer=address" cargo test test_switch_device -- --ignored --nocapture with adding a delay on the end of the test (otherwise the stacktraces won't be printed, don't know why)
running 1 test

Switch default device for Output while the stream is working.

Output devices
--------------------
 204: AppleGFXHDAEngineOutputDP:10001:0:{C315-2684-05BF0E12}
	uid: EV2750
 194: AppleHDAEngineOutput:1F,3,0,1,1:0
	uid: Headphones
  41: SoundflowerEngine:0
	uid: Soundflower (2ch)
  52: SoundflowerEngine:1
	uid: Soundflower (64ch)

Switch device for Output: 194 -> 41
Switch device for Output: 41 -> 52
Switch device for Output: 52 -> 204
Switch device for Output: 204 -> 194
=================================================================
==7236==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000010bdb at pc 0x000106410723 bp 0x7000029fa1c0 sp 0x7000029fa1b8
READ of size 1 at 0x616000010bdb thread T6
    #0 0x106410722 in core::sync::atomic::atomic_load::h4dc415c6a3ce79a6 atomic.rs:2277
    #1 0x10647185c in core::sync::atomic::AtomicBool::load::hd6d654f0922c62d7 atomic.rs:404
    #2 0x1063fb16c in cubeb_coreaudio::backend::AudioUnitStream::reinit_async::_$u7b$$u7b$closure$u7d$$u7d$::hbea024c63054739e mod.rs:3270
    #3 0x1063082e2 in coreaudio_sys_utils::dispatch::create_closure_and_executor::closure_executer::haff5ead75c17e7a3 dispatch.rs:59
    #4 0x106c87441 in asan_dispatch_call_block_and_release (librustc_rt.asan.dylib:x86_64+0x41441)
    #5 0x7fff6e3f850d in _dispatch_client_callout (libdispatch.dylib:x86_64+0x350d)
    #6 0x7fff6e3fdacd in _dispatch_lane_serial_drain (libdispatch.dylib:x86_64+0x8acd)
    #7 0x7fff6e3fe451 in _dispatch_lane_invoke (libdispatch.dylib:x86_64+0x9451)
    #8 0x7fff6e407a9d in _dispatch_workloop_worker_thread (libdispatch.dylib:x86_64+0x12a9d)
    #9 0x7fff6e6526fb in _pthread_wqthread (libsystem_pthread.dylib:x86_64+0x26fb)
    #10 0x7fff6e651826 in start_wqthread (libsystem_pthread.dylib:x86_64+0x1826)

I dig a bit deeper today. The 0x616000010bdb here is destroy_pending: AtomicBool in AudioUnitStream at mod.rs:3270
https://github.com/ChunMinChang/cubeb-coreaudio-rs/blob/7fe03b4201160f84aad1c12536affe6b05f8839f/src/backend/mod.rs#L3270
I suspect there is a stream-reinit-task posted to the global task queue in the cubeb context (aka AudioUnitContext::serial_queue) while stream-destroy-task is being executed in the global task queue.
Suppose there are 3 different threads

M: the Main thread running the test_switch_device test
T: the thread running the task in the global task queue (AudioUnitContext::serial_queue)
D: the device-changed callback thread (whereaudiounit_property_listener_callback is on)

The timeline should be like this

M: Start running test_switch_device
M: Initialize cubeb context
M: Initialize cubeb stream
M: Start cubeb stream
M: Change the default output device
The default device is changed: The following works might be run at the same time

M: Get notification of the device changed

Do 5 again until it's repeated X times

D: If the stream-reinit-task is pending/being run, skip this event. Otherwise, post an async stream-reinit-task to the global task queue

T: Start executing the stream-reinit-task

The following works might be run at the same time:

After the default output device is changed X times, the test is about to be finished, so
M start destroying cubeb stream, which posts a sync stream-destroy-task to the the global task queue. Then M is blocked until the stream-destroy-task is done.
While M is executing, the D is fired for the last device-changed event and then posts an async stream-reinit-task

If stream-destroy-task is posted before stream-reinit-task, T will execute stream-destroy-task first
T: Finishing the stream-destroy-task
The following works might be run at the same time:

M: Destroy cubeb context
T: Pick and run the stream-reinit-task after the cubeb stream is destroyed

T: Touching destroy_pending leads to a crash

At the step 10, touching the destroy_pending in a destroyed cubeb stream causes the crash.

@padenot, @kinetiknz, @achronop, any idea to fix this properly?
I see there is a lock used in audiounit_stream_destroy but not sure if it can help for the above case (or the analysis is incorrect?). Does this happen before? Not sure if I missed something when rewriting the code in Rust...

In addition to what you have, you could use the if stm_guard.destroy_pending.load(Ordering::SeqCst) inside the main body of reinit_async() in a way that we don't async_dispatch another reinit closure if this flag is true. In this case, you would also need synchronization between destroy() and reinit_async().

If the solution is the above I guess the c-api is not protected by this problem, probably we haven't tried the same test.


Multi / Linked GPU Example?

Was wondering if there was a multi gpu example that demos "alternate frame rendering" AFR?
No one has anything like this for Vulkan but D3D12 examples do.

Nothing I'm aware of. I'd do one myself, but I'm not on a multi-gpu setup.

I have 4 different multi-gpu systems. Crossfire x2 RX 580, Crossfire x2 R9 280x, SLI x2 GTX 960, and SLI x2 GTX 250.
I don't have time atm to make a demo myself as I'm focused on a different project but maybe I can help contribute here later.  If anyone ever has a multi-gpu test they would like me to run I can validate it for them. Just clearing the backbuffer in AFR mode would be good enough.

The idea is good.

Can you open up a sample request at the https://github.com/KhronosGroup/Vulkan-Samples?

K made one: https://github.com/KhronosGroup/Vulkan-Samples/issues/85
Also I'm working on a framework that will have m-gpu support in Vulkan and D3D12: https://github.com/reignstudios/Orbital-Framework
When I get it working there I can share what API features are needed to make an example here.

@zezba9000 in case it's still of interest to you, https://github.com/NVIDIA/Q2RTX/ is an example of using device groups, which is one of the ways to do multi gpu.

@nanokatze Ya device groups is the correct way for SLI/CrossFire like parody.


chore: removing cocoapods support

Summary of Changes
Removing parts, found so far, related to CocoaPods.
By submitting this pull request, you are confirming the following:

I have reviewed the Contribution Guidelines.
I have performed a self-review of my own code.
I have updated my repository to match the develop branch.
I have included test data or screenshots that prove my fix is effective or that my feature works.
I have checked that all tests work and swiftlint is not throwing any errors/warnings.

CI failure is fixed in #839

It seems that there's some unrelated to changes CI issues. But speaking about the changes itself they looks good to me.


Jib a pre-packaged JAR/WAR

Description of the issue:
Create a container image from a given executable Fat JAR or WAR.
E.g., jib app.jar --image=gcr.io/my-registry/app
Potentially having a plugin option that simply operate on the final artifact.

The command line tools is a great.
FTR, Jib 1.4.0 plugins now have <containerizingMode>packaged that simply picks up the final JAR, which addressed a number of issues when not using a JAR. However, using the packaged mode with a fat/shaded JAR is not well supported and should be avoided. The support for fat/shaded JAR/WAR are being tracked in #1857.

FTR:
We have the Jib Core library upon which our Jib build plugins were built. The example there shows how easily you can write a program to do custom containerization.
And actually there's a non-official command-line tool called Cram based on Jib Core that can cover this scenario with relative ease (example).

Huh, I didn't remember that.  Nice find 😄

As updated in https://github.com/GoogleContainerTools/jib/issues/1859#issuecomment-528526823, this is already implemented in Jib CLI now. Closing this issue.


Is sqflite compressing the json data?

From what I assumed then what I read the answer is "no!", SQLite does not compress text data, let alone sqflite.
That wouldn't make sense as it's a TEXT field where normal people typically try to find data quickly (where clause). If there was a compression, sqflite would have to decompress the compressed field of all rows for each query that has a where on that column.
Feel free to reopen if you have good news.


Fix line continuation issue in IPv6 detect

http://cdn.pasteraw.com/jqqkycnrew3bjl7tnwrfc7dkg6hlikd
- hosts: localhost
  gather_facts: no
  tasks:
    - name: Try with > continuation
      debug:
        msg: >
          {{ 'yes' | bool }}
    - name: Try with | continuation
      debug:
        msg: |
          {{ 'yes' | bool }}
    - name: Try with |- continuation
      debug:
        msg: |-
          {{ 'yes' | bool }}

PLAY [localhost] ***************************************************************

TASK [Try with > continuation] *************************************************
ok: [localhost] => {
    "msg": "True\n"
}

TASK [Try with | continuation] *************************************************
ok: [localhost] => {
    "msg": "True\n"
}

TASK [Try with |- continuation] ************************************************
ok: [localhost] => {
    "msg": true
}


[jax2tf] Added a test for SavedModel with pytrees

This was in response to an external user running into problems
with converting and saving a SavedModel for a function where
one of the arguments is a dict. This test demonstrates that
this works, both for the conversion, and for the saving/restoring.

@rxsang please take a look

@voutcn PTAL
voutcn


XCTestAssertNoThrow for 3.1

Adds XCTestAssertNoThrow function
Adds two test for testing XCTestAssertNoThrow

This has already been merged to master in #184, but I was asked by @briancroom to open a PR against the swift-3.1-branch.

cc @briancroom ready for you.

@swift-ci please test

@briancroom OSX seems to have crashed instantaneously

@swift-ci please test OS X

Same problem

@shahmishal Hey Mishal..sorry to trouble you again, but the OS X PR CI seems to be having a hard time here. Could you take a look when you get a chance?

@swift-ci test OS X

Looks like it's working - thanks, @shahmishal!

Ah, it looks like it failed due to NSHost errors.

looks like stuff was merge in, so another CI test is needed

@swift-ci please test

@briancroom Looks like everything has passed!

👌thanks @ArtSabintsev!

My pleasure - thank you!


Adding the Football Player Club Info

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #(issue_no)
Replace issue_no with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

First iteration of the feature. I am working on making the code more object-oriented and readable. The Documentation would follow in the following pull requests.

Refactored the code to make it more modular.

Refactored the code to make it more modular.

@shahidshakil Are you going to add any more features?? or the ReadMe??

@shahidshakil Are you going to add any more features?? or the ReadMe??

I will perform the requested changes and add a readme file.

@shahidshakil Any Updates?

@all-contributors please add @shahidshakil  for code


semgrep: 1.0.0 -> 1.14.0

Description of changes

Update to 1.14.0
Also fixed update script
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I haven't built the changes yet, but this draft LGTM.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1950


Create a node API benchmark based on zenoh

Adds the simple, unscientific benchmark example used to create the benchmarks reported in https://github.com/dora-rs/dora/discussions/169#discussioncomment-4593726.

New results:
ZENOH:
Latency:
size 0x0     : 125.854µs
size 0x8     : 125.051µs
size 0x40    : 134.696µs
size 0x200   : 143.422µs
size 0x800   : 140.832µs
size 0x1000  : 143.49µs
size 0x4000  : 131.922µs
size 0xa000  : 121.403µs
size 0x64000 : 400.116µs
Throughput:
size 0x0     : 319920 messages per second
size 0x8     : 439601 messages per second
size 0x40    : 403327 messages per second
size 0x200   : 350658 messages per second
size 0x800   : 55052 messages per second
size 0x1000  : 47572 messages per second
size 0x4000  : 14316 messages per second
size 0xa000  : 7120 messages per second
size 0x64000 : 917 messages per second

ICEORYX:
Latency:
size 0x0     : 79.726µs
size 0x8     : 51.027µs
size 0x40    : 45.64µs
size 0x200   : 63.176µs
size 0x800   : 64.402µs
size 0x1000  : 54.382µs
size 0x4000  : 58.624µs
size 0xa000  : 61.343µs
size 0x64000 : 77.179µs
Throughput:
size 0x0     : 278009 messages per second
size 0x8     : 262613 messages per second
size 0x40    : 223301 messages per second
size 0x200   : 145858 messages per second
size 0x800   : 71805 messages per second
size 0x1000  : 43043 messages per second
size 0x4000  : 13365 messages per second
size 0xa000  : 5279 messages per second
size 0x64000 : 1119 messages per second

These are interesting results. I am a bit surprised by the latency increase for size 0x64000, as the size of packet that is sent on the network does not change, it is just an "address" the data.   I would also like to know which version of zenoh have you used to run the tests, as the latest version has some important improvements on latency and that may reduce the gap between zenoh and ICEOryx.
That said, considering the fact that  zero-copy is in Zenoh an optimisation while  IceOryx has been designed ground-up for that purpose, I think that that looks quite good.
We'll do some investigation to see if we can reproduce the strange increase in size for 0x64000. Will keep you posted.
Don't hesitate to reach us out (on Zenoh's discord https://discordservers.com/server/914168414178779197) if you have questions.

@kydos Thanks for taking a look! Please keep in mind that these benchmarks are very basic and not scientific at all. So the higher latency for 0x64000 might not be caused by zenoh at all.

I would also like to know which version of zenoh have you used to run the tests, as the latest version has some important improvements on latency and that may reduce the gap between zenoh and ICEOryx.

We are currently using a pinned dependency on commit https://github.com/eclipse-zenoh/zenoh/commit/79a136e4fd90b11ff5d775ced981af53c4f1071b. We tried to update to v0.6.0-beta  when it was released, but ran into some deadlock problems. (We saw that you released a v0.7.0-rc version before the holidays and we plan to try it soon.)

Don't hesitate to reach us out (on Zenoh's discord https://discordservers.com/server/914168414178779197) if you have questions.

Thanks a lot!

This can be closed at it has been merged as part of #162.


cargo-shuttle: add platform version switches

Description of change
Added a platform_version cargo-shuttle argument which can be set as environment as well. Up to this point we can use it against the new platform for:

project start
project status
project list
project delete

How has this been tested? (if applicable)
Tested locally.
Notes
cargo shuttle deploy is not supported yet, but that will happen in a follow up PR.

Wouldn't it be better to put all of that behind a trait, and just switch the implementation ? With anything that can be shared being in standalone functions ? It's a larger rework, but this would make things clearer rather than if/else and v1/v2.


[#121680663]brief overview page: add link to dos contract

https://www.pivotaltracker.com/story/show/121680663

Looks good :+1:


RBD Encryption improvements that need addressing

Ensure volume creation is complete before responding with a volume match for a CreateVolume request

Comment: https://github.com/ceph/ceph-csi/pull/697/files?file-filters[]=.go#r356896828
The intention is to note the status of creation and later, either complete the creation if certain steps are missed (like adding the encryption attribute to the image) or garbage collect the image and the reservation, and create afresh.
This provides a defense against any duplicate responses that the CO may have processed, to ensure the controller only responded when an entire CreateVolume call is complete.

processEncryptedDevice should check if device is already encrypted, prior to invoking encryptDevice and update encryption parameter on the image.

Comment: https://github.com/ceph/ceph-csi/pull/697/files?file-filters[]=.go#r355185194
This is to ensure if the plugin fails between calling EncryptVolume and SaveRbdImageEncryptionStatus in encryptDevice, we do not encrypt it again (which will not happen in the current code, as the device format will not be an empty string in processEncryptedDevice), but we need to update the SaveRbdImageEncryptionStatus on detecting such cases.

Optimize checks in detachRBDImageOrDeviceSpec to avoid checking for encrypted devices based on the image stash

Comment: https://github.com/ceph/ceph-csi/pull/697/files?file-filters[]=.go#r355185378

@ShyamsundarR I'd like to re-iterate on first task here:
current implementation in case of successful volume creation but failed image-meta step will get here
And before returning successful response it will call ensureEncryptionMetadataSet which will update this image-meta key to make sure that image is ready to be used for attach process.
Does this satisfy the requirement?
The only place I can see this to make things bad is if volume was already attached and encrypted and then CreateVolume for the same volume comes in and forces metadata to be updated to requiredEncryption, but I don't see how CreateVolume request can come after volume was attached at least once.

@ShyamsundarR I'd like to re-iterate on first task here:
current implementation in case of successful volume creation but failed image-meta step will get here And before returning successful response it will call ensureEncryptionMetadataSet which will update this image-meta key to make sure that image is ready to be used for attach process.
Does this satisfy the requirement?
The only place I can see this to make things bad is if volume was already attached and encrypted and then CreateVolume for the same volume comes in and forces metadata to be updated to requiredEncryption, but I don't see how CreateVolume request can come after volume was attached at least once.

hi vasyl-purchel, can you tell me what is image-meta? and where can i find it ?

hi @fanchenxu-ship , image-meta is metadata of an rbd image in ceph, so can be found with rbd image-meta get <image> <key> command


Can't select some dates in week scope at month changes

Using week scope I'm unable to select dates from next/previous months. It seems that it only enables the month with the highest number of days shown. Using month scope everything work fine. Is this the expected behavior? How can I make all days selectable?

Looking at the code I see that this is the intended behavior since collectionView shouldSelectItemAtIndexPath at FSCalendar.m just return NO if selected date isn't in the current month.

I'm facing the same issue here
This one if I'm at Month's scope and selected day 1

Then if I try reverting to Week's scope

And then if I go to next month from Week's scope.


Convert double to int in lambda task output?

I have a legacy server that I need to reach through a Conductor http task that only accepts numeric inputs as integers and will reject any floating point number with an error.
I searched for this issue and came across this: #1200
But that is referring to converting an input int into a double, which is not what I am looking for. I want to convert the output into an int.
Is this possible?
edit:
for reference, I am using the docker-compose container as a dev environment
edit2:
as a visual example:
// input (this input comes from either a lambda task or a JSON JQ transform task)
{     "id": 1 }
// expected serialized output (http task body)
"{ \"id\": 1}"
// actual serialized output (pulled from debugger at destination API)
"{\"id\": 1.0}"

{   "name": "test_http_int_wf1",   "version": 0,   "input": {     "id": 1   },   "workflowDef": {     "name": "test_http_int_wf1",     "description": "test_http_int_wf1",     "version": 1,     "tasks": [       {         "name": "jq_1",         "taskReferenceName": "jq_1",         "type": "JSON_JQ_TRANSFORM",         "inputParameters": {           "id": "${workflow.input.id}",           "queryExpression": "{ id_o: .id }"         }       },       {         "name": "int_http_task",         "taskReferenceName": "int_http_task",         "inputParameters": {           "http_request": {             "uri": "https://ent0oa4isdccpe5.m.pipedream.net",             "method": "GET",             "contentType": "application/json",             "accept": "application/json",             "body": {               "id_k": "${jq_1.output.result.id_o}"             }           }         },         "type": "HTTP"       }     ]   } }
I tried running the above workflow in the latest version of Conductor. You can see that the workflow input is {"id": 1} which is used in the body of the JSON_JQ_TRANSFORM task and the output of that task in the HTTP Task.
See screenshot below, the input is NOT converted to a Double. Am i missing some step in reproducing the issue?

Thanks. Yes, I gave a simplified version of what I am doing, and when hard-coding an int, it does seem to output correctly.
So, what I did not include in my example was the step before the JQ transform which was an http response.
for example, the http response body is a simple int:
{
"response": {
"headers": {
"Server": ["nginx/1.10.3 (Ubuntu)"],
"Connection": ["keep-alive"],
"Content-Length": ["8"],
"Date": ["Thu, 04 Feb 2021 01:58:34 GMT"]
},
"reasonPhrase": "Success",
"body": 10784123,
"statusCode": 200
}
}
so, replace {id: 1} with {id: "${http_step.output.response.body}"} where http_step is an http task that results in the output above


Let tape$TestCb return a promise

Let tape$TestCb return a promise
If you want to use async/await with Tape you will need to prefix your test function with async, e.g.
test('Promise resolves true', async (assert: tape$Context) => {
  const result = await promiseFunction();
  assert.true(result);
  assert.end();
}

But this will cause type checking to fail as the callback no longer returns void.

Ah well, I just started using async functions, in that time I forgot to include them in the definitions...
Does our test setup support async / await syntax?
Would like to see that test case in the tape test file

Does our test setup support async / await syntax?
Would like to see that test case in the tape test file

Yes, anything that Flow can read is valid flow-typed test code


Paper outline

Thought I'd get a draft/outline of an eventual paper up here. Hope this isn't way too premature! :)

Makes sense, and this prevents @apragsdale and I from suggesting we do it in R markdown. 🤣

Wow! This looks really good, thanks @apragsdale! Do we want to include this here though, or have a separate repository for the manuscript?

Yes, this is awesome thanks @apragsdale! But I second the idea of spinning this into its own repo. There's no point in weighing down the software repo here with latex etc, and it'll make it easier to keep track of issues on the paper if we can use the issue tracker for that. Small focused repos are good.

Ok, will do! That makes perfect sense to me. I'll make a demes paper repo and share.


Feature to get message from telegram

Use telegram api to receive message

Hi, I'd would like to work on this issue

The idea is to add a method to retrieve messages sent from the chat and store it locally
Issue assigned to @bayucakra20
🌟 Star it 🍴Fork it 🤝 Contribute to it!
Happy Coding..
Feel free to drop in https://discord.gg/e47wmTW

The idea is to add a method to retrieve messages sent from the chat and store it locally
Issue assigned to @bayucakra20
🌟 Star it 🍴Fork it 🤝 Contribute to it!
Happy Coding..
Feel free to drop in https://discord.gg/e47wmTW

Hi @rexdivakar , for receiving messages of chatbot, actually i can use from getUpdates api which currently method is already there and I can use it, is it enough to use that? or should I use other api like getMessages ? and for storing data locally, I would like to store it in csv file, or do you have any suggestion? thank you

hey @bayucakra20  yes u can use getUpdates  and please store the data (chat details, user details) in a json format for easier use in future.

I see, okay will use json format then, thank you @rexdivakar for the suggestion


mistake on NtQuerySecurityObject page

There's a mistake on this page - it says that the SecurityInformation argument is a pointer, when actually it's a ULONG and thus passed by value.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 31063e0f-7395-ae8f-d700-aebadeca7527
Version Independent ID: db6924d6-9530-961d-16d4-52969ae79600
Content: NtQuerySecurityObject function (ntifs.h) - Windows drivers
Content Source: wdk-ddi-src/content/ntifs/nf-ntifs-ntquerysecurityobject.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

There's also a contradiction - it says that SecurityDescriptor will be a relative SD, but then in the first sentence of Remarks mentions absolute SDs.

First sentence of Remarks describes SECURITY_DESCRIPTOR.

Thanks again, @hsebs , this is also now fixed!


npm audit fail

What are you trying to achieve?
Run npm audit and get no errors.
What do you get instead?
Low severity issue on codeceptjs > inquirer > lodash
lodash version should be greater or equal then 4.17.5

Provide console output if related. Use --verbose mode for more details.

{
  "actions": [
    {
      "action": "review",
      "module": "lodash",
      "resolves": [
        {
          "id": 577,
          "path": "codeceptjs>inquirer>lodash",
          "dev": false,
          "optional": false,
          "bundled": false
        }
      ]
    }
  ],
  "advisories": {
    "577": {
      "findings": [
        {
          "version": "3.10.1",
          "paths": [
            "codeceptjs>inquirer>lodash"
          ],
          "dev": false,
          "optional": false,
          "bundled": false
        }
      ],
      "id": 577,
      "created": "2018-04-24T14:27:02.796Z",
      "updated": "2018-04-24T14:27:13.049Z",
      "deleted": null,
      "title": "Prototype Pollution",
      "found_by": {
        "name": "Olivier Arteau (HoLyVieR)"
      },
      "reported_by": {
        "name": "Olivier Arteau (HoLyVieR)"
      },
      "module_name": "lodash",
      "cves": [
        "CVE-2018-3721"
      ],
      "vulnerable_versions": "<4.17.5",
      "patched_versions": ">=4.17.5",
      "overview": "Versions of `lodash` before 4.17.5 are vulnerable to prototype pollution. \n\nThe vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects.\n\n",
      "recommendation": "Update to version 4.17.5 or later.",
      "references": "- [HackerOne Report](https://hackerone.com/reports/310443)",
      "access": "public",
      "severity": "low",
      "cwe": "CWE-471",
      "metadata": {
        "module_type": "",
        "exploitability": 1,
        "affected_components": ""
      },
      "url": "https://npmjs.com/advisories/577"
    }
  },
  "muted": [],
  "metadata": {
    "vulnerabilities": {
      "info": 0,
      "low": 1,
      "moderate": 0,
      "high": 0,
      "critical": 0
    },
    "dependencies": 136,
    "devDependencies": 35347,
    "optionalDependencies": 792,
    "totalDependencies": 35483
  },
  "runId": "fa7f1cc0-c632-44b6-a25b-e7d7b9610b03"
}

Provide test source code if related

// paste test

Details

CodeceptJS version: 1.4.6
NodeJS Version: 8.12.0
Operating System: MacOS Mojave
Protractor || WebDriverIO || Nightmare version (if related)
Configuration file:

# paste suite config here

You can make a PR for this

I made a PR here https://github.com/Codeception/CodeceptJS/pull/1327 but I guess it needs some additional review before it is good to go

Nice! Thank you!

Issue closed. PR merged. https://github.com/Codeception/CodeceptJS/pull/1352


Got "fatal error: 'android/text/TextUtils.h' file not found"

Was getting a bit code error (just upgraded to Xcode 7) so decided to compile j2objc on my machine.  After which I got this error, any hints?

Should be fixed now, as the file is in my local build and I just synced to our GitHub repository.


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #20.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #20

Similar to https://github.com/conda-forge/pycolmap-feedstock/pull/21, we just need to bump the build number and then we are ready to merge.


feat(transformer/async-to-generator): handle arrow-function correctly

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6640  👈
#6634
#6633
#6632
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite

Merge activity

Oct 17, 4:41 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

My suggestions for follow-ups (which you are free to ignore!):
Small things

exit_expression: Style: Convert the 3-branch if / else if into a match.
exit_statement: Style: Reduce indentation by starting function with let Statement::FunctionDeclaration(func) = stmt else { return };
exit_statement: Function::id field is always Some for function declarations. Replace if let Some(id) = func.id.take() { with let id = func.id.take().unwrap(), and remove the else branch.
exit_expression: No need to check body.r#async(). await cannot be used in a non-async function, so *body.r#async() is always true here.

Refactor
Instead of ctx.ancestry.ancestors().find_map() and then if in_async_function ..., use a loop and return to bail out if nothing to be done. e.g.:
// Exit if this `await` is top level, or in an async generator function
for ancestor in ctx.ancestors() {
    match ancestor {
        Ancestor::FunctionBody(body) => {
            if *body.generator() {
                return;
            }
            break;
        }
        // Arrow functions are never generators
        Ancestor::ArrowFunctionExpressionBody(_) => break,
        Ancestor::ProgramBody(_) => return,
        _ => {}
    }
}

// Convert the expression to yield
*expr = ctx.ast.expression_yield(
    SPAN,
    false,
    Some(ctx.ast.move_expression(&mut await_expr.argument)),
);

Personally I think this is a bit clearer, though it's a matter of taste. If you prefer how it is, feel free to ignore me.
Avoid constructing a new Function
transform_function doesn't need to construct a new Function, it can mutate the existing one.

Take ownership of the Expresson / Statement in exit_expression and exit_statement via ctx.ast.move_expression / move_statement.
Get the owned Box<Function> via this pattern.
Pass Box<'a, Function<'a>> into transform_function.

Getting ownership by matching twice on expr being an Expression::Function is an ugly pattern, but the upside is (a) less operations and allocations and (b) simplify transform_function because only one move_* operation, instead of loads of little ones.
Note: I'm suggesting passing Box<Function> (not Function) into transform_function, because:

Box is only 8 bytes. You can avoid having a Function (104 bytes) on the stack.
Then you don't have to allocate the Function back into arena. Box<Function> already has it in arena, and you can mutate it in place.

@overlookmotel Good suggestion, I will keep it in mind!


PowerShell script identified for use is no linger linked

The link provided in the documentation to the PowerShell script is no longer pointing to a relevant script for use in setting up the Remote Desktop Services (RDS) Deployment in the Azure marketplace.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f7279474-d477-e029-e1b9-c8b8342077a6
Version Independent ID: e84b3157-2b40-54ee-183f-23dc7cc81ad2
Content: Seamlessly deploy RDS with ARM and Azure Marketplace
Content Source: WindowsServerDocs/remote/remote-desktop-services/rds-in-azure.md
Product: windows-server
Technology: remote-desktop-services
GitHub Login: @lizap
Microsoft Alias: elizapo

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


CumulusTV crashes in loop when I open Live Channels

I have a single M3U playlist loaded into CumulusTV (I created it on my smartphone, synced with gdrive to the CumulusTV app on my Shield TV).
Sometimes, when I go to open the Live Channels app, the CumulusTV app crashes (the Android dialog appears), if I click "ok", it crashes again and again in loop.
Once I manage to kill the Live Channels app, if I open the CumulusTV app, I see that my m3u playlist isn't loaded. I have to click "sync" few times and wait a minute to see it appear again.
I guess the problem is that my M3U playlist is loaded through an Heroku app (because I need to parse the playlist to fix some meta data), and it takes usually 15 seconds to load.
Any solutions for this problem?

I have crash reporting set up, so I should see when the app crashes, although I don't know why there's an issue in your case offhand.

I've been seeing the same issue.  Solution is to double tap the home button to bring up the task switch and close live channels, then open CumulusTV and wait 5-10 seconds for it to sync.  Then Live Channels works fine.  Seems you have to do this every time you reboot or resume the Android TV from sleep.

I guess I should say that the above is a workaround, not exactly a "solution"...  This first started happening with version 1.7.3 by the way.

Try the next update and let me know what happens.

@Fleker If you are referring to 1.7.5, it has the same issue.

This must be an issue related to syncing the first time. I think a potential solution would be to preload data in the system whenever there is a reboot.

See #254