Call to a member function connection() on null with PHP 7.1

I was using this effectively until I upgraded to 7.1. I dont think thats an issue as I havent been able to find anyone else with it, but the error message is not descriptive so im not sure whats going on. With the basic code example:
$responses = wait(parallelMap([
      'https://google.com/',
      'https://github.com/',
      'https://stackoverflow.com/',
    ], function ($url) {
      return file_get_contents($url);
    }));

I get this error:
An uncaught Exception was encountered
Type: Amp\MultiReasonException

Message: Multiple errors encountered

Filename: /home/orgname/public_html/vendor/amphp/parallel-functions/src/functions.php

Line Number: 56

Backtrace:

File: /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php
Line: 76
Function: send

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 130
Function: Amp\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Deferred.php
Line: 45
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/functions.php
Line: 466
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/ResolutionQueue.php
Line: 55
Function: Amp\Promise\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Failure.php
Line: 29
Function: __invoke

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 125
Function: onResolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 155
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php
Line: 95
Function: fail

File: /home/orgname/public_html/vendor/amphp/amp/lib/Failure.php
Line: 29
Function: Amp\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 125
Function: onResolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 155
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php
Line: 95
Function: fail

File: /home/orgname/public_html/vendor/amphp/amp/lib/Failure.php
Line: 29
Function: Amp\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 125
Function: onResolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 155
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php
Line: 95
Function: fail

File: /home/orgname/public_html/vendor/amphp/amp/lib/Failure.php
Line: 29
Function: Amp\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 125
Function: onResolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 155
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php
Line: 95
Function: fail

File: /home/orgname/public_html/vendor/amphp/amp/lib/Failure.php
Line: 29
Function: Amp\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 125
Function: onResolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php
Line: 155
Function: resolve

File: /home/orgname/public_html/vendor/amphp/amp/lib/Deferred.php
Line: 55
Function: fail

File: /home/orgname/public_html/vendor/amphp/amp/lib/functions.php
Line: 214
Function: fail

File: /home/orgname/public_html/vendor/amphp/amp/lib/Loop/NativeDriver.php
Line: 130
Function: Amp\Promise\{closure}

File: /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php
Line: 134
Function: dispatch

File: /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php
Line: 72
Function: tick

File: /home/orgname/public_html/vendor/amphp/amp/lib/Loop.php
Line: 84
Function: run

File: /home/orgname/public_html/vendor/amphp/amp/lib/functions.php
Line: 170
Function: run

File: /home/orgname/public_html/application/controllers/Lists.php
Line: 63
Function: Amp\Promise\wait

File: /home/orgname/public_html/index.php
Line: 315
Function: require_once

if i print out out the error on line 56 of /home/orgname/public_html/vendor/amphp/parallel-functions/src/functions.php
i see a very long error, here's some of it:
Array ( [0] => Amp\Parallel\Context\ContextException Object ( [message:protected] => Starting the process failed [string:Exception:private] => [code:protected] => 0 [file:protected] => /home/orgname/public_html/vendor/amphp/parallel/lib/Context/Process.php [line:protected] => 197 [trace:Exception:private] => Array ( [0] => Array ( [function] => Amp\Parallel\Context\{closure} [class] => Amp\Parallel\Context\Process [type] => -> [args] => Array ( ) ) [1] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php [line] => 73 [function] => throw [class] => Generator [type] => -> [args] => Array ( [0] => Amp\Parallel\Context\ContextException Object ( [message:protected] => Starting the process timed out [string:Exception:private] => [code:protected] => 0 [file:protected] => /home/orgname/public_html/vendor/amphp/parallel/lib/Context/Internal/ProcessHub.php [line:protected] => 118 [trace:Exception:private] => Array ( [0] => Array ( [function] => Amp\Parallel\Context\Internal\{closure} [class] => Amp\Parallel\Context\Internal\ProcessHub [type] => -> [args] => Array ( ) ) [1] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Coroutine.php [line] => 73 [function] => throw [class] => Generator [type] => -> [args] => Array ( [0] => Amp\TimeoutException Object ( [message:protected] => Operation timed out [string:Exception:private] => [code:protected] => 0 [file:protected] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line:protected] => 214 [trace:Exception:private] => Array ( [0] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/NativeDriver.php [line] => 130 [function] => Amp\Promise\{closure} [args] => Array ( [0] => r [1] => ) ) [1] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 134 [function] => dispatch [class] => Amp\Loop\NativeDriver [type] => -> [args] => Array ( [0] => 1 ) ) [2] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 72 [function] => tick [class] => Amp\Loop\Driver [type] => -> [args] => Array ( ) ) [3] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop.php [line] => 84 [function] => run [class] => Amp\Loop\Driver [type] => -> [args] => Array ( ) ) [4] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line] => 170 [function] => run [class] => Amp\Loop [type] => :: [args] => Array ( [0] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => [promise] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => Closure Object ( [this] => Amp\Coroutine Object *RECURSION* [parameter] => Array ( [$exception] => [$value] => ) ) [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => Array ( [0] => Array *RECURSION* [1] => Array ( ) ) [resolved:Amp\Coroutine:private] => [result:Amp\Coroutine:private] => [onResolved:Amp\Coroutine:private] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => ) [parameter] => Array ( [$e] => [$v] => ) ) [resolutionTrace:Amp\Coroutine:private] => ) ) ) ) ) [5] => Array ( [file] => /home/orgname/public_html/application/controllers/Lists.php [line] => 63 [function] => Amp\Promise\wait [args] => Array ( [0] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => Closure Object ( [this] => Amp\Coroutine Object *RECURSION* [parameter] => Array ( [$exception] => [$value] => ) ) [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => Array ( [0] => Array *RECURSION* [1] => Array ( ) ) [resolved:Amp\Coroutine:private] => [result:Amp\Coroutine:private] => [onResolved:Amp\Coroutine:private] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => ) [parameter] => Array ( [$e] => [$v] => ) ) [resolutionTrace:Amp\Coroutine:private] => ) ) ) [6] => Array ( [file] => /home/orgname/public_html/system/core/CodeIgniter.php [line] => 532 [function] => testme [class] => Lists [type] => -> [args] => Array ( ) ) [7] => Array ( [file] => /home/orgname/public_html/index.php [line] => 315 [args] => Array ( [0] => /home/orgname/public_html/system/core/CodeIgniter.php ) [function] => require_once ) ) [previous:Exception:private] => ) ) ) [2] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Failure.php [line] => 29 [function] => Amp\{closure} [class] => Amp\Coroutine [type] => -> [args] => Array ( [0] => Amp\TimeoutException Object ( [message:protected] => Operation timed out [string:Exception:private] => [code:protected] => 0 [file:protected] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line:protected] => 214 [trace:Exception:private] => Array ( [0] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/NativeDriver.php [line] => 130 [function] => Amp\Promise\{closure} [args] => Array ( [0] => r [1] => ) ) [1] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 134 [function] => dispatch [class] => Amp\Loop\NativeDriver [type] => -> [args] => Array ( [0] => 1 ) ) [2] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 72 [function] => tick [class] => Amp\Loop\Driver [type] => -> [args] => Array ( ) ) [3] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop.php [line] => 84 [function] => run [class] => Amp\Loop\Driver [type] => -> [args] => Array ( ) ) [4] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line] => 170 [function] => run [class] => Amp\Loop [type] => :: [args] => Array ( [0] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => [promise] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => Closure Object ( [this] => Amp\Coroutine Object *RECURSION* [parameter] => Array ( [$exception] => [$value] => ) ) [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => Array ( [0] => Array *RECURSION* [1] => Array ( ) ) [resolved:Amp\Coroutine:private] => [result:Amp\Coroutine:private] => [onResolved:Amp\Coroutine:private] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => ) [parameter] => Array ( [$e] => [$v] => ) ) [resolutionTrace:Amp\Coroutine:private] => ) ) ) ) ) [5] => Array ( [file] => /home/orgname/public_html/application/controllers/Lists.php [line] => 63 [function] => Amp\Promise\wait [args] => Array ( [0] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => Closure Object ( [this] => Amp\Coroutine Object *RECURSION* [parameter] => Array ( [$exception] => [$value] => ) ) [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => Array ( [0] => Array *RECURSION* [1] => Array ( ) ) [resolved:Amp\Coroutine:private] => [result:Amp\Coroutine:private] => [onResolved:Amp\Coroutine:private] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => ) [parameter] => Array ( [$e] => [$v] => ) ) [resolutionTrace:Amp\Coroutine:private] => ) ) ) [6] => Array ( [file] => /home/orgname/public_html/system/core/CodeIgniter.php [line] => 532 [function] => testme [class] => Lists [type] => -> [args] => Array ( ) ) [7] => Array ( [file] => /home/orgname/public_html/index.php [line] => 315 [args] => Array ( [0] => /home/orgname/public_html/system/core/CodeIgniter.php ) [function] => require_once ) ) [previous:Exception:private] => ) [1] => ) ) [3] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php [line] => 125 [function] => onResolve [class] => Amp\Failure [type] => -> [args] => Array ( [0] => Closure Object ( [this] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => [resolved:Amp\Coroutine:private] => 1 [result:Amp\Coroutine:private] => Amp\Failure Object ( [exception:Amp\Failure:private] => Amp\Parallel\Context\ContextException Object *RECURSION* ) [onResolved:Amp\Coroutine:private] => [resolutionTrace:Amp\Coroutine:private] => ) [parameter] => Array ( [$exception] => [$value] => ) ) ) ) [4] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Internal/Placeholder.php [line] => 155 [function] => resolve [class] =><EMAIL_ADDRESS>[type] => -> [args] => Array ( [0] => Amp\Failure Object ( [exception:Amp\Failure:private] => Amp\TimeoutException Object ( [message:protected] => Operation timed out [string:Exception:private] => [code:protected] => 0 [file:protected] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line:protected] => 214 [trace:Exception:private] => Array ( [0] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/NativeDriver.php [line] => 130 [function] => Amp\Promise\{closure} [args] => Array ( [0] => r [1] => ) ) [1] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 134 [function] => dispatch [class] => Amp\Loop\NativeDriver [type] => -> [args] => Array ( [0] => 1 ) ) [2] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 72 [function] => tick [class] => Amp\Loop\Driver [type] => -> [args] => Array ( ) ) [3] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop.php [line] => 84 [function] => run [class] => Amp\Loop\Driver [type] => -> [args] => Array ( ) ) [4] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line] => 170 [function] => run [class] => Amp\Loop [type] => :: [args] => Array ( [0] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => [promise] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => Closure Object ( [this] => Amp\Coroutine Object *RECURSION* [parameter] => Array ( [$exception] => [$value] => ) ) [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => Array ( [0] => Array *RECURSION* [1] => Array ( ) ) [resolved:Amp\Coroutine:private] => [result:Amp\Coroutine:private] => [onResolved:Amp\Coroutine:private] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => ) [parameter] => Array ( [$e] => [$v] => ) ) [resolutionTrace:Amp\Coroutine:private] => ) ) ) ) ) [5] => Array ( [file] => /home/orgname/public_html/application/controllers/Lists.php [line] => 63 [function] => Amp\Promise\wait [args] => Array ( [0] => Amp\Coroutine Object ( [generator:Amp\Coroutine:private] => Generator Object ( ) [onResolve:Amp\Coroutine:private] => Closure Object ( [this] => Amp\Coroutine Object *RECURSION* [parameter] => Array ( [$exception] => [$value] => ) ) [immediate:Amp\Coroutine:private] => 1 [exception:Amp\Coroutine:private] => [value:Amp\Coroutine:private] => Array ( [0] => Array *RECURSION* [1] => Array ( ) ) [resolved:Amp\Coroutine:private] => [result:Amp\Coroutine:private] => [onResolved:Amp\Coroutine:private] => Closure Object ( [static] => Array ( [resolved] => [value] => [exception] => ) [parameter] => Array ( [$e] => [$v] => ) ) [resolutionTrace:Amp\Coroutine:private] => ) ) ) [6] => Array ( [file] => /home/orgname/public_html/system/core/CodeIgniter.php [line] => 532 [function] => testme [class] => Lists [type] => -> [args] => Array ( ) ) [7] => Array ( [file] => /home/orgname/public_html/index.php [line] => 315 [args] => Array ( [0] => /home/orgname/public_html/system/core/CodeIgniter.php ) [function] => require_once ) ) [previous:Exception:private] => ) ) ) ) [5] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Deferred.php [line] => 55 [function] => fail [class] =><EMAIL_ADDRESS>[type] => -> [args] => Array ( [0] => Amp\TimeoutException Object ( [message:protected] => Operation timed out [string:Exception:private] => [code:protected] => 0 [file:protected] => /home/orgname/public_html/vendor/amphp/amp/lib/functions.php [line:protected] => 214 [trace:Exception:private] => Array ( [0] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/NativeDriver.php [line] => 130 [function] => Amp\Promise\{closure} [args] => Array ( [0] => r [1] => ) ) [1] => Array ( [file] => /home/orgname/public_html/vendor/amphp/amp/lib/Loop/Driver.php [line] => 134 [function] => dispatch [class] => Amp\Loop\NativeDriver [type] => -> [args] => Array ( [0] => 1 ) ) [2] => Array ( [file] =>

any help would be appreciated!

I'm getting this with the first reason:
{
  "message": "Uncaught Error in worker with message \"Call to a member function connection() on null\" and code \"0\"",
  "exception": "Symfony\\Component\\Debug\\Exception\\FatalThrowableError",
  "file": "/var/www/vendor/amphp/parallel/lib/Worker/Internal/TaskFailure.php",
  "line": 45,
  "trace": [
    {
      "file": "/var/www/vendor/amphp/parallel/lib/Worker/TaskWorker.php",
      "line": 126,
      "function": "promise",
      "class": "Amp\\Parallel\\Worker\\Internal\\TaskFailure",
      "type": "->"
    },
    {
      "function": "Amp\\Parallel\\Worker\\{closure}",
      "class": "Amp\\Parallel\\Worker\\TaskWorker",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Coroutine.php",
      "line": 76,
      "function": "send",
      "class": "Generator",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Internal/Placeholder.php",
      "line": 130,
      "function": "Amp\\{closure}",
      "class": "Amp\\Coroutine",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Coroutine.php",
      "line": 81,
      "function": "resolve",
      "class": "Amp\\Coroutine",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Internal/Placeholder.php",
      "line": 130,
      "function": "Amp\\{closure}",
      "class": "Amp\\Coroutine",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Coroutine.php",
      "line": 81,
      "function": "resolve",
      "class": "Amp\\Coroutine",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Internal/Placeholder.php",
      "line": 130,
      "function": "Amp\\{closure}",
      "class": "Amp\\Coroutine",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Deferred.php",
      "line": 45,
      "function": "resolve",
      "class"<EMAIL_ADDRESS>      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/byte-stream/lib/ResourceInputStream.php",
      "line": 99,
      "function": "resolve",
      "class": "Amp\\Deferred",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Loop/NativeDriver.php",
      "line": 206,
      "function": "Amp\\ByteStream\\{closure}",
      "class": "Amp\\ByteStream\\ResourceInputStream",
      "type": "::"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Loop/NativeDriver.php",
      "line": 97,
      "function": "selectStreams",
      "class": "Amp\\Loop\\NativeDriver",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Loop/Driver.php",
      "line": 134,
      "function": "dispatch",
      "class": "Amp\\Loop\\NativeDriver",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Loop/Driver.php",
      "line": 72,
      "function": "tick",
      "class": "Amp\\Loop\\Driver",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/Loop.php",
      "line": 84,
      "function": "run",
      "class": "Amp\\Loop\\Driver",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/amphp/amp/lib/functions.php",
      "line": 170,
      "function": "run",
      "class": "Amp\\Loop",
      "type": "::"
    },
    {
      "file": "/var/www/vendor/spatie/laravel-collection-macros/src/macros/parallelMap.php",
      "line": 31,
      "function": "Amp\\Promise\\wait"
    },
    {
      "function": "{closure}",
      "class": "Illuminate\\Database\\Eloquent\\Collection",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Support/Traits/Macroable.php",
      "line": 107,
      "function": "call_user_func_array"
    },
    {
      "file": "/var/www/app/Http/Controllers/EdgesController.php",
      "line": 193,
      "function": "__call",
      "class": "Illuminate\\Support\\Collection",
      "type": "->"
    },
    {
      "function": "path",
      "class": "App\\Http\\Controllers\\EdgesController",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Controller.php",
      "line": 54,
      "function": "call_user_func_array"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php",
      "line": 45,
      "function": "callAction",
      "class": "Illuminate\\Routing\\Controller",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Route.php",
      "line": 212,
      "function": "dispatch",
      "class": "Illuminate\\Routing\\ControllerDispatcher",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Route.php",
      "line": 169,
      "function": "runController",
      "class": "Illuminate\\Routing\\Route",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
      "line": 665,
      "function": "run",
      "class": "Illuminate\\Routing\\Route",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 30,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Router",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/barryvdh/laravel-cors/src/HandleCors.php",
      "line": 36,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Barryvdh\\Cors\\HandleCors",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php",
      "line": 41,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Illuminate\\Routing\\Middleware\\SubstituteBindings",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 104,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
      "line": 667,
      "function": "then",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
      "line": 642,
      "function": "runRouteWithinStack",
      "class": "Illuminate\\Routing\\Router",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
      "line": 608,
      "function": "runRoute",
      "class": "Illuminate\\Routing\\Router",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
      "line": 597,
      "function": "dispatchToRoute",
      "class": "Illuminate\\Routing\\Router",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",
      "line": 176,
      "function": "dispatch",
      "class": "Illuminate\\Routing\\Router",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 30,
      "function": "Illuminate\\Foundation\\Http\\{closure}",
      "class": "Illuminate\\Foundation\\Http\\Kernel",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/fideloper/proxy/src/TrustProxies.php",
      "line": 57,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Fideloper\\Proxy\\TrustProxies",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",
      "line": 31,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",
      "line": 31,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php",
      "line": 27,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php",
      "line": 62,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Illuminate\\Foundation\\Http\\Middleware\\CheckForMaintenanceMode",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/barryvdh/laravel-cors/src/HandlePreflight.php",
      "line": 29,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 151,
      "function": "handle",
      "class": "Barryvdh\\Cors\\HandlePreflight",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",
      "line": 53,
      "function": "Illuminate\\Pipeline\\{closure}",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
      "line": 104,
      "function": "Illuminate\\Routing\\{closure}",
      "class": "Illuminate\\Routing\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",
      "line": 151,
      "function": "then",
      "class": "Illuminate\\Pipeline\\Pipeline",
      "type": "->"
    },
    {
      "file": "/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",
      "line": 116,
      "function": "sendRequestThroughRouter",
      "class": "Illuminate\\Foundation\\Http\\Kernel",
      "type": "->"
    },
    {
      "file": "/var/www/public/index.php",
      "line": 55,
      "function": "handle",
      "class": "Illuminate\\Foundation\\Http\\Kernel",
      "type": "->"
    }
  ]
}

+1
Any solution !?

Where does that Call to a member function connection() on null happen? I don't see how this is related to PHP 7.1, I think it's rather that some other library was updated when you switched to 7.1?

I'll inform you with my error informations tomorrow.

The TaskError object that is thrown has a method getWorkerTrace() that you can use to get the stack trace of the exception thrown in the worker. Then you can see where the connection() method is being called on null.

I'll try.

I'm closing this due to the lack of activity.

@kelunik I have the same problem when trying to request the database in a parallel worker.

@ThibaudDauce See https://github.com/amphp/parallel/issues/70#issuecomment-497479728 and report that, please.


test: added tests for UpdateChannelParams

Description

Added tests for UpdateChannelParams in msg_server_test.go.
closes: #5479
Commit Message / Changelog Entry
test: added tests for `UpdateChannelParams`

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[X] Targeted PR against the correct branch (see CONTRIBUTING.md).
[X] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.

[X] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[X] Provide a commit message to be used for the changelog entry in the PR description for review.
[X] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (947b15e) 80.90% compared to head (deb3018) 80.95%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5494      +/-   ##
==========================================
+ Coverage   80.90%   80.95%   +0.05%
==========================================
  Files         197      197
  Lines       15235    15235
==========================================
+ Hits        12326    12334       +8
+ Misses       2437     2429       -8
  Partials      472      472

see 1 file with indirect coverage changes


Modified rendering functionality for load-more button

Fixes #1086
Description

Added allLoaded state to track when all contributors are loaded
Updated loadMore function to set allLoaded to true when reaching the end of the list
Conditionally render "Load More" button based on allLoaded state
Button now disappears after all contributors are loaded, improving UX

Video
https://github.com/user-attachments/assets/c6925d85-f5c3-4f70-82b8-5e0b3d186b1b

@mdazfar2 Please review and merge this PR


[Bug/Glitch] Items in hotbar don't dim along with interface opacity

Legacy4J Version
1.21-1.7.2
Mod Loader Version
Fabric Loader 0.16.0
Bug/Glitch Occurrence Context
I've been playing the mod using the Re-Console modpack on Modrinth.
Crash Report
No response
What happened wrong?
The items in the hotbar don't correctly dim along with the hotbar. I've attached a screenshot of the issue.

Below is a screenshot from the Xbox 360 Edition, showing what the items should look like.

disable hud_batching in the immediatelyfast config file

It’s not a bug so much as it is a result of how the optimization method works


feat: add new variant to command

Description (required)
This PR adds a new variant to one of the options returned to the hook astro:config:setup
For Astro version: 4.15. See astro PR #11729.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/integrations-reference.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@ematipico Looks like this will need updating in the section below, around lines 106-112 too?

Updated!

@ematipico Thank you, but it also needs a line at 113 explaining it!  :smile:  Is it just the same text as the explanations for the others, or is it different?

@sarah11918 done


Step positions are erratic

Also steps don't seem to correctly position themselves according to the docs.. and they work differently in Mozilla Firefox versus Google Chrome, unless there's a fix for it, I'm moving on I'm afraid

Maybe it would be good idea to specific a fallback if there's no space for the supported position.


Remove domain label from kubevirt_vmi_memory_unused_bytes

Signed-off-by: arthursens<EMAIL_ADDRESS>
What this PR does / why we need it:
Removes the domain label from the kubevirt_vmi_memory_unused_bytes metric.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
#3927 was created before #3845 got merged, so it was created with the domain label. There was plenty of time to fix the PR before getting #3927 merged, but due to my lack of attention it got merged with the extra label.
Release note:

`domain` label removed from metric `kubevirt_vmi_memory_unused_bytes`

/lgtm
/approve
/retest
@ArthurSens thanks!


🥳[Feature] Litecoin Card 2FA

This is when you are trying to login to the Litecoin Card.
When entering 2FA to access the Litecoin card on Litewallet, I submit a number and the keyboard reverts back to letters. I have to change it to numbers for every single digit I enter.
You could copy/paste but I'm not sure if all of our users are going to be able to do that.

thanks @Patrick-t-mcdermott

More info here: https://github.com/litecoin-foundation/litewallet-team/issues/31
cc: @Patrick-t-mcdermott  @Crypto-Keeper-miners

Will not do Ternio/Unbanked is out of business.


Qwen2 Model Series

Reminder

[X] I have read the README and searched the existing issues.

System Info
Windows11,10,linux
Reproduction
none
Expected behavior
can you add Qwen2 series of model?
Others
can you add Qwen2 series of model?

nevermind


Updating Plugins

I've made a major update to my plugin, which adds features and fixes bugs. Is there a way to roll out the update? If I submit a pull request to overwrite it in plugins.json, will it automatically update? Or is there a way to notify users of my plugin and give them an option to update it?
Thanks.

Also, my plugin's UrlDownload is listed as https://github.com/HorridModz/Flow.Launcher.Plugin.Add2Path/releases/download/v1.0.0/Flow.Launcher.Plugin.Add2Path.zip, but in my new release (2.0.0) the link has changed to https://github.com/HorridModz/Flow.Launcher.Plugin.Add2Path/releases/download/v2.0.0/Flow.Launcher.Plugin.Add2Path.zip.  So I assume this will break the CI?

Is there a way to roll out the update?

Just use GitHub release, preferable using workflow like this one

will it automatically update

It automatically updates using data from repo releases. It already did [ https://github.com/Flow-Launcher/Flow.Launcher.PluginsManifest/commit/bff84b3af7f186be71436a983b66f82d970f3063 ]

is there a way to notify users of my plugin

pm update
There is Discord channel which has notification about every plugin included in this manifest

Is there a way to roll out the update?

Just use GitHub release, preferable using workflow like this one

will it automatically update

It automatically updates using data from repo releases. It already did ( bff84b3 )

is there a way to notify users of my plugin

pm update
There is Discord channel which has notification about every plugin included in this manifest

It already updated? That's interesting, how would it know if the release link changed (or it just uses latest release)? But I see the commit you linked - thanks for letting me know.

I thought I already posted this, but I don't see it so I'll post it again - it doesn't seem to have updated on my end. I both reinstalled the plugin and ran pm update; it's still using the old version in my FlowLauncher.

@jjw24

So all plugins do get updated to newer versions automatically, it's an automated process that checks for new versions. You don't need to submit a separate pr after you release an update to your plugin as long as it's using GitHub Release as mentioned by NoPlagiarism.
The availability in the Plugin Store after the manifest is updated may vary because of the use of CDN and their caching policy, but will appear in the store eventually.

@HorridModz I see your plugin repo does not use  GitHub Action workflow to publish your release, please add it. You can follow this to add it.
Please ensure the workflow is added as it is an important requirement for all plugins in the store.

@HorridModz I see your plugin repo does not use GitHub Action workflow to publish your release, please add it. You can follow this as an example.
Please ensure the workflow is added as it is an important requirement for all plugins in the store.

Sorry for being a stubborn pain in the butt, but I've never used Github Actions. Do I have to - this is just a wild case - add that file to my project and edit it, and then it will run and everything will somehow be unicorns and rainbows next time I push to Github? Is there a tutorial or some guide I can follow? Thanks, and sorry for asking you to spoonfeed me.

The availability in the Plugin Store after the manifest is updated may vary because of the use of CDN and their caching policy, but will appear in the store eventually.

Oh wow, I tried pm update again and it worked this time! That's great! It kind of sucks that the update isn't automatically rolled out, though, as major bugfixes are included that fix corruption of the PATH environmental variable (a serious change I want people to automatically have) - would it have been considered the plugin's responsible to detect and require updates when it was first written and published?

@HorridModz I see your plugin repo does not use GitHub Action workflow to publish your release, please add it. You can follow this as an example.
Please ensure the workflow is added as it is an important requirement for all plugins in the store.

Sorry for being a stubborn pain in the butt, but I've never used Github Actions. Do I have to - this is just a wild case - add that file to my project and edit it, and then it will run and everything will somehow be unicorns and rainbows next time I push to Github? Is there a tutorial or some guide I can follow? Thanks, and sorry for asking you to spoonfeed me.

All good.
GitHub Actions is a CI/CD (Continuous Integration and Continuous Deployment) platform that allows you to automate your project development workflows. It enables you to build, test, and release your code (plugin in your case) directly from GitHub by creating custom workflows defined in YAML files. These workflows can be triggered by various events, such as push events, pull requests, or schedule-based triggers, so when you push your code changes it will build it automatically, and when you push your code into your main branch, it will automatically create a new GitHub Release. This means you do not need to build locally on your computer, zip up the files and manually create a release.
Give that file a go, do it on a separate branch, and when I have some free time I can help you fix any issues you may have with it. You can try this https://docs.github.com/en/actions/using-workflows/about-workflows#create-an-example-workflow

@HorridModz I see your plugin repo does not use GitHub Action workflow to publish your release, please add it. You can follow this as an example.
Please ensure the workflow is added as it is an important requirement for all plugins in the store.

Sorry for being a stubborn pain in the butt, but I've never used Github Actions. Do I have to - this is just a wild case - add that file to my project and edit it, and then it will run and everything will somehow be unicorns and rainbows next time I push to Github? Is there a tutorial or some guide I can follow? Thanks, and sorry for asking you to spoonfeed me.

All good.
GitHub Actions is a CI/CD (Continuous Integration and Continuous Deployment) platform that allows you to automate your project development workflows. It enables you to build, test, and release your code (plugin in your case) directly from GitHub by creating custom workflows defined in YAML files. These workflows can be triggered by various events, such as push events, pull requests, or schedule-based triggers, so when you push your code changes it will build it automatically, and when you push your code into your main branch, it will automatically create a new GitHub Release. This means you do not need to build locally on your computer, zip up the files and manually create a release.
Give that file a go, do it on a separate branch, and when I have some free time I can help you fix any issues you may have with it. You can try this docs.github.com/en/actions/using-workflows/about-workflows#create-an-example-workflow

Thank you! Sounds good.

@HorridModz I see your plugin repo does not use GitHub Action workflow to publish your release, please add it. You can follow this as an example.
Please ensure the workflow is added as it is an important requirement for all plugins in the store.

Sorry for being a stubborn pain in the butt, but I've never used Github Actions. Do I have to - this is just a wild case - add that file to my project and edit it, and then it will run and everything will somehow be unicorns and rainbows next time I push to Github? Is there a tutorial or some guide I can follow? Thanks, and sorry for asking you to spoonfeed me.

All good.
GitHub Actions is a CI/CD (Continuous Integration and Continuous Deployment) platform that allows you to automate your project development workflows. It enables you to build, test, and release your code (plugin in your case) directly from GitHub by creating custom workflows defined in YAML files. These workflows can be triggered by various events, such as push events, pull requests, or schedule-based triggers, so when you push your code changes it will build it automatically, and when you push your code into your main branch, it will automatically create a new GitHub Release. This means you do not need to build locally on your computer, zip up the files and manually create a release.
Give that file a go, do it on a separate branch, and when I have some free time I can help you fix any issues you may have with it. You can try this docs.github.com/en/actions/using-workflows/about-workflows#create-an-example-workflow

Just one more question, if you don't mind. Should I create the action files locally, or on the remote repository? Does it matter?

@jjw24 If you're able to, it would be great if you could check out the pull request I just created in my plugin's repo. Absolutely no rush, and I really appreciate all the help.
I'll close this issue since it has nothing to do with this repository and we should be good to go,


Is there any way to implement angular 4?

Is there any way to implement angular 4?

None yet, feel free to dig in!

Is there any update for Angular 6?

There are no plans for this right now, but maybe soon


Enable vectorcall on nogil build

This works locally (numpy.random test suite passes, no new test failures in the cython tests) and should be substantially faster. It was disabled for the python 3.9 nogil fork but @colesbury tells me the version in Python 3.13 supports vectorcall.

Yeah, I think this makes sense. Some of the old nogil-3.9 configuration (like disabling vectorcall) were not really related to the GIL, but were due to other interpreter changes that are not present in 3.13.
There are two other configurations currently disabled in CYTHON_COMPILING_IN_CPYTHON_NOGIL that I think can be enabled. I don't know if it makes sense to change them together in one PR or in separate PRs, but I'll list them here:

CYTHON_USE_PYLONG_INTERNALS: should be okay to enable -- the objects are immutable so no thread-safety issues.
CYTHON_FAST_THREAD_STATE: should be okay to enable -- thread local state is thread-safe

So I think that leaves the following that should be disabled in free-threaded 3.13 (but not default 3.13):

CYTHON_USE_PYLIST_INTERNALS: we should continue to keep this disabled so that we use the Python APIs that perform the appropriate locking when modifying list objects.

There are also the following which are disabled in 3.13 due to version checks and also disabled explicitly with CYTHON_COMPILING_IN_CPYTHON_NOGIL:

CYTHON_USE_DICT_VERSIONS: this is deprecated (since 3.12), but if it were ever "un-deprecated" we'd want to continue to disable this in free-threaded builds.
CYTHON_USE_UNICODE_WRITER: should be okay to enable if it works in 3.13 in the future
CYTHON_FAST_GIL: a bit weird, but I think it should be okay to enable it if works in 3.13 in the future

There are two other configurations currently disabled in CYTHON_COMPILING_IN_CPYTHON_NOGIL that I think can be enabled.
[...]

All those suggestions make sense I think.
I'm inclined to merge vectorcall now because it's probably the most significant change and largely just "the recommended way of calling" now, rather than an optimization. The rest can come later if wanted and if they appear to work.

CYTHON_FAST_GIL: a bit weird, but I think it should be okay to enable it if works in 3.13 in the future

I think we looked at it fairly recently (on regular with-GIL Python) and decided that it had turned into something that was neutral at best and possibly a pessimization, so it's unlikely to get re-enabled.


CON-68: Replace various occurrences of "consent management"

Related Issue
https://govstack-global.atlassian.net/browse/CON-68

Ping @aaviksoo

Great work :tada:
After all tweaks in terminology, eliminating "management" seems to be a real win. In every case, it has been replaced with a more meaningful and precise term.


fix bug with HTTPS RPC endpoint for node URL not being recognized

RPC node endpoints using HTTPS (for example https://myrpc.com) are being prepended with the string http://, resulting in RPC requests getting sent to, for example, http://https//alphanet.tezrpc.me.
This PR resolves the bug by simply properly checking for the existence of the string https:// in the node endpoint.

Nice catch @leopoldjoy , thanks man!


fix: handling of token page throttling

High Level Overview of Change
The token page is prone to being throttled because it tries to load in
order books for the "top 10 tokens". This change moves logic to useQuery
and out of redux. It then makes sure the token's information is loaded
in before trying to load in dex pairs.
Fixes https://github.com/ripple/explorer/issues/790
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactor (non-breaking change that only restructures code)
[x] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Translation Updates
[ ] Release

TypeScript/Hooks Update

[ ] Updated files to React Hooks
[x] Updated files to TypeScript

Before / After
Before

After

Seems like #984 might be related

Seems like #984 might be related

I think we can merge this one in first to fix token page. Then we can rebase the one that you created


Kicked whilst connecting to LOBBY: [LP] A database error occurred whilst loading permissions data. Please try again later. If you are a server admin, please check the console for any errors.

As the title says I'm too tired to deal with it, uploaded the whole network take what do you need from it please just tell me how to fix it or even better, just modify it and I will give you the upload link, I spent 5 hours trying to fix this error but no luck, searched all the available threads and everything, please help me.
Server Link: https://drive.google.com/file/d/1ZxJP2KhmcI8DaIxvo9kl5PENC1nvPD1H/view?usp=sharing
Feel free to modify the settings and tell me what the fck is wrong because I can't fucing figure it out. Thanks in advance. [Latest ver of LP, imported LP table, configured MySQL also check INSTALL.yaml file to see a complete list of what I have done inside the server files] Please I beg of you help me.

The networking side is handled already, the main problem is I can't connect to the server. Please any help is appreciated

Check the console for errors. Including during startup.

Thanks, I know what kind of place is it, just gave the whole package for people interested in details, less talking more working you know? Anyway, no errors during runtime. No error during setup and no error during lp import ranks.yml command. If it was a simple obvious problem I wouldn't be here right now. Thanks for your opinion, double-checked if I can see any runtime errors, and still nothing, the console is clean.

Maybe description was a little too rough, I am stressed enough because of this situation, sorry if I offended someone, just 5 hours of continuous debugging it's not the best thing I could have done today.

I'd be expecting a startup error. Especially related to MySQL.

Figures, MySQL initializes just fine, no problems there either.

Can we still have your log?

Wich one, bungee or backend server lobby?
[This was the main reason I included the server files]

here's bungee
latest.log

and here's backend server [LOBBY]
latest.log

Tell me if you need the plugins list or certain versions of things, pretty much using the latest with everything.

You are aware that you can send ONE single comment right?
It is rather annoying for people to receive 3 separate notifications (through e-mail) which could easly be summed up into one major comment itself.
Also, not everyone wants to download files. It's recommended to upload them to https://hasteb.in instead.

Thanks, and sorry, just a little overwhelmed by this issue, from now on I will send compressed messages in single comments and upload it to pastebin or hastebin. Thanks for the advice.

 (P.S.: Why did you send the bungee log if there's no LP installed?)
Anyways the guide to fix MySQL errors is here: https://github.com/lucko/LuckPerms/wiki/Storage-system-errors

Yeah, that fixed it, I don't know how I overlooked whole lines like that. So very sorry for the unnecessary trouble, and thank you so much @BrainStone . The Bungee server had LP for Bungee installed but had disabled it in the latest run, the same issue. Again, sorry for the trouble and thank you!

как вы это решили?


Mac

Is there a way to get this working for Mac deployments?

AFAIK, le plugin works on OSX. Did you encounter issues on Mac?
I can't test it from where I am.


Event list block [calendar site attribute] selection error

https://user-images.githubusercontent.com/43093665/139372464-ea05f6f5-212d-4b62-9aa4-c75bcaf320da.mov

When  selected  Calendar Site Attribute of the Event List Block, got  Field 'caID' doesn't have a default value and  json_decode() expects parameter 1 to be string, array given errors .
Please see the above screen recording.

Unable to reproduce this on the latest develop.


Upgrade: Fix test flakiness around upgrade reminders

Should fix #852.
The fix is to use an environment variable to always show the upgrade message, if present.
While looking at the post-command hook code, I discovered some simple cleanups that are isolated to different commits:

Removed unreachable code.
Changed a message to refer to gvfs status instead of git status.

/azp run GitHub VFSForGit Mac Functional Tests

/azp run GitHub VFSForGit Mac Functional Tests

@derrickstolee with this change the functional tests are no longer testing/validating the upgrade reminder logic in the hooks because GVFS_UPGRADE_DETERMINISTIC is only used in the tests.
Rather than adding the check for GVFS_UPGRADE_DETERMINISTIC would we be better off disabling the test(s) until we have an approach for showing the upgrade message that's deterministic?

would we be better off disabling the test(s) until we have an approach for showing the upgrade message that's deterministic?

I think this change allows us to test most of the product code path, and provides value. I guess we could get even closer by tweaking the following line:
if ((IsUpgradeMessageDeterministic() || randomValue <= reminderFrequency)
to something like:
int reminderFrequency = IsUpgradeMessageDeterministic() ? 100 : 10;
...
`if ((randomValue <= reminderFrequency)`
...

So this environment variable would only change the frequency (to have it run every time).

I guess we could get even closer by tweaking the following line:
int reminderFrequency = IsUpgradeMessageDeterministic() ? 100 : 10;

@jamill thanks for posting that suggestion, it made me realize I misread the change to the if statement.  I incorrectly thought that IsUpgradeMessageDeterministic was skipping the rest of the checks (rather than just skipping the random number portion).
Thanks!
/cc: @derrickstolee


Warning about set-output deprecated

Bug description
I receive the following warning for this action
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

From the blog:
Action authors who are using the toolkit should update the @actions/core package to v1.10.0 or greater to get the updated saveState and setOutput functions.

Environment

pkg-size-action version: latest
Operating System: not relevant
Node version: not relevant

+1


Add set/get features

This PR add the functionalities for getting/setting features from/to the camera through rpc/nwc requests.
TO BE TESTED

The set/get features have been tested successfully with frameGrabberGui2, merging


Features/output

TODO : Replace declared stubs with real classes stubs once they are implemented.

Codecov Report

Merging #6 into staging will decrease coverage by 2.5%.
The diff coverage is 94.11%.

@@            Coverage Diff            @@
##           staging      #6     +/-   ##
=========================================
- Coverage      100%   97.5%   -2.5%
=========================================
  Files            9      11      +2
  Lines           65     120     +55
=========================================
+ Hits            65     117     +52
- Misses           0       3      +3

Impacted Files
Coverage Δ

src/output/generator.js
94.11% <94.11%> (ø)

src/index.js
100% <0%> (ø)

Continue to review full report at Codecov.

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


Occasional double or triple writes for same data

Ran into a similar issue as mentioned in 3315, 6946, and 6853.
Basically, when using curl to post data from a bunch of text files, occasionally some points will be written into the database 2 or 3 times, with the points being exactly the same (measurement, tags, fields, everything). I am in parallel pushing the same data into a different database using UDP, and here I don't have the duplication issue. When I run service influxd restart, it appears to have gotten rid of the duplicates once the system comes back up.
This happens with influxdb version 0.13.0 on Ubuntu 16.04
I'll happily provide more information if needed, but just wanted to call attention to the issue again!

Can you test with a current nightly release?

#7027 should fix this.  Sounds very similar to #6946

Duplicate of #6946

Sorry I was unable to test with a nightly release quickly, and #7027 looks good, thanks!


Update README.md

Convert "sudo rm -rf /esp/efi/refind/" to codeblock
Add commands to remove the SteamDeck_rEFInd  directories and desktop shortcutt

sudo shouldn't really be needed to remove files from $HOME directory, but it's not really a problem either (in my opinion). Merge approved.


changed type text to textarea

modified the field type text to textarea for issue 5265

@Ravi-kumar9347 please read and follow Change log entry and Create a pull request from your fork Item 2. We do not review pull requests until all GitHub checks pass.

@tiberiuichim and @sneridagh , can you check my PR once ?

@davisagli, i am new to the open source, so can you please help me the exact path of above image. because i only see this image. where can i find that comment sectoin.

@stevepiercy  sorry for my things i did, can i reopen this or should i mention why i closed this pr

@Ravi-kumar9347 do whatever you think is best. I already gave you direction in my comment in the other PR.

@stevepiercy then would you consider the latest pr


Mention & link to new app studio book EC content

In draft until https://github.com/redhat-appstudio/book/pull/18 is merged.

https://github.com/redhat-appstudio/book/pull/18 is merged.


Spoilering used words by cheaters is possible

A new day starts at UTC time, which is the same worldwide. However, if someone moves from Poland to the UK and manually adjusts the date instead of changing the timezone in their system, they can create a shared link with a password that will display it to people in regular UTC zones.
Expected behaviour
Such spoilers should be blocked

After:


[FEATURE] support table/column lineage

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
ref: https://github.com/maropu/spark-sql-flow-plugin
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

https://github.com/apache/incubator-kyuubi/pull/3185#issue-1329564580


Remove repos that should not be notebook tested

Internal discussions resulted that just cudf, cuml, cugraph, & cuspatial notebooks should be tested.
We might exclude more notebooks and will iterate on this PR.

Thanks Ray! 🙏
Is this worth noting in the README or description of these images as well?

Even though CI is not passing, this PR reduces the number of notebooks being tested, so it will help unblock CI tests in #559

/merge


Admin left sidebar is still visible

I have installed the plugin in a fresh payload install, and I should have missed something but the left sidebar is still visible so I can't get enough space for the preview.
I looked into the  scss and there is nothing about the nav, is it still in development ?
Thanks !

Hey, you're totally right. The toolbar doesn't shrink automatically. The screenshot doesn't reflect the example of this repo. It was made from another project where we applied some custom styling / logic to expand / collapse the toolbar.
It's maybe a bit misleading. We should change the screenshot or write a small hint.
If you're interested how we hide the toolbar, feel free to ask.


Profile detection in camera preview on Android and added launcher icon

App name should have a space

Why is the screen only dimmed in the centre?

The name is too long if it has a space so we end up with something like "Extrusion Find..."

Without the space it displays as:
ExtrusionFin
der

We could just call it "Extrusion"

Where? On the home screen on in the app tray?
The black box is only in the centre of the screen because this is the area in which profile detection occurs.

Should the black box also be circular?

I don't know... It's square because the profile detector produces a square image.

Wrt. a circular viewport, I decided against it because the matching does actually work over the whole square subsection and IMHO a circle would look ugly if touching the edges.
Wrt. the border, it's possible to make them any colour we want: just initialize the whole surface to that colour and it will forever stay that way. I see no pressing need, though.


added note about updated security baseline

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8389

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @ei, for your information
Thank you

I have already filled a complaint with the ICCC and the F.B.I. For violation of privacy and infringement
Ernesto

On Dec 14, 2020, at 5:21 PM, Daniel Simpson<EMAIL_ADDRESS>wrote:

Merged #8513 into public.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

So you know I do have an appointment with an attorney tomorrow to prosecute
Ernesto

On Dec 14, 2020, at 5:21 PM, Daniel Simpson<EMAIL_ADDRESS>wrote:

Merged #8513 into public.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Some domains are listed as live even when DNS times out

@climber-girl noticed that the output of the following command reports nara-at-home.gov as "live" even though there are no MX records for that domain:
$ trustymail --json --debug --timeout=5 --smtp-timeout=5 --dns=<IP_ADDRESS> nara-at-work.gov

This pull request fixes this issue.  Domains for which no MX records exist will no longer be listed as "live".
This pull request is related to NCATS JIRA ticket CYHY-706.

There are a couple of other places where we catch the same exceptions (dns.resolver.NoAnswer and dns.timeout.Exception), but I don't think we want to label the domain as "not live" in those cases.  I would be interested to hear others' thoughts, though.
The parts of the code I am talking about are here and here.

I guess the real question is, what does "live" vs "not live" mean for trustymail?  Does it mean we have or don't have an MX record, respectively?
It's worth looking at the relevant code in dhs-ncats/trustymail_reporter to see how live vs not live impacts the results that are reported.

I can always revert the PR.
What does "exists" mean here?  That the domain is registered?  That's not something we check for explicitly in trustymail, although in NCATS' scanning it is always the case because we use current-federal as our list of parent domains.

It's true we're not checking top-level domain whois', but I think that (and welcome further discussion on) a domain not NXDOMAIN'ing or SERVFAILing is a reasonable proxy for existence. It's functionally "live" if the domain resolves in public DNS, and therefore can benefit from DMARC action.


Add clarifications to README setup instructions

Is your feature request related to a problem? Please describe.
Some of the instructions are unclear and incomplete, making them hard to follow.
Describe the solution you'd like
Add instructions (or a link to instructions) for installing and running redis server and for setting up postgres, and rephrase the line about configuring the database.
Are you working on this? (Yes/No)
Yes

Hey @nrs1729, this can be a GCI task, I'll add one so you can claim it then

Thanks!

These are the instructions if the developer chooses not to use Docker correct ?

These are the instructions if the developer chooses not to use Docker correct ?

Yeah without Docker

I've already done two beginner tasks so someone else can claim it if they want.

@nrs1729 That's very kind of you. You can send a PR, in-case no one claims this within a few days we'll merge yours because this is a very important part of the ReadMe and we need it to be done as soon as possible.

Okay cool, I made a PR last week for a task adding WSL instructions (https://github.com/CircuitVerse/CircuitVerse/pull/720) so is it okay if I use that as a base instead of the currently merged README (create a branch of the branch I made for the task)? I know some other people edited the README for docker instructions etc.

No one has claimed it so I had a go and made a PR https://github.com/CircuitVerse/CircuitVerse/pull/749 (based of the currently merged readme - the instructions I/other people added for WSL and docker are in different PRs), is that alright?


Fix undefined css property / Sitemap Post Url

Sorry it took me so long to take care of this, but I'll incorporate your changes in the next release of Telescope :)


test framework starts taskCount + 1 mesos tasks

if you run the example framework and executor and pass the -task-count=2 value, mesos ends up running 3 tasks instead of two.
I see this by looking at the logs and I see:
...Prepared task: go-task-1...
...Prepared task: go-task-2...
...Prepared task: go-task-3...

The error seems on this file
https://github.com/mesos/mesos-go/blob/master/examples/test_framework.go#L109
for sched.tasksLaunched <= sched.totalTasks &&

if I change it to
for sched.tasksLaunched < sched.totalTasks &&

then it only schedules the number of tasks  I passed on the command line.
If you agree this is an issue, I can send a quick PR to fix it.
Thanks

Sounds like a bug to me. PR welcome

tnx, PR sent


Local google fonts loading in http not https

Hey,
I'm using the Kirki plugin as part of the NK Godlike theme. Using the customizer i've added a couple font's however they try to load over http instead of https for some reason. The font is available via the same path over https. (They load locally)
I've got a URL rewrite in ISS for http to https and the same on cloudflare, but no matter what i do i cannot get them to load over https. My site does not load insecure content which results in no font showing up.
Version: 3.0.39
Site: https://astral-imperium.com
To see the issue, you can load the website and see the mixed content messages in the google chrome console.
Is this a bug or potential config issue because i'm using local font's? From what i can see if they loaded from google then it would use https no problem, but i'd like to keep them local if possible.

@Shadowsong87 I think there may be something improperly set-up on your site...
Kirki uses native WordPress functionality to store the Google Fonts (see this line)
We just use wp_handle_sideload. That function in its turn calls _wp_handle_upload` if you checks its source. That calls wp_upload_dir to get the URL of your uploads folder.
I can think of 3 things that may have caused this:

wrong WP_CONTENT_URL defined in your wp-config.php
Wrong URLs set-up in Dashboard > Settings > General
perhaps multisite with a domain-mapping plugin which has the wrong domain protocol set-up for that site?

Thanks for the reply, we had recently moved over to multisite which is when we noticed the issue. However for some unknown reason the issue now appears to have gone and no more errors. Wondering if it was cache related or something strange that needed time to update.
Either way all working so this one can be closed off!

@aristath Same issue has above. The funny thing is that Lato loads over http and Simonetta over https.

I have this errors too. I never use http but:
Mixed Content: The page at 'https://wp.vlthemes.com/arquito/wp-admin/post.php?post=75&action=edit' was loaded over HTTPS, but requested an insecure stylesheet 'http://wp.vlthemes.com/arquito/?action=kirki-styles&editor=1&ver=3.0.39'. This request has been blocked; the content must be served over HTTPS.

Any news on this?

The latest update fixed this https://wordpress.org/plugins/kirki/#developers


Test fmi2 wrapper functions

Call all functions (including all member functions) in FMIWrapper.jl and fix remaining bugs.

Current code overage of wrapper functions is around 58% of relevant lines:
https://coveralls.io/builds/27500652/source?filename=src%2FFMIWrapper.jl


CHEBI:42156

Dear ChEBI curators,
Could you please add the structure in attachment (17-epiestriol.pdf) to CHEBI:42156 ?
To complete the entry, I suggest:
names: 17-epiestriol;  16α,17α-estriol; 16α-hydroxy-17α-estradiol (Uniprot name)
definition: A 3-hydroxy steroid that is the 17α stereoisomer of estriol.
PMID:23288867
Many thanks for your help
Nevila-Hyka-Nouspikel

Now done.
Kind regards,
Gareth

Thank you very much Gareth! It looks perfect.
All the best,
Nevila


CLAP feature extraction code init

Can you move scripts/CLAP_features/extract_features.py to ego4d/egoexo/scripts? i.e. git mv scripts/CLAP_features/extract_features.py scripts/extract_clap_features.py
Looks good, could be improved to distribute the extraction, but since you've already extracted the features then this doesn't matter.
Please delete the code I've flagged as unused (this is just noise when you read it). I've also comments as suggestions for future code you write (don't need to apply my suggestions other than delete unused code).


Why encoder-decoder architecture?

Hi @LTH14! Congrats on your nice work being accepted by CVPR.
Just as the title, I'm confused why you choose to use an encoder-decoder architecture like MAE? Have you ever tried using a encoder only arch like BEiT?

We haven't tried an encoder-only structure like BEiT. The reason why we chose the MAE-style enc-dec structure is simply that they were the sota method at that time. Also, an encoder-decoder structure enables us to decouple the representation learning from the generation.


Sync eng/common directory with azure-sdk-tools repository for Tools PR 1365

Sync eng/common directory with azure-sdk-tools repository for Tools PR 1365

@weshaggard - please run the CI here which uses cosmos emulator, in case there is any CI.

https://dev.azure.com/azure-sdk/public/_build/results?buildId=717285&view=results

Closing out this PR on behalf of automation.


Have check run the system tests

fixes: https://github.com/creek-service/creek-system-test-gradle-plugin/issues/19
Have check task depend on systemTest. Plus added a test covering :cleanSystemTest.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage increased (+0.07%) to 97.917% when pulling 42b60adedd5366aca60d521c43dda4466a0f962c on check into c56cf52e769c42b2c8b684ecafa416a7b1c346b2 on main.


[BDGR-180][WIP] Write new vMix client and mock server

Still to do:

[ ] Port tests to use the new MockVMixServer

/yarn unlock


[FEATURE]: allow to have verhicle positions in HA at a higher frequency than 5 mins

At present the vehicle locations are collected every minute in a geojson file
The geojson is imported in HA using the core/native geojson integration
This integration has a update frequency of 5 minutes which is a bit slow.
Veh/. positions should update in HA at the same rate as with which they are extracted from the real-time source (once per minute at least)

Hi,
I'm trying to implement a "smart sensor refresh".
Something like: refresh data if GPS is moving ( > 50 meters ) , or current data are outdated ( > 20/30 minutes for testing)".
I have created a "zone" in HA to simulate my position/movements.
Indeed i receive new coordinated every few minutes...
I'm searching for a solution/workaround.
Fabien

This is not related at all ... this topic deals with buses/trains/etc. that, if realtime is setup,  donot update fater than 5 mins.

Using my own listner when tracker is updated, i receive the info at 2024-05-21 13:00:19.529 ,
Using the _handle_coordinator_update :  2024-05-21 13:01:05.292

[
o old => update
2024-05-21 13:00:19.529 INFO (MainThread) [custom_components.gtfs2.sensor] GTFSLocalStopSensorList._update_attrs(caller=event/listner): Arround Phone local_stoplist, GPS moved 14 => update
2024-05-21 13:00:19.530 INFO (MainThread) [custom_components.gtfs2.sensor] GTFSLocalStopSensorList._update_attrs(caller=event/listner): Arround Phone local_stoplist, from (50 4) => (50 4)
2024-05-21 13:01:05.292 INFO (MainThread) [custom_components.gtfs2.sensor] GTFSLocalStopSensorList._update_attrs(caller=_handle_coordinator_update): Arround Phone local_stoplist, GPS moved 14 => update
2024-05-21 13:01:05.292 INFO (MainThread) [custom_components.gtfs2.sensor] GTFSLocalStopSensorList._update_attrs(caller=_handle_coordinator_update): Arround Phone local_stoplist, from (50 4) => (50 4)
^C](url)

This post is for bus/tram/etc. positions in HA only not device-trackers

About 2y ago I tested 'update_entity' or reload_integration and this did not work for geojson. I now tested the manual 'reload' and this does apply the changes to the position, as such no need to build this feature


rails 6 (sprockets 4) asset changes

Rails changes it's default logic for determining top-level targets. It will now use only a file at ./app/assets/config/manifest.js for specifying top-level targets.

Since we're here, would you help us fix the build, too? It needs a fix like https://github.com/dblock/slack-strava/commit/7de7cba6ba0d4e0262f74606f6e907213120bdde

I did those kind of grammar fixes.

Merged via https://github.com/ruby-grape/grape-swagger-rails/pull/98


PassHUD does not start

Hi,
I downloaded the App using the releases page, unzipped it and tried to start it. Unfortunately, it does not start but says

You can't open the application "PassHUD.app" because it may be damaged or incomplete.

Thanks for opening the issue! I just tried downloading it fresh myself and don't get the same error unfortunately. This is also the first macOS app I've tried to distribute so good odds I've messed it up somehow. What OS version are you on?
Perhaps it was incompletely downloaded? Do you get the same m5sum for the downloaded zip file as I do?
% md5 PassHUD.app.zip
MD5 (PassHUD.app.zip) = de1975eae4580ef3a5ba278504b180db

Oh one more thought, do you allow application from outside the app store in your security system preferences? The application is unsigned as well, so at least on my High Sierra machine I need to explicitly allow PassHUD to run in security system preferences too.

Sorry for the delay on this. I've just cut an 0.2.0 release and packaged it as a DMG built from an archive. Please let me know if this works better for you!

The issue is solved, thank you :)


Subctl/Operator support for vxlan cable driver

What would you like to be added:
subctl/operator needs to support a new cable driver.
Why is this needed:
As a part of  https://github.com/submariner-io/submariner/issues/674 new vxlan cable-driver will be supported. It should be possible to create a deployment with this driver.
Subctl : should accept a new option vxlan for cable driver.
Operatror : Should ensure that this is passed to g/w pod.

bump


Support named parameters in calls to endpoints

As the title says.

Ahhh yes, I was looking into this and thought of reaising a ticket. Thanks.


Azure analysis example notebook unknown pipeline

From the Azure Analysis Example.ipynb last code block

from orion.analysis import analyze
pipeline_path = '../orion/pipelines/azure.json'
anomalies = analyze(pipeline_path, data, hyperparams=hyperparameters)
anomalies.head(5)

I get an unknown pipeline error:

Should the pipeline path instead be:

pipeline_path = '../orion/pipelines/verified/azure/azure.json'

May be solved by #176

Thanks @skyeeiskowitz, yes this error is resolved in PR #177.
Side note: to use azure you will need to pass a subscription_key and an endpoint parameters in either the hyperparameter settings or directly edit the pipeline, otherwise the pipeline will fail.
If you have additional questions, please reopen the issue!


[BUG] Blob(Async)Client download methods don't detect when no content is returned/written

Describe the bug
The following code in stress tests  syncClient.downloadContent()  can results in the following HTTP requests:

The first one does not contain x-ms-range (requestRange) and was able to download 26214400 bytes out of 52428800.
So the SDK makes another try for bytes=26214400-52428799.
This time fault-injector mistakenly returns 200 with 0 content length.
The SDK assumes that content was fully downloaded and returns it to the user without any error.
As a result, user gets corrupted data.
While the root cause is problematic http-fault-injector behavior, it'd still be great to detect when:

we requested a range
service returned less than we requested
we know there is more because we know the length of the content

SDK should should keep trying get the content until we get the expected length (within retry policy limits).
Exception or Stack Trace
No exception is thrown, stress tests fail with content mismatch errors.
To Reproduce
https://github.com/Azure/azure-sdk-for-java/blob/abadbdfa9a652a119bad4cbb409a939b435d1f72/sdk/storage/azure-storage-blob-stress/src/main/java/com/azure/storage/blob/stress/DownloadContent.java#L33
Expected behavior
SDK should do best effort to detect bogus responses and fail fast.

@lmolkova are we sure this is a bug?  What if the SDK requests a range that exceeds the size of the blob in the service?  Then we would expect to receive a 200 response from the service and less bytes than the SDK was expecting.

@seanmcc-msft
The bug here is the SDK behavior on the second request: we knew the content length from the first request. We've read 0 bytes and assumes a success.
This is probably not a real-life issue since it only happens when service/proxy behaves incorrectly.
But still I'd be an improvement to fail when incorrect behavior is detected.

Let's revisit in the future, it is very unlikely this scenario could occur in the service.


Update asm to 9.0

with JDK 16 support (sealed classes)
according to https://asm.ow2.io/versions.html

Would you mind creating a JIRA ticket to control what was upgraded? Thanks in advance!

Coverage remained the same at 49.779% when pulling 2409f7c2ec182c8e74860e9c670b614f737f87c7 on sepe81:update-to-asm-9 into f1dccc4610b9455a0e18c8f5d24bd9df945fbb0d on apache:master.

LGTM :100:


SSLError

I followed the instructions as per the readme, but I've been getting the following error :-
Reading credentials ...
 Authenticating with NITT SonicWall ...
Traceback (most recent call last):
  File "SonicWall_Login.py", line 103, in <module>
    if login(session):
  File "SonicWall_Login.py", line 63, in login
    t = session.get(base_url + 'auth1.html')
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/sessions.py", line 521, in get
    return self.request('GET', url, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/adapters.py", line 519, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: EOF occurred in violation of protocol (_ssl.c:590)

Seems like many OS X users have faced the same issue ( requests/issues/3006 ).
Can you try installing the ndg-httpsclient python package.
i.e. pip install ndg-httpsclient


Flutter UI Issue Urgent issue on Production

Hello Team
Out of a sudden, this package has started giving me UI issues on WEB, could you please let me know what needs to be done?
Tried on both 3.13.5 and 3.13.9 but no luck.
OLD UI

New UI
Without any update on anything

Same issue

I have same issue on flutter version 3.16.0 too. seem like some of property not apply when upgrade. I tried to downgrade to 3.13.9. It's work fine. maybe breaking change version cause the issue. (I testing on android)

I too have similar issue on Android and iOS. After the update to Flutter 3.16.0, the UI dimensions became a bit off (parts that use screen_util)

Got the solution please use version flutter_screenutil 5.7.0 if you are using this in flutter web until they fix the issue in the latest flutter_screenutil.
Use it like
flutter_screenutil 5.7.0
Do not use it like
flutter_screenutil ^5.7.0

Hi! Downgrading this lib doesn't solve this issue on mobile at all. All measurements are off.

Also returning flutter_screenutil to 5.7.0 returns the error #477 (Keyboard error)

I have the same issue on Android.
Latest flutter 3.19.3 + latest package flutter_screenutil: 5.9.0 have the issue.
It is weird, as problem happens only when run the app in release mode.


Question: How to trigger revert

Thank you for this great plugin. I'm aware that by providing a {server: { revert:(...) => { object to setOptions will allow you to define custom operations processing uploaded files. But lets say I want to add some extra buttons to the uploader for several tasks, besides obviously creating my own onClick handlers, how can I, given a upload id already, inform filepond to revert an upload?
I know there's a cancel button built in but my needs are more specific.
I'm using filepond with Vue as a single page component.

The revert handler is triggered by the removeFile call, so maybe you can use that?

Is there anyway to call removeFile from vue-filepond? I'm using filepond with vuejs

The revert handler is triggered by the removeFile call, so maybe you can use that?

i dont think this is true, did you try?

@sbusch You're right, it doesn't call the revert, see test case: https://codesandbox.io/s/vanilla-filepond-revert-remove-o2yqo?file=/src/index.js
Will see if I can pick this up later this week.

@sbusch should be fixed in 4.13.5, please confirm.
https://github.com/pqina/filepond/releases/tag/4.13.5

@rikschennink first thank you for your effort! I now had the time to test it the new release. Unfortunatley it doesn't work for me.
When I call filepond.removeFile(), the first uploaded file is removed from view but no DELETE request (as defined by server.revert) is submitted.
The reason is - at least - that the file's origin is 1 (== FileOrigin.INPUT), so your change at https://github.com/pqina/filepond/blob/044a7ca00393b6f03cf732ae61a2ce6a876ad8a1/src/js/app/actions.js#L906 does not apply. I wrote "at least" because I'm not sure if item.revert(createRevertFunction(... would issue such a DELETE operation at all...

@sbusch just published 4.13.6 which should fix this issue

Works for me, removeFile() and removeFiles() trigger the DELETE request :-)
Thank you very much!

@sbusch this functionality has been reset in 4.13.7 as it caused backwards incompatibility issues, you can still trigger revert by adding { revert: true } as a parameter to removeFile() or removeFiles()

@rikschennink Thanks for the heads-up, didn't expect that kind of service! I'll update & test it

@rikschennink better late than never:
removeFile() works as expected:

removeFile({revert: false}) removes first element and doesn't revert (= no DELETE XHR)
removeFile({revert: true})  removes first element and reverts the upload with a DELETE XHR

But I cannot get removeFiles() working.  Behavior is the same for removeFiles({revert: false}) and removeFiles({revert: true}), always:

all items are removed from list
a revert with DELETE XHR is issued for the first file (independent of revert option)

Am I holding it wrong? ;-)

@sbusch should be fixed in release 4.19

Is it possible to remove specify file by passing the id, it always remove the first file?
Can we do some thing like this.$refs.filePond.removeFile({ revert: true, id: serverId }); ? (passing the actualid id in DB)


morphs break insert key

As soon as I key a morph the insert key breaks. After that every time I use the I shortcut or right click an pick insert key blender tries to add keys to the "Button Keying Set" the only way I can add keys for the rig is to add them through the item rollout and right click to add a key. What am I missing. I tried to lock the Button Key set - no help. Remove button key set - no help. Even with the auto key mode selected it always tries to add to the button key set.
Thanks
sc_studio

Found what it was - forgot to add morphs to daz morph set


Question: How is nuitka dealing with python imports?

@kayhayen Hello, If you recall I've already asked about this one on previous posts but the whole subject is still pretty confusing to me, so please allow me to come back to it once again.
I'd really like to understand how nuitka is dealing with python imports. While I'm fine considering other parts of nuitka code generation/optimization as a black box (at least for now) I'd really like to understand how this is working, I'd really like to understand fully the real meaning of the import control options group e.g. {--recurse-stdlib --recurse-none --recurse-all, --recurse-on --recurse-to --recurse-not-to --recurse-plugins --recurse-files, --recurse-pattern}.
From what I've roughly understood so far, the fact than nuitka parses/discover more or less imports won't affect to the PE Import Directory, right? Said otherwise, whether nuitka add more or less c++ that imports python stuff is just affecting the PE .text/.data sections, is this correct? Or... I'm just talking nonsense, I'm really confused about the whole subject :/
Anyway, summing up, consider this a very low-priority question it'd be really interesting if eventually you feel like it and write about it. In the form of blog post, an explanation here, in the dev manual... Being able to understand this will allow me to think about possible addons to add on top of nuitka that may or may not be relevant but definitely will give me a wider perspective about the whole thing.
Regards,
B

Brief note one about this one, it took me a little bit of time to fully understand the whole recursive options but after playing/fooling around and analizing the type of c code that was being generated out of a dummy hello world package things I've fully understood what they are doing.
Just adding this remark so you can decide whether is still important to eventually deal with this one or not. Maybe there are users more clever than me than by just reading the Options help will immediately grasp what they're intended for. In this particular case, I'm more a practical guy that learn by "doing" and checking what the code does ;)
\o

I sent an email to the mailing list about these, basically part of the --recurse-* options should be named more like --include, namely those that address filenames and directories, because that is what those do, and other others should be --follow or --nofollow to decide automatic following of imports if they are used or not.
Until I enhanced this, I am not going to describe the current state though. It's wild growth, and with the advent of --include options has become unnecessary.

So at long last, here is an answer, that I intend to put into user manual afterwards:
Inclusion vs Following vs. Defaults
The filename you gave on the command line is always included.
As for inclusion options: Inclusion of modules is supposed to only include that module no matter what. And of packages, that package, all modules below its namespace, no matter what. No other options will limit that. Your best attempt currently at excluding stuff defined to be included is to delete its Python files before compiling.
Following only happens when an import is encountered, starting from any included or followed to module, so that can happen recursively. You can enable or disable it globally. For standalone mode it's enabled globally, for module mode, it's disabled globally. But you can still make decisions for specific namespaces. When you say --nofollow-import-to that is going to take precedence over --follow-import-to no matter what.
Currently, to compile a package, you also have to include it with that option. That disables you from making overrides to it. A future release might change things, so that packages compiled are automatically included, but obey --nofollow-import-to=.tests to make it easy. Alternatively a --noinclude=.tests option with a high precedence could also come, this is not clear yet.
Obviously I hate documenting what I consider interim states, but there have been several people who wondered this already, and it's a fair question.


Functional mixins

There is a 4 years old term: functional mixin
The idea behind it is very similar to stampit's. -  "has-a" or "uses-a" relationships between composed components.
Correct me where I'm wrong.
Differences to stampit I found so far (please, add up):

The composition API implies your deep JS knowledge (see .call(prototype) calls below) and somewhat bulky.

var RoundButton = function(radius, label, action) {
    this.radius = radius;
    this.label = label;
    this.action = action;
};

asButton.call(RoundButton.prototype);
asCircle.call(RoundButton.prototype);

var button1 = new RoundButton(4, 'yes!', function() {return 'you said yes!'});
button1.fire(); //'you said yes!'

You can have only one initializator (aka constructor). In stampit you can have as many as you want.
Closures are proposed to do via IIFE. Which is handy, but not quite as stampit's init()'s.
The API doesn't protect you from long prototype chain hierarchies. Stampit fights against this bad habit. :)
The proposed way of doing things wouldn't allow set default values for all the mixins' states easily. I.e. while creating objects only a single "constructor" receives the passed arguments. See RoundButton above. Whereas stamp's .create(refs) method argument is merged into object instance.
The benchmarks are fast. Object creation is optimized because of using the new keyword and omitting _.extend for each object created.
Does not require any modules like stampit. Everything is vanilla JS.

Features stampit have but the proposed functional mixins don't.

Delayed instantiation. - Stampit init() function(s) can return promise, which then is being resolved to an object instance.
stamp.static() - this helps a lot to do BDD style coding. See this example.
Stampit allow you to deep merge data using stamp.props().

The benchmarks are fast. Object creation is optimized because of using the new keyword and omitting _.extend for each object created.

[ ] See "Is There a Big Performance Difference Between Classical and Prototypal Inheritance?"

We can reference those functional mixins in stamp wikipedia page. Huh?

I don't think we need to address functional mixins in our docs, and the wikipedia page has been deleted. Apparently we need to get more people writing about stamps so there are more sources than just my book. ;)
Can we close this issue?

Functional mixins got continuation. With ES7 decorators it looks very much alike composables but with a different syntax. Read here: http://raganwald.com/2015/06/26/decorators-in-es7.html
The composition syntax looks like this:
@BookCollector @Author
class BookLover extends Person {};

Where BookCollector, Author are composable behaviors (mixins) and the Person is ES6 class.
I see several downsides of this approach. Anyone else see them?

Ok so I'm new to ESNext and very very new to the stamps concept, but I can't seem to find how any of this can't be accomplished without decorators (and maybe also Reflection and Proxies which I know very little about), save for being able to instantiate a stamp without using new.  So to answer your question, I don't think I can see any downsides immediately but I'm probably overlooking something.
https://github.com/wycats/javascript-decorators has some examples showing how to decorate classes not only in the way your example gives above, but with arguments, and also to decorate methods and properties by using decorators inside a class.  This repo is the spec used by Babel's 'experimental' (used widely) implementation of decorators.
I'll grab a few examples from there for reference:
@isTestable(true)
class MyClass { }

function isTestable(value) {
   return function decorator(target) {
      target.isTestable = value;
   }
}

Passing an argument - factories here we come!
class C {
  @enumerable(false)
  method() { }
}

function enumerable(value) {
  return function (target, key, descriptor) {
     descriptor.enumerable = value;
     return descriptor;
  }
}

So it seems that you can use decorators as factories and also to enumerate classes. This allows you to avoid class inheritance with an incredible degree of flexibility, and leverage the power of javascript's prototypical inheritance powers very similarly to what stamps achieves.
Also, because decorators use Object.defineProperty in a way that precedes your defined class, you could use this to backfill and overwrite class properties in your constructor() method. For example:
@annotation
class MyClass {
  // override the decorator-provided property at the constructor() level so your class can do things with it after instantiation
   constructor(){
     this.isMyClass = true;
   }
   // or you could even override a property at the getter level!
   get annotated(){
     return `we don't need no annotation`;
   }
 }

function annotation(target) {
   // Add properties to target
   target.annotated = true;
   target.isMyClass = false;
}

Lastly, the descriptor argument in a decorator function has some niceties.
let descriptor = {
  value: specifiedFunction,
  enumerable: false,
  configurable: true,
  writable: true
};

(To be honest I don't totally understand this yet but the spec has some nice examples)
And one last thing - because stamps are a specification, it is quite possible that a set of convenience decorators/etc could be used to create stamps!
I wonder if someone could create a minimalist ESNext implementation of the stamp concept with all the desired bells and whistles, using as much of the es6/7/etc spec that is available to, say, Babel, as is possible.
Once 'desugared' it would probably look similar to this library!
Looking forward to someone proving me wrong, because I've only scratched the surface with all of this yet!

Let me start with a quote:

social networks rank strategies prioritize the popular and habitual

I would rephrase to:

people prefer the popular and habitual

Classes are habitual. Decorators are popular in C# and Java (and few other languages). It's logical to see people (re)implementing the same in all other new languages like JavaScript.
The downsides listed by Eric above are pretty much applicable to the decorators too.

You won't be able to compose two classes, and you won't be able to compose two decorators only (without a class, or method, or else). You'd have to decide which behavior would be a class, and which is a decorator.

It is a very, very hard choice. Trust me. I did that for years in C#.
Also, stampit deliberately avoid class, constructor, new and instanceof keywords applications to stamps. These are antipatterns in JS (see Eric's link above).
Additionally, while applying decorators you need to know which object they are applicable to: class, method, data, etc. Whereas in stampit you just .compose().
The JavaScript property descriptors (aka Object.defineProperty) with all the bells and whistles are coming to stampit v3. And they are already implemented and described here: https://github.com/stampit-org/stamp-specification
Saying all that I am thinking of using decorators and stamps together. They can be a good match!


Programmatically decide which section to move

First of all, thanks for these awesome plugin, it really get its job done!
Is there a way to programmatically tell scrollify which section to move? Maybe implementing some callback that uses the return value to reference the section to move or something like that?
Thanks!

Use the move method

I have the same problem.
I think what @joaquinrulin is trying to say, is how can you put some logic to decide which is the next section to move. In my problem the sections are not in consecutive order, so I have to decide which one to move. If I put this logic in the before hook and use the move method it enters an infinite loop. The other posible solution is to implement the on-scroll method and then call move method, but this sound counterproductive (if the library already has an in-built on-scroll definition). Maybe it could be public so we could do something like this:
$.scrollify.onScroll(function() {
  // Section selection logic here...
  $.scrollify.move(element);
});

Thanks for the explanation @KimDongHwan. Scrolling to non-consecutive sections is not something that Scrollify supports, but it's certainly something you could relatively easily modify Scrollify to achieve. Internally Scrollify uses a variable called index to define which section to scroll to, maybe you could create a setIndex method that could change the index to what you need.

Thanks, I will try that!