@angular2-material 2.0.0-alpha.8 not working

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[ x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?
bug

What is the current behavior?
When using the latest release of angular2-webpack-starter with angular 2.0.0-rc.6, when trying to integrate angular2 material from the material branch, and using version: 2.0.0-alpha.8 I get:
(Running the app does not work, Is it possible to upgrade the material branch so I can see where the problem lies?)

WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>20:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>15:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>15:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>15:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>8:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>8:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>16:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>8:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>8:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>8:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>15:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>17:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>9:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>7:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>8:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>12:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in<EMAIL_ADDRESS>3:24 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

They've released 2.0.0-alpha.8-1. I think you can also obtain it using @latest.

thanks, solved by using 2.0.0-alpha.8-1


Create table editor

Edit table 'live'
Add new row at the bottom of the table automatically
Where appropriate, filter acceptable choices via AJAX

BOM editor
orders (CSO / PO)

Drag and drop re-ordering
New line at the bottom
Update data via AJAX
Auto-complete fields using JSON API
POST at the end
Auto-complete for fields

Proposed / implemented solution:

Data is edited 'in-line' using modal forms which are pulled in via AJAX
Page (or components thereof) are reloaded as necessary
Data tabulation performed using footable


[Nette\Application\BadRequestException] No route for HTTP request.  when running tests

I'm getting this error when running codecept run functional

Functional Tests (1) ---------------------------------------
E Test1Cest: Verify homepage (1.16s)
Time: 14.23 seconds, Memory: 34.00MB
There was 1 error:

Test1Cest: Verify homepage
Test  tests\functional\Test1Cest.php:tryToTest

[Nette\Application\BadRequestException] No route for HTTP request.
Scenario Steps:

$I->amOnPage("/") at tests\functional\Test1Cest.php:18

#1  C:\Development\project\web\vendor\nette\application\src\Application\Application.php:83
#2  C:\Development\project\web\vendor\arachne\codeception\src\Connector\NetteConnector.php:73
#3  C:\Development\project\web\vendor\symfony\browser-kit\Client.php:315
#4  Codeception\Lib\InnerBrowser->amOnPage
#5  C:\Development\project\web\tests_support_generated\FunctionalSuiteTesterActions.php:142
#6  C:\Development\project\web\tests\functional\Test1Cest.php:18
#7  Test1Cest->tryToTest

Homepage HTML is outputed in console when calling command also, and HTML is correct of homepage , and links looks good there also...
You need some more info on it or you have a clue what could it be?
My Test1Cept looks like:

class Test1Cest
{
    public function _before(FunctionalSuiteTester $I)
    {
    }

    public function _after(FunctionalSuiteTester $I)
    {
    }

    // tests
    public function tryToTest(FunctionalSuiteTester $I)
    {
		$I->wantTo('Verify homepage');
		$I->amOnPage('/');
		$I->see('Welcome');
    }
}

and _bootstrap file:
define('WWW_DIR', __DIR__ . '/../../www');
define('APP_DIR', __DIR__ . '/../../app');
define('ESHOPID', 1);
$_SERVER['REMOTE_ADDR'] = '<IP_ADDRESS>';
$_SERVER['HTTP_HOST'] = 'project.local';
$_SERVER['REQUEST_METHOD'] = 'GET';
$_SERVER['HTTPS'] = TRUE;
require __DIR__ . '/../../app/bootstrap.php';
return $container;

I'm just wanting this to work then I'll play with correct bootstrap, different db connection and etc...
and functional.yml
error_level: "E_ALL"
class_name: FunctionalSuiteTester
modules:
    enabled:
        - Arachne\Codeception\Module\NetteApplicationModule
        - Arachne\Codeception\Module\NetteDIModule:
            tempDir: ../../temp/cache/functional
            configFiles:
                - ../../app/config/config.neon
                - ../../app/config/config.local.neon
                - config.neon

Don't know if it's related but What I've noticied now when debugging is that
https://github.com/symfony/browser-kit/blob/master/Client.php#L286
$uri = $this->getAbsoluteUri($uri); returns http://localhost/
and not my virtual host... Is that maybe issue?

I believe problem is in my custom router. I did little debugging
https://github.com/nette/application/blob/master/src/Application/Routers/RouteList.php#L37
First time page is loaded I have all my routes here (this load is probably directly from codeception, I don't know...), but then when it hits my code $I->amOnPage('/'); now $this does not have any routes defined...
How can I avoid this? any thoughts?

Ok so first a response I've written when reading your latest post on nette forum:
Oh. Ok I'l try to help you out. I'd like my repository to be compatible with most people's use cases but it's difficult to achieve without knowledge of other people's applications.
Arachne/Codeception should work with Nette 2.4 (~2.3 means >=2.3 && <3.0). Should be compatible with both 2.3 and 2.4...
With Arachne/Codeception your app/bootstrap.php file is NOT executed at all. If you included it manually somehow (which you should not) the container your bootstrap.php returns won't be used anyway.
Instead you should set up your routes in a RouterFactory service (see https://github.com/nette/sandbox/blob/master/app/router/RouterFactory.php and https://github.com/nette/sandbox/blob/master/app/config/config.neon#L23).

Oh and your tests/functional/_bootstrap.php file should be empty. I mean mine is.

That's all I can think of at the moment. Let me know if the RouterFactory service helps and how far you'll get that way.
When you manage to set it up we will need to update the docs in this repo accordingly to prevent other users running into the same problems.
Thanks for bringing this up!

Well I'm working on project that's preety old, started with nette 0.9. Project is preety big and rewriting it or clearing out deprecated code isn't easy. It's working currently with nette 2.4 but most of the stuff needs to be rewritten, to much usage of \Nette\Environment through project and basically I'm easily modernizing it to go up to date, but that's task that will span over long period of time... Some modules are in rewrite process and they're done proper nette 2.4 way, router is still not there, but this is rather easy fix. Now I'm figuring out how this all is working since I'm new with codeception, so wasn't really sure how it supposed to work, but I'm getting there. Thanks for your support, I'll resolve this my way, I'm close to it, and then I'll write here how it went, what I did and why (I'll have to bypass some stuff because of legacy code in my project)

Glad to help. Let me know if you run into any more troubles. I'm looking forward to your report!
Just a recommendation - write the stuff down periodically before you forget the details. ;-)

I would do that but sometimes I have to go two steps behind so I can advance and then this here would be mess.
first test is running now and it's running fine with warnings :)
1050x DEPRECATION: Nette\Environment is deprecated
Those are the steps I did:
my bootstrap.php file has to be loaded because I still have some initializatione code there without which my app won't run so this is my _bootstrap.php:
define('WWW_DIR', __DIR__ . '/../../www');
define('APP_DIR', __DIR__ . '/../../app');

$_SERVER['HTTP_HOST'] = 'heimkaup.local';

require __DIR__ . '/../../app/bootstrap.php';

and in tests:
    public function _before(FunctionalSuiteTester $I)
    {
    	$container = $I->getContainer();
    	require (__DIR__ . '/../../app/bootstrap-router.php');
    }

I know it's bad, but I'm making it work. Now I can easily try to make this work properly...
I have to clear out bootstrap.php code which I was planning for a long time, and properly initialize router, after that all should be fine...

Yeah that _bootstrap.php seems about fine. My app is much newer so I've written it to keep my app/bootstrap.php as simple as possible. Try initializing what you can in services. Also you might need to add your own CompilerExtension to add some code into container initialization in afterCompile (like https://github.com/Kdyby/Translation/blob/master/src/Kdyby/Translation/DI/TranslationExtension.php#L448-L454).

I've got rid of bootstrap-router, so I've got rid of
   public function _before(FunctionalSuiteTester $I)
    {
        $container = $I->getContainer();
        require (__DIR__ . '/../../app/bootstrap-router.php');
    }

I think that's actually good enough for now, willcleanup app/bootstrap.php little bit, but that actually now doesn't have any influence on tests setup, would be nice to get rid of global constants through the code, but I don't see that comming soon...
Thank you very much for your help.


fails to build - Error 2

[ 93%] Building C object esp-idf/hccapx_serializer/CMakeFiles/__idf_hccapx_serializer.dir/hccapx_serializer.c.obj
/Users/XXXX/Downloads/esp32-wifi-penetration-tool-master/components/hccapx_serializer/hccapx_serializer.c: In function 'save_eapol':
/Users/XXXX/Downloads/esp32-wifi-penetration-tool-master/components/hccapx_serializer/hccapx_serializer.c:102:49: error: implicit declaration of function 'ntoh' [-Werror=implicit-function-declaration]
     eapol_len = sizeof(eapol_packet_header_t) + ntohs(eapol_packet->header.packet_body_length);
                                                 ^~~~~
cc1: some warnings being treated as errors
make[3]: *** [esp-idf/hccapx_serializer/CMakeFiles/__idf_hccapx_serializer.dir/hccapx_serializer.c.obj] Error 1
make[2]: *** [esp-idf/hccapx_serializer/CMakeFiles/__idf_hccapx_serializer.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....

then a couple lines later...
make[1]: *** [CMakeFiles/flash.dir/rule] Error 2
make: *** [flash] Error 2
make failed with exit code 2

I'm on mac os 10.14.6

I have only Error 1 but it's practically the same issue:
[2/11] Building C object esp-idf/hccapx_serializer/CMakeFiles/__idf_hccapx_serializer.dir/hccapx_serializer.c.obj FAILED: esp-idf/hccapx_serializer/CMakeFiles/__idf_hccapx_serializer.dir/hccapx_serializer.c.obj
And later:
    eapol_len = sizeof(eapol_packet_header_t) + ntohs(eapol_packet->header.packet_body_length);                                                  ^~~~~ cc1: some warnings being treated as errors ninja: build stopped: subcommand failed. ninja failed with exit code 1

BTW this is on the Wemos S2 mini. Somehow this is not working on that board...

I have tried many many ways both on Linux with IDF and on windows with a couple of programmers. I've erased the mem in every try but it will NOT work on the Wemos S2 board...

O.k. so I finally got this working:

install VSCode on Linux
install ESP-IDF plugin and leave everything default
clone the github in VScode
build in VScode
make sure every setting in the lower blue bar is set to the correct setting:
Select port (on my sys it was /dev/ttyACM0), Select board: ESP32s2, set flash type to UART then click flash...

VSCode installs a released version (4.4.1 at the moment) instead of checking out master. So likely that's where the difference, and thus this issue lies. I had the same problem, also solved by just pulling the v4.4.1 branch of esp-idf.


⚠ Bofrost.at has degraded performance

In ae4cc52, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2356 ms

Resolved: Bofrost.at performance has improved in c480a20.


feat(snapshots): write Receipt to snapshots during ExecutionStage

attention: it only writes to static files if there's no pruning/configuration enabled for receipts (includes --full which only includes deposit contract receipts). Meaning: it keeps them on database
on top of #5733

Testing on holesky, but rfr.


Update pom file to leave the server running when you run the local deploy profile.

Update pom file to leave the server running when you run the local deploy profile, remove the docker profile as it is no longer needed and update README.md to reflect changes.

This change is

Reviewed 3 of 4 files at r1.
Review status: 3 of 4 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Use TestKit for defining and executing functional tests

All tests under integTest should be executed with TestKit, the built-in solution for executing functional tests with Gradle.
Goal: Avoid any custom infrastructure logic, benefit from built-in features.
What is called integration test in this project should be coined with functional test. You can find other examples on the setup of TestKit in other plugins I wrote e.g. the Docker plugin.

Thank you for the suggestion @bmuschko
I will use your Docker plugin for examples, I want to become more familiar with the TestKit in general so this is a very good excuse to do so.

I am impressed with the clarity and structure of your tests in the Docker plugin @bmuschko - I think I will borrow much of your build logic when I get to this task. I am excited at the opportunity to make this change.


Error while setting up synapse pyspark env

Using pre-release v0.4.1
Preparing synapse pyspark env...
conda 23.3.1

Checking if conda is installed ... true
User Agent is node/16.17.1 (windows_nt 10.0.22621; win32; x64)
C:\Users\ThomasHilles�y\anaconda3

C:\Users\ThomasHilles�y

Download c:/users/thomashilles�y/.ipython/profile_default/startup/init_lighter.py script completed, download to c:/users/thomashilles�y/.ipython/profile_default/startup/init_lighter.py
Error: ENOENT: no such file or directory, open 'c:\users\thomashilles�y\.ipython\profile_default\startup\init_lighter.py'
Installing PySpark releated packages error

Hi, @thilles . Please update to the latest vscode version. This issue has been fixed.


How to query without a schema?

Hey!
Thanks for making a gem.
I don't have a schema for my endpoint, but I do have a query + params. Is there a way to query without a schema (file or http)?
Thanks!

Not sure, but this might be helpful: https://github.com/rmosolgo/graphql-ruby/pull/2327 and https://github.com/github/graphql-client/issues/211 (another client)

Yes, @dblock is right about this. Theoretically you may not need a schema in production, but this needs to be implemented in the underlaying gem first.


Allow generate signed url for upload objects

We provide an API Reach for generating an URL for an object for the user to get.
Maybe we can provide like Reach but for uploading an object.

How about add API like:
type Accessor interface {
    func Access(op, path string, pairs...) (req *http.Request, err error)
}

We can implement it as most object support SignedURL.
For Accessor, I have two other doubts：

What's the difference between Reach() and AccessRead()? Both of them are used for reach an object, maybe AccessRead() is not needed?
If the service only support AccessRead(), like kodo, does it mean we can't implement Accessor for it?

Hi, I camp up a new idea that, we can define a new interface like:
type HttpSinger interface {
    QuerySignHttp(req *http.Request, ps ...types.Pair) (req *http.Request, query string, err error)
//    HeaderSignHttp(req *http.Request, ps ...types.Pair) (req *http.Request, auth string, err error)
}

For now, HeaderSignHttp is not required, we can add them later.

QuerySignHttp(req *http.Request, ps ...types.Pair) (signedReq *http.Request, url string, err error) is indeed more universality. We can generate request's signed URL in QuerySignHttp.
As external methods are provided for obtaining signed URL for most services, maybe the parameter req *http.Request complicates matters：

Users need to pass in the req.URL correctly.
We need to parse req.URL to get the wanted request resource(operation, path...).

How about one of the following methods：

QuerySignHttp(op path string, ps ...types.Pair) (signedReq *http.Request, err error)
QuerySignHttp(req *Request, ps ...types.Pair) errortype Request struct {
    Name        string  // "GetObject"
    HTTPPaht    string  // "{Key+}"
    HTTPRequst  *http.Request
    ...
}

req, err := store.QuerySignHttp(types.OpRead, "abc")

req, err := store.QuerySignHttp(types.OpWrite, "abc", pairs.WithContentType("application/json"))

req, err := store.QuerySignHttp(types.OpWriteMultipart, "abc", pairs.WithMultipartId("qqqq"))

Looks nice.

req, err := store.QuerySignHttp(types.OpRead, "abc")

req, err := store.QuerySignHttp(types.OpWrite, "abc", pairs.WithContentType("application/json"))

req, err := store.QuerySignHttp(types.OpWriteMultipart, "abc", pairs.WithMultipartId("qqqq"))

I will continue the GSP based on this.


Temporarily fix README URLs.

The doc directory has a ver0.3 area temporarily until new docs settle. It'll be a little nicer to newcomers to still see the images in the README.
Thanks!

Thanks!


Prompt disappear on ctrl+c

Prompt disappear on ctrl+c (SIGINT)
Instead of C:\folder [(master)]> it's replaced by C:\folder PS
If I hit enter, prompt goes back to C:\folder [(master)]>
I just installed posh git with psget from within powershell on a fresh install of windows 8.1.
PSVersionTable:
Name                           Value
----                           -----
PSVersion                      4.0
WSManStackVersion              3.0
SerializationVersion           <IP_ADDRESS>
CLRVersion                     4.0.30319.42000
BuildVersion                   6.3.9600.17400
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion      2.2

Edit: reproducible on windows 10 with posh-git version 869d4c5159797755bc04749db47b166136e59132
C:\Users\i301937\Documents\GitHub\saplinks [master]> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.0.10240.16384
WSManStackVersion              3.0
SerializationVersion           <IP_ADDRESS>
CLRVersion                     4.0.30319.42000
BuildVersion                   10.0.10240.16384
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3

Not reproducible with version <IP_ADDRESS>5 got with oneGet on windows10

I see the PS periodically when I hit Ctrl-C, but the Git prompt always comes back by hitting Enter again so I have never bothered to try to figure out why. I doubt there is much we could do to intercept the Ctrl-C anyway…?

apparently we can with TreatControlCAsInput
see http://stackoverflow.com/questions/1710698/gracefully-stopping-in-powershell
I haven't tried though

Yeah, if I spam Ctrl-C I can get it to happen.

I don't know if it's worth spending time on that.

I tend to agree, though if someone wants to tackle it I'm curious what they could come up with.


Version Numbers - Align with PyPI

Can you adjust the version number so that it is inline with PyPI expectations?
kevin@pegasus:~/vncdotool$ make
/usr/local/lib/python2.7/dist-packages/setuptools/dist.py:350: UserWarning: The version specified ('0-11-1') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
  "details." % self.metadata.version
/usr/local/lib/python2.7/dist-packages/setuptools/dist.py:350: UserWarning: The version specified ('0-11-1') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
  "details." % self.metadata.version

I'm not able to reproduce that issue.  Is that an older version of vncdotool you have checked out?
> make version
python setup.py --version
0.11.1

Perhaps its just legacy artifacts on my system, but I just did a fresh clone of the github.
kevin@pegasus:~$ git clone  https://github.com/sibson/vncdotool.git
Cloning into 'vncdotool'...
remote: Counting objects: 1464, done.
remote: Total 1464 (delta 0), reused 0 (delta 0), pack-reused 1464
Receiving objects: 100% (1464/1464), 415.06 KiB | 0 bytes/s, done.
Resolving deltas: 100% (831/831), done.
Checking connectivity... done.
kevin@pegasus:~$ cd vncdotool
kevin@pegasus:~/vncdotool$ python setup.py build
/usr/local/lib/python2.7/dist-packages/setuptools/dist.py:350: UserWarning: The version specified ('0-11-1') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
  "details." % self.metadata.version
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/__init__.py -> build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/pyDes.py -> build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/rfb.py -> build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/loggingproxy.py -> build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/client.py -> build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/api.py -> build/lib.linux-x86_64-2.7/vncdotool
copying vncdotool/command.py -> build/lib.linux-x86_64-2.7/vncdotool
kevin@pegasus:~/vncdotool$

Submitted a quick PR.... #101


[Static Analysis] Use Rector 0.9 for 4.1 branch with php version feature 7.3

Update rector dependency to 0.9 for 4.1 branch with php version feature 7.3
Checklist:

[x] Securely signed commits

@paulbalandan if the  latest fix on Postgre testing currently still in develop, it can wait until 4.1 branch rebased against develop.

@paulbalandan if the  latest fix on Postgre testing currently still in develop, it can wait until 4.1 branch rebased against develop.

@paulbalandan if the  latest fix on Postgre testing currently still in develop, it can wait until 4.1 branch rebased against develop.

@paulbalandan if the  latest fix on Postgre testing currently still in develop, it can wait until 4.1 branch rebased against develop.

4.1 is rebased to develop - @samsonasik looks like you will need to rebase as well, sorry about that. Might be easier to start over?

4.1 is rebased to develop - @samsonasik looks like you will need to rebase as well, sorry about that. Might be easier to start over?

Yes, I will start over.

Yes, I will start over.


Further clarifications about adding joints

Hi,
Thank you for providing this library, I have been looking for a FK/IK solution in Arduino for such a long time!
Would you kindly clarify what do the parameters mean when adding a new joint please -> kinematics_object.add_joint_axis(0, 0,  1,  4, 0,    0);
Should these present joint position + orientation of each joint ?
Thank you very much,

Hi,
The add_joint_axis method takes in a joint axis expressed as a screw axis in the base frame. A screw axis representation can be used to determine the relationship between the two consecutive links that the joint connects.
The following video explains the process of determining the screw axis of the joints by means of an example: https://youtu.be/cKHsil0V6Qk](https://youtu.be/cKHsil0V6Qk](https://youtu.be/cKHsil0V6Qk)). Note that the screw axis needs to be expressed in the S frame for this library.
Let me know if you need any other clarifications.


Add bindings for misc image methods

This PR adds support for a small handful of misc image methods which are not covered by the binding, such as hasalpha.
Since vips is still a bit of a black box for me, I'm not 100% sure that this is the correct way to add support for these methods, but it looks like pyvips does the same thing.
I'm not sure whether tests are necessary here, and if they are, I'm not sure where to put them.

For addalpha, I'd put something like this just after bandsplit (ie. in the convenience method area):
function Image_method:addalpha()
    local max_alpha

    if self:interpretation() == "rgb16" or
        self:interpretation() == "grey16" then
        max_alpha = 65535
    else
        max_alpha = 255
    end

    return self:bandjoin(max_alpha)
end

(I've not written Lua for a long time and that's untested, I hope I have it right)

Hi, I've amended this PR to only add the hasalpha and addalpha methods. I've also rebased on master and added tests for the new functionality.

Look good!
I guess array.lua needs some local adding. I wonder why lint passed this before?

Could you also add a line to changelog? And credit yourself, of course.

... libvips now has:
double
vips_interpretation_max_alpha(VipsInterpretation interpretation)
{
    switch (interpretation) {
    case VIPS_INTERPRETATION_GREY16:
    case VIPS_INTERPRETATION_RGB16:
        return 65535.0;
    case VIPS_INTERPRETATION_scRGB:
        return 1.0;
    default:
        return 255.0;
    }
}

but it was only added recently, so you'd need to add a test. It's simpler just to reproduce the code in lua.

libvips already provides an addalpha function: https://www.libvips.org/API/current/libvips-conversion.html#vips-addalpha, https://github.com/libvips/libvips/blob/159e8bea25fbc70316e32cd36add0b7c899568b7/libvips/conversion/bandjoin.c#L521-L541. Why don't we simply make the binding call that instead of reimplementing the logic in Lua?

Actually, how come the binding doesn't cover addalpha already? I can't really say I understand how the binding works yet but what makes addalpha different from the other conversion methods that are automatically bound (e.g. composite, premultiply, etc.)?

libvips is in a few layers:

At the base is GObject, the object system from glib. It's a little like Java, so single-inheritance, multiple inheritance of interfaces, introspection (a mix of runtime and derived from scanning header files), and a signal/slot mechanism (java delegates).
libvips layers VipsObject on that, which adds mostly full run-time introspection and some extra stuff around object lifetime management.
Next is a VipsOperation class which defines operation lifetime (create object, set parameters, build, read results, dispose).
Things like VipsComposite are VipsOperation subclasses that implement image composition (obviously).
lua-vips works by catching references to undefined methods on the image object, then walking the class hierarchy below VipsOperation and looking for a class with that nickname. It's actually pretty simple, just a 150 lines of lua in voperation.lua.

The libvips C API is just a few thin wrappers over this object system. The C++ / ruby / python / php / etc. bindings all work the same way -- in effect, the libvips binding is generated at runtime via introspection. The nice thing is that because it's mostly automatic, the lua binding is tiny, and will work with new versions of libvips with (usually) no changes needed. No maintenance is the best maintenance!
You can use vips -l to show the libvips class hierarchy, it might make it clearer:
$ vips -l
  VipsOperation (operation), operations
    VipsSystem (system), run an external command
    VipsArithmetic (arithmetic), arithmetic operations
      VipsBinary (binary), binary operations
        VipsAdd (add), add two images
        VipsSubtract (subtract), subtract two images
...

vips_addalpha() doesn't use this object system, it's just a simple C function in the C API (which lua-vips does not use), so it won't appear.
You could call it via ffi, but it was added fairly recently, so you'd need something like eg.:
if libvips.version > 8.9 then
  return vips_addalpha(in)
else
  return in:bandjoin(max_alpha)
fi

Since you'll need the lua fallback anyway, and it's trivial, it's probably simpler to just always use that.

The gobject docs have an introduction to their object system, if you're curious:
https://docs.gtk.org/gobject/index.html

Oh, I see, thanks for the explanation.

It was added fairly recently, so you'd need something like eg.:

Would that really be necessary, though? Why bother polyfilling older versions of the library? Wouldn't it be reasonable to simply throw an error when someone tries to use a function that doesn't exist in their version of libvips?
I'm just concerned that by (re)implementing functions in Lua, we're treading a thin line; whenever the libvips function is updated (such as to add support for scRGB), we'll have to update the Lua implementation, or risk a situation where the binding silently produces results different from libvips (which, IMO, is worse than having the binding fail completely).

I had a go and I think calling the C API for this would be tricky and likely to cause bugs in future. It's much cleaner and safer to have a plain lua implementation.
We could add addalpha as a true libvips operation, that would be another good approach.

Right, I didn't realize that calling the C API for addalpha would be less trivial than for e.g. hasalpha, since it creates a new image.
I'm in favour of making addalpha a true libvips operation; I'll try to open a PR if someone doesn't beat me to it. In the meantime, we can probably merge this.

Thanks @RiskoZoSlovenska for your contribution. I merged it.


Error when batch query!

i'm having a error when i run batch query:
foreach ($query->each($batchSize) as $item) {
}

Can you wrote more info about this error?


Add prettier formatting to dependabot prs

Description
Dependabot PRs add a Changelog line which fails the recent prettier check. See https://github.com/opensearch-project/opensearch-go/actions/runs/4662363358/jobs/8252624135?pr=294
This PR adds a prettier formatting in the dependabot PR workflow.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Seems like we need to install it first.
      - name: Install dependencies
        run: npm i -g npm@8 && npm i -g prettier


Cannot submit Workflow that uses ValueFrom "supplied" field

When trying to create a Task which uses the "supplied" field of ValueFrom (see https://argoproj.github.io/argo-workflows/fields/#valuefrom), the submission fails as the field in Hera is a bool, so the output yaml contains supplied: true instead of the expected supplied: {} which is shown here https://github.com/argoproj/argo-workflows/blob/master/examples/suspend-template-outputs.yaml#L33
The error itself:
cannot unmarshal bool into Go struct field ValueFrom.template.spec.templates.outputs.parameters.valueFrom.supplied of type v1alpha1.SuppliedValueFrom

I believe this will be fixed by #420 as https://github.com/argoproj-labs/hera-workflows/pull/420/files#diff-b1d6ef48f102cc95d204c1e886127c7e057e3dca0622f020b0f61c8ea3d62ab1R1109 as SuppliedValueFrom will be an empty class, not a boolean, so the new usage code will look like
Parameter(name="supplied-var", value_from=ValueFrom(supplied=SuppliedValueFrom()))

Just filing the issue for visibility and to ask for the PRs to merge and release asap! 🙏 Thanks!

Thanks for bringing this up @elliotgunton! Glad to know the auto-generated models will solve the issue :) I think we should be able to release the PRs soon. I am currently working on constructing the Container, Task, Suspend, etc, objects, which migrate the existing core objects like Task and Workflow. When that is done I will put up a PR and tag you since, at that point, we can start merging the new release.

@flaviuvadan I realised the PRs will only add the openapi models themselves, and files such as https://github.com/argoproj-labs/hera-workflows/blob/f75597bd4f68bddbf7d2e39a146ee26615af55b9/src/hera/workflows/workflow.py and at https://github.com/argoproj-labs/hera-workflows/blob/f75597bd4f68bddbf7d2e39a146ee26615af55b9/src/hera/workflows/value_from.py#L77 specifically, the usage of self.supplied will be the same so won't build the yaml correctly. I'll be making a PR to fix a couple of bugs I saw around this hopefully today! 😄


Support for Codegen gpt2 model

I tried to load the model and reference model using the following for codegen model
model = AutoModelForCausalLM.from_pretrained(ckpt,             trust_remote_code=True)
where ckpt is salesforce finetuned model path.
I get the following error while initializing
    ppo_trainer = PPOTrainer(config, model, ref_model, tokenizer, dataset=dataset, data_collator=collator)
ppo_trainer = PPOTrainer(config, model, ref_model, tokenizer, dataset=dataset, data_collator=collator) *** ValueError: model must be a PreTrainedModelWrapper, got <class 'transformers.models.codegen.modeling_codegen.CodeGenForCausalLM'> - supported architectures are: (<class 'trl.models.modeling_value_head.AutoModelForCausalLMWithValueHead'>, <class 'trl.models.modeling_value_head.AutoModelForSeq2SeqLMWithValueHead'>)
@lvwerra   Any suggestions ?

Thanks @lvwerra . It worked.

Awesome! Closing the issue now


Update lm_kiviads.md: wrong bidder code

🏷 Type of documentation

[x] text edit only (wording, typos)

Hello, could you please update the site as soon as possible? Thank you!

@KiviAds - I see the code PR for a new adapter -- https://github.com/prebid/Prebid.js/pull/10415
But there's also a docs PR for that new adapter at https://github.com/prebid/prebid.github.io/pull/4829
Can we cancel this PR?

I'm going to assume that https://github.com/prebid/prebid.github.io/pull/4829 overlaps with this ticket. Closing.


LGA data

Hello - Did you add this in the end? I can't spot it. I'm submitting the final data/story to the ODI on Monday for them to consider do if we can include it there's not much time left.

I've made another shot at this, and I'm importing from the dataset you prepared last year.
It seems a bit off. My test run generated 362 new entries and 160 errors out of the 1623 rows of data in the file.
I'm doing it again now, with some tweaks, into the database behind https://gbptm-stage.herokuapp.com
I initialised that database with a copy of the current production data as of about 6pm this evening.
You'll be able to compare the two datasets by  switching between "production" and "staging" in the settings screen of the admin tool.
I expect the import to complete at about 10.30ish this evening...

Hello
Thanks.
It seems to have only imported the councils that state they use WGS84 and not those using OSGB36? - comes to 383 toilets including Poole who don’t state what they use, with 231 new toilets.
Of the councils from that list that I’ve looked at, Poole, Mid Sussex, Plymouth, Lichfield seem to match OSM locations most of the time.
Hillingdon, Brent, Mid Suffolk, West Oxfordshire are a bit out causing duplications.
It seems hit and miss and likely that most of those new toilets risk being duplications where either the LGA data locates poorly (Hillingdon) or our existing data is in the wrong place (Plymouth).  I’d need to check through them using the GBPTM Analyser before they went ‘live’. If I edit the ‘staging’ dataset does that store my edits until they’re made live? I don’t want to spend time on it then find they’re written over if you tried importing LGA dataset (for the OSGB36 date or anything) again, in which case I can hold off.
Is our de-duplicator still set at 20m? I think this was a mistake on my part - too restrictive.
It doesn’t seem like any of the councils in the LGA list feature as ‘best’ or ‘worst’ in any of our statistics so in that sense it won’t be obvious that they’re not included in the Production dataset at this point. It would be good if they were by November 18th so we’ve met that deliverable, but it depends how much correction work I’d need to do on it..
Gail.

On 16 Oct 2016, at 20:20, Rupert Redington<EMAIL_ADDRESS>wrote:
I've made another shot at this, and I'm importing from the dataset you prepared last year.
It seems a bit off. My test run generated 362 new entries and 160 errors out of the 1623 rows of data in the file.
I'm doing it again now, with some tweaks, into the database behind https://gbptm-stage.herokuapp.com https://gbptm-stage.herokuapp.com/
I initialised that database with a copy of the current production data as of about 6pm this evening.
You'll be able to compare the two datasets by switching between "production" and "staging" in the settings screen of the admin tool.
I expect the import to complete at about 10.30ish this evening...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/neontribe/gbptm/issues/76#issuecomment-254067827, or mute the thread https://github.com/notifications/unsubscribe-auth/ACkOD6i9RSm21rZdhtS7GbdDd_-Bg4txks5q0njtgaJpZM4KW_mL.


Implement TreeItem.get_button_tooltip(column, idx).

When added to TreeItem, buttons are given tooltips. When returned via get_button(...), however, the button is a Texture and the tooltip information isn't included.
For accessibility purposes, it is useful to have access to the tooltip text. As such, we can retrieve a button's tooltip to use as a button label.
My accessibility addon needs this to allow keyboard control over buttons in Tree columns. Specifically, without it, I can't add keys/buttons to actions.
Related to #14011.

Thanks!


OpenAPIDemo LEDGER_URL environment variable not available to run_demo script

Running MacOS Monterey 12.1
When using the demo instructions for docker for the OpenAPIDemo I found that the $LEDGER_URL environment variable was NULL within the ./run_demo script.
This was causing the demo to fail. The docker container would try to start but would fail to obtain the genesis file and quickly terminate.
Modifying the command to use export LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io fixed it for me.
This link helped me figure this out.

By default the run_demo script assumes that a local instance of an Indy network is being used, and that the user has started an instance of von_network.  For the OpenAPIDemo, the Greenlight Dev Indy network is used, as outlined in the Getting Started. To use that, you prefix the commands with setting the LEDGER_URL as noted in the instructions you reference -- LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber --events --no-auto --bg -- that first part sets the environment variable used in the rest of the script.


Make xlsx import much faster

As tested in a leapfrog, using an external python script xlsx2csv instead of Roo is much faster. In some test with a large .xlsx import time went down from ~5 minutes to 10 seconds (30 times faster).
Implement the necessary changes to deploy this.

So much faster! :+1:


 We then intend to use these features to predict team performance across different tasks, to understand how different theories about team communication processes "play out" across different task contexts.
The Problem
At the end of the day, the features that we are measuring are only proxies of the "true" underlying team feature. Consider, for example, the following causal diagram. We might think, based on behavioral science theories, that Feature A (Positivity) positively impacts our Dependent Variable B of interest (Team Performance). But in reality, we do not have access to the true positivity of a team --- that's inside the hearts and minds of team members. We only have access to what they said during a given interaction, and we can generate proxy measures (e.g., Proxy A' and Proxy A'') using different computational methods to try to predict the underlying variable.
This problem generally applies to all features; in the image below, we also extend it to some Feature C (measured by Proxies C' and C'') and Feature D (measured by Proxies D' and D'').

Suppose then that we use these proxies to predict team performance, and we find that D' is stronger than A' for predicting team performance.
Can we then say, for this task, "Feature D is a stronger predictor of team performance than Feature A?"
One potential issue here is that we don't know whether the reason Feature D' > Feature A' is because Feature D > Feature A (e.g., the underlying feature is a better predictor), or simply because D' is a stronger proxy of D than A' is a proxy of A (in other words, A' is just a weak proxy for an otherwise strong theory). We need some way to validate or evaluate the computationally-extracted features so that we can argue that they all do a reasonable job of quantifying the underlying human construct.
To do this, we need labels.
Proposal: Creating a Parallel Labeling Pipeline to Validate Computationally-Extracted Features
I'd like to gut-check the following proposed pipeline:

As we extract features from the literature review, we will also note down the exact original definitions and survey questions traditionally used to measure those constructs in psychology.
Just as we did for Task Mapping, we create survey questions around those original definitions/questions.
We put those survey questions into the same rating pipeline as Task Mapping, and we ask our panel of High-Effort Turkers to rate a small subsample of team conversations (e.g., ~100 chats).
We use those 100 chats to sanity check / evaluate how well the proxies perform against human judgment.

In effect, I'm looking for some way to create "Gold" labels so that we can sanity check that the features we are extracting make sense and cohere with the measures from behavioral science that they are meant to approximate. My proposal is to leverage a pipeline that is similar to what we have already built for Task Mapping, but to do so for the behavioral features that we extracted in the Process Mapping process. The proposal is to do this on only a very small subset of the conversations, primarily for validating our computational measures.
Of course, one objection is that the human labels from Turk still won't perfectly match the original measures from behavioral science. After all, in the original psychology papers, many of the features we extracted were measured via self-report surveys; e.g., people evaluated their own subjective feelings. Here, the best we can do is to ask other people to read the chats and make a judgment.
However, the hope is that we can use these labels as a sanity check --- as good of a sanity check as we can get, anyway --- to confirm that our features are reasonable proxies for the behavioral constructs they are intended to measure.

Very cool!!

Do the features have a score for every team member or is it one score for the whole conversation? I can imagine one member may feel differently about turn-taking or positivity than another in the same conversation. How is that reconciled in the feature score? One person may feel positivity, but the models say it wasn't.
^Maybe not helpful, just a thought I had when reading :D

Notes from Lab Meeting:

What if humans are not good raters --- and this is not a good gold standard?
This is basically the construct validity problem in psychology --- see Psychometric: An Introduction (Furr & Bacharach)
One check: if you have 2 measures, look and see how correlated they are (e.g., correlation is 0.9, so feels pretty good that they are capturing the same thing)
If they are not correlated, then perhaps ask people to rank the same examples in terms of positivity, and see which one is more correlated in terms of human ratings.

Ch 8-9 could help at least understand how this is traditionally tackled.

Duncan suggests:

You get two measures (e.g., Naive Bayes and BERT); check that they're highly correlated --- if they are correlated, then there is no problem
If they're not highly correlated, throw both into the model, and see if one is more predictive than the other, and then use that --- you can also say, 'they are capturing different elements of the same thing'

James: Do people care about an ML measure of positivity, or whether you surveyed them --- do people leave the discussion having a positive experience?
Linnea: This feels a bit unsolveable, kind of like any researcher DF: maybe the answer is you never will get a perfect measure, so make a decision, make it transparent and admit the limitations, and then people can critique and help improve it.
James: If you have an outcome that you care about (task performance) and some intermediate outcomes (positivity, turn taking) and some interventions (communication skill training) then the engineer/manager just cares about the relationship between the intervention and the outcome. You might care about the intermediate outcomes if you have some other intervention that works on those intermediating variables that you could choose to draw on
In that case, you’d want to use whatever intermediating measures you used to measure these extra interventions...
Duncan: Thinks that the main contribution is not about the goodness of the 'metrics' -- it's not about psychometrics or ML

Main contribution is to integrative experiments
To the extent that we can find measures that are already validated in the literature, then it's fine to use those
And if there are 2 or 3 that are equally validated, and they yield uncorrelated rankings, toss them all in

Duncan: What keeps us honest is out-of-sample prediction. And if you had a better proxy, maybe your predictions could have gotten better, then your model could get more predictive.

We can step around some of these objections by saying, 'you know, at the end of the day, we are forcing our model to make predictions on new data, and we can quantify how well it does'

Linnea: Ben Lira might have an idea or two
(Emily I think he was in Uri's class with us last fall)

@shapeseas we calculate features at 2 levels --- 1) per chat; and 2) per team member, and then aggregated at the conversation level.

15:18:51 From Mark Whiting to Everyone:
	https://github.com/orgs/Watts-Lab/projects/8/views/1
15:32:58 From Linnea Gandhi to Everyone:
	Could results just trigger IFF real? Or is the staggered timeline the problem? (Sorry if I missed a tech detail)
15:33:23 From Emily Hu to Everyone:
	Can we not just run an experiment where we recruit reviewers into an experiment instead of doing a field study
15:33:46 From Emily Hu to Everyone:
	does it have to be an audit study?
15:34:54 From Linnea Gandhi to Everyone:
	you give a continuous score, standardize by reviewer, and the top X get in
15:35:35 From Linnea Gandhi to Everyone:
	or a two-stage process -- you do the ratings, then submit, then chatGPT dropped, you are shown your ratings of the real ones again and re-vote on action
15:35:54 From Linnea Gandhi to Everyone:
	I love how we academics are all in on experimenting on others but nothing that impacts our own consequences :-)
15:36:03 From Linnea Gandhi to Everyone:
	This is why corporations don't experiment.
15:37:53 From Linnea Gandhi to Everyone:
	Reacted to "Screenshot2023_02_16_153657.jpg" with ❗
15:37:56 From Mark Whiting to Everyone:
	Accept!
15:42:18 From Linnea Gandhi to Everyone:
	HAHA the problem with like ALL psychology. Proxies for our brains.
15:42:44 From Mark Whiting to Everyone:
	Reacted to "HAHA the problem wit..." with 👍
15:43:06 From Linnea Gandhi to Everyone:
	A good book: Psychometric: An Introduction (Furr & Bacharach)
15:43:29 From Linnea Gandhi to Everyone:
	Ch 8-9 could help at least understand how this is traditionally tackled.
15:46:52 From Linnea Gandhi to Everyone:
	WWJD
15:46:57 From Linnea Gandhi to Everyone:
	What would James do (in this situation)
15:47:47 From James Houghton to Everyone:
	Don’t give me too much credit
15:47:57 From Linnea Gandhi to Everyone:
	Reacted to "Don’t give me too mu..." with 💳
15:48:09 From Linnea Gandhi to Everyone:
	Reacted to "Don’t give me too mu..." with 🍰
15:49:35 From Linnea Gandhi to Everyone:
	Ben Lira might have an idea or two
15:49:47 From Linnea Gandhi to Everyone:
	(Emily I think he was in Uri's class with us last fall)
15:50:09 From Mark Whiting to Everyone:
	Reacted to "Don’t give me too mu..." with 🍰
15:53:36 From Linnea Gandhi to Everyone:
	This feels a bit unsolveable, kind of like any researcher DF: maybe the answer is you never will get a perfect measure, so make a decision, make it transparent and admit the limitations, and then people can critique and help improve it.
15:53:58 From Mark Whiting to Everyone:
	Reacted to "This feels a bit uns..." with 👍
15:54:23 From James Houghton to Everyone:
	If you have an outcome that you care about (task performance) and some intermediate outcomes (positivity, turn taking) and some interventions (communication skill training) then the engineer/manager just cares about the relationship between the intervention and the outcome. You might care about the intermediate outcomes if you have some other intervention that works on those intermediating variables that you could choose to draw on
15:55:15 From James Houghton to Everyone:
	In that case, you’d want to use whatever intermediating measures you used to measure these extra interventions...
15:56:28 From Linnea Gandhi to Everyone:
	(Sorry dogs dissected a toy - brb)
16:03:08 From Linnea Gandhi to Everyone:
	"nobody got fired for hiring mckinsey"
16:03:15 From James Houghton to Everyone:
	I thought it was IBM?
16:03:35 From Linnea Gandhi to Everyone:
	haha probably both
16:03:45 From Linnea Gandhi to Everyone:
	we always said mckinsey bc we were competitors :-0
16:04:06 From Linnea Gandhi to Everyone:
	"nobody got fired for citing something with 100 cites"???
16:05:21 From James Houghton to Everyone:
	My adage: All academic disagreements boil down to ambiguity in the research question…
16:05:30 From James Houghton to Everyone:
	=)
16:07:01 From Linnea Gandhi to Everyone:
	Reacted to "=)" with 👍
16:08:47 From Linnea Gandhi to Everyone:
	Mark's comment makes me think of "Policy Prediction Problems" from Sendhil
16:09:00 From Linnea Gandhi to Everyone:
	I don't need to know why its raining but just to bring an umbrella
16:09:59 From James Houghton to Everyone:
	Good enough is better than most?
16:10:47 From Emma Arsekin to Everyone:
	I have to run to another call, but thanks everyone!
16:12:05 From<EMAIL_ADDRESS>to Everyone:
	@Mark can you download the chat? Maybe a helpful esource for Emily / we can upload to the github issue as part of the gut check (if everyone is okay with it)
16:12:56 From Mark Whiting to Everyone:
	Reacted to "@Mark can you downlo..." with 🍸

Closing as this is about a previous version of the project and no longer related to the toolkit


Ensemble percentiles as dim

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #462

[x] Tests for the changes have been added (for bug fixes / features)
[x] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?
Changes the behaviour of ensembles.ensemble_percentiles to concatenate the percentiles along a percentiles dimension by default. The old behaviour can be obtained by specifying split=True.

Also, the method now accepts DataArrays. (In fact when passing a dataset, it simply loops on the variables with realization as a dim.)

Does this PR introduce a breaking change?
Yes!

Other information:

Pull Request Test Coverage Report for Build 1937

24 of 24 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 77.441%

Totals

Change from base Build 1936:
0.06%

Covered Lines:
2657

Relevant Lines:
3431

💛  - Coveralls


MySQL: There is no (longer a?) 6 GB memory option

Describe the bug
The MySQL workspace service template defines four SKUs: 2, 4, 6, and 8 CPUs. This is mapped to GP_Gen5_X in TF, where X is the number of cores. However, there is no SKU GP_Gen5_6 (or at least not anymore). The valid SKUs for a General Purpose Gen 5 MySQL single server are GP_Gen5_2, GP_Gen5_4, GP_Gen5_8, GP_Gen5_16, GP_Gen5_32, and GP_Gen5_64.
Ref: https://learn.microsoft.com/azure/mysql/single-server/concepts-pricing-tiers
Steps to reproduce

Attempt to deploy a GP | 5GB 6vCores SKU from TRE.

Deployment fails with
Error message: expected sku_name to be one of [B_Gen4_1 B_Gen4_2 B_Gen5_1 B_Gen5_2 GP_Gen4_2 GP_Gen4_4 GP_Gen4_8 GP_Gen4_16 GP_Gen4_32 GP_Gen5_2 GP_Gen5_4 GP_Gen5_8 GP_Gen5_16 GP_Gen5_32 GP_Gen5_64 MO_Gen5_2 MO_Gen5_4 MO_Gen5_8 MO_Gen5_16 MO_Gen5_32], got GP_Gen5_6

Azure TRE release version (e.g. v0.14.0 or main): v0.15.2

Hi @SvenAelterman this has been fixed with the release of v0.17.0 with transition to the flexible server resource.
sql_sku = {
    "B | 4GB 2vCores"   = { value = "B_Standard_B2s" },
    "GP | 8GB 2vCores"  = { value = "GP_Standard_D2ds_v4" },
    "BC | 16GB 2vCores" = { value = "MO_Standard_E2ds_v4" }
  }

@SvenAelterman is this good to be closed?

@tim-allen-ck I will be upgrading my TRE to 0.17.0 sometime today probably, I will test again then.

Closing Issue


Added the "not applicable" market sector option to CMA case schema

The Competition and Markets authority have recently started including Office for the Internal Market projects and Subsidy Advice Unit referrals in their CMA case specialist finder. However, the market sector field in the CMA case data type does not apply to these new types. Therefore, we are adding a new "not applicable" option to the CMA case market sector field.
Trello card: https://trello.com/c/SdjSO9PB

Looks good, this will need the same changes made in publishing-api and potentially search-api as well :)

I've already applied to publishing API. Will look into search, thanks for the heads up


Volume Up/Down Graphic Toggle

Checklist

[x] I have searched for existing issues

Is your feature request related to a problem? Please describe.
I have an LG 32UL950 monitor that works great with MonitorControl, but the volume graphic included with MonitorControl overlaps the native monitor volume control that pops up when volume is changed with the volume keys.
Describe the solution you'd like
It would be great to have a simple toggle in the preferences to disable the volume up/down graphics in MonitorControl.
Describe alternatives you've considered
I tried to find ways to disable the native volume graphic, but there isn't a way to disable it (and I'm sure many other monitors are similar).

This function will be added in 3.0.0. :)
Since this is a duplicate of this https://github.com/MonitorControl/MonitorControl/issues/480 (although your request is the older one, sorry) - I'll close this issue, but you can keep track and add a reply there. Thanks!


PEP 8 stylistic cleanup

Consider running flake8 against the code to improve readability and identify issues with missing and unused imports. flake8 identifies PEP 8 stylistic issues.
This is low priority, but something to consider for long-term code maintainability and readability.
I made a first attempt at reducing issues identified by flake8 in the main modules; see https://github.com/apthorpe/HARK/tree/master/HARK This isn't meant as a pull request as much as gauging interest in the stylistic cleanup effort.
FWIW, I was introduced to HARK at SciPy 2018 and thought I might contribute some effort toward software engineering tasks (testing, packaging, code review, Python 2/3 compatibility & conversion). I typically start with flake8 style cleanup because stylistic modifications shouldn't change the code functionality and it gives me an opportunity to read  through the code.

@apthorpe Thanks for the suggestion, and for your interest in helping!
I'd be interested in using flake8 or black or a similar tool to improve our formatting, and use automated testing to lock in the codebase against future linter errors. @mgerring @mnwhite @npalmer-professional do you have any preferences here? I suggest we go with black to favor decisiveness. :)

@brainwane I'm generally in favor!  However important caveat: in the past some code style decisions were made as compromises to make it easier for economists to follow some of the complicated math more easily.  That part is pretty vital, since the heavy-duty contributors will largely be economists/other researchers working on the complicated math parts of the code.
As with many things I think the answer will be "let's run both in different forks and eyeball the outputs." Ideally all the suggestions will not interrupt math-style-reading!
@brainwane what would it take to do what @apthorpe did, but with black?  I say we do that, then ping @mnwhite and @llorracc and see if we can get a quorum on one or the other.

I was not aware of black; I've been looking for a tool like that for
years. I'll start familiarizing myself with it ASAP.
Once there's a decsion made, I'm still willing to create a branch, do the
scut work, and submit a PR.
On Fri, Jul 13, 2018 at 4:51 PM npalmer-professional <
<EMAIL_ADDRESS>wrote:

@brainwane https://github.com/brainwane I'm generally in favor! However
important caveat: in the past some code style decisions were made as
compromises to make it easier for economists to follow some of the
complicated math more easily. That part is pretty vital, since the
heavy-duty contributors will largely be economists/other researchers
working on the complicated math parts of the code.
As with many things I think the answer will be "let's run both in
different forks and eyeball the outputs." Ideally all the suggestions will
not interrupt math-style-reading!
@brainwane https://github.com/brainwane what would it take to do what
@apthorpe https://github.com/apthorpe did, but with black? I say we do
that, then ping @mnwhite https://github.com/mnwhite and @llorracc
https://github.com/llorracc and see if we can get a quorum on one or
the other.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/171#issuecomment-404963225, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABD3DeSEJSYjFHs_tmAjinFZV9fdtP12ks5uGRZugaJpZM4VPiGy
.

Yes, I'm in favor of style cleanup. We tried to be consistent with variable and function naming standards, and have a naming style guide at www.github.com/econ-ark/NARK ... It hasn't been touched in two years, and I don't think everything we do is consistent with it.
I swear there is a consistent naming convention in HARK, but some of it is merely my personal headcanon.

Also: Some very strong words are used in the NARK, like "PROHIBITED".  This is obviously not the case.

athorpe, thanks for your help!
Not only am I in favor of style improvements, I'm in favor of having a policy about style, which is publicly posted (so that other people can help us abide by that style).
Matt pointed you to the NARK document, but that is more for economists defining naming conventions for commonly used variables in our models.  We do not have a well-defined set of guidelines for code (except that variable names should be consistent with the guidelines in the NARK).
If you could help us define a style (maybe just by proposing that "econ-ark should post a link saying that its preferred style is [x] which will be enforced by [tool y]", then help update our code to that style, it would be even better than just suggesting specific code changes flagged by such a tool.

@apthorpe thank you for the thorough response!
As you have perhaps gathered, we're in the midst of a few different overhauls with Econ-ARK, such as the Python 3 support we just landed. It would be great for you to join us in our Zulip asynchronous chat https://chat.opentechstrategies.com/#narrow/stream/16-Econ-ARK (I don't have your email address, otherwise I would create an account for you and send you an invite; feel free to create an account and join in the discussion).
Right now I think flake8 is a better match for what we're doing because I see that black says it's not yet production ready, and it sounds like there are some outstanding questions they need to resolve.
I think a good way to start would be to create two different diffs against HARK/core.py, so we can get a feel for what flake8 says needs fixing. One diff would be a minimal change to clean up only the most egregious problems that make the codebase actively hard to work with, and the other would use flake8's full PEP 8 compliance toolset to make a fully compliant file. What do you think?


keptn cli doesn't create projects or services

Your issue may already be reported! Please search on the issue tracker before creating a new one.
Environment

Client OS (e.g., Linux, macOS, Windows): macos
Keptn Version (keptn version): 0.11.2
Kubernetes Cloud Provider (e.g., GKE, AKS): EKS
Kubernetes version (kubectl version): v1.21.2-eks-06eac09
--

Affected Component

[ ] Approval
[X] Bridge
[ ] CLI
[ ] Datastore
[ ] Docs
[ ] Distributor / Event Broker
[ ] Helm
[ ] Istio
[ ] Jmeter
[ ] Kubernetes Integration
[ ] Openshift Integration
[ ] REST API
[ ] Webhook

Describe the bug

To Reproduce

Steps to reproduce the behavior:

Create a shipyard file

apiVersion: "spec.keptn.sh/0.2.2"
kind: "Shipyard"
metadata:
  name: "shipyard-krateo"
spec:
  stages:
    - name: "dev"
      sequences:
        - name: "delivery"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "direct"
            - name: "test"
              properties:
                teststrategy: "functional"
            - name: "evaluation"
            - name: "release"
        - name: "delivery-direct"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "direct"
            - name: "release"

    - name: "staging"
      sequences:
        - name: "delivery"
          triggeredOn:
            - event: "dev.delivery.finished"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "blue_green_service"
            - name: "test"
              properties:
                teststrategy: "performance"
            - name: "evaluation"
            - name: "release"
        - name: "rollback"
          triggeredOn:
            - event: "staging.delivery.finished"
              selector:
                match:
                  result: "fail"
          tasks:
            - name: "rollback"
        - name: "delivery-direct"
          triggeredOn:
            - event: "dev.delivery-direct.finished"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "direct"
            - name: "release"

    - name: "production"
      sequences:
        - name: "delivery"
          triggeredOn:
            - event: "staging.delivery.finished"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "blue_green_service"
            - name: "release"
        - name: "rollback"
          triggeredOn:
            - event: "production.delivery.finished"
              selector:
                match:
                  result: "fail"
          tasks:
            - name: "rollback"
        - name: "delivery-direct"
          triggeredOn:
            - event: "staging.delivery-direct.finished"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "direct"
            - name: "release"

        - name: "remediation"
          triggeredOn:
            - event: "production.remediation.finished"
              selector:
                match:
                  evaluation.result: "fail"
          tasks:
            - name: "get-action"
            - name: "action"
            - name: "evaluation"
              triggeredAfter: "2m"
              properties:
                timeframe: "2m"

Run this command
keptn create project krateo --shipyard=./shipyard.yaml
This is the output

WARNING: Creating a project without Git upstream repository is not recommended.
You can configure a Git upstream repository using:

keptn update project PROJECTNAME --git-user=GIT_USER --git-token=GIT_TOKEN --git-remote-url=GIT_REMOTE_URL

Starting to create project
Project created successfully

Project is not created.
If you upload the shipyard file from the WebUI it works correctly.
No error logs on configuration-service or shipyard-controller.
After the project is successfully created from the WebUI, run this command

keptn create service demo --project=krateo

This is the output

Starting to create service
Create service was unsuccessful
Error: Create service was unsuccessful. invalid character 'p' after top-level value
-----DETAILS-----404 page not found

FWIW it might be similar to https://github.com/keptn/keptn.github.io/issues/984 . In this issue a space inside the SLI expression led to a broken Prometheus configuration file: https://github.com/keptn/examples/blob/4dcf77e307e62b07c9c4bd16572650803cd38c4f/quickstart/demo/slo.yaml#L28-L32 . Since the YAML generation in Keptn is unified, I suspect a systemic issue under the hood
@maurosala Any chance you could extract the configuration file from the POD

Hi @oleg-nenashev, I have found the problem.
Our keptn bridge is behind cloudflare proxy.
There are two possibilities in cloudflare (as you can see here)

If I enable the proxy keptn client does not work, but if I disable it and expose the bridge directly all seems to work.

Thanks for the update! This error message is weird anyway:
Starting to create service
Create service was unsuccessful
Error: Create service was unsuccessful. invalid character 'p' after top-level value
-----DETAILS-----404 page not found

Hi @maurosala, I am glad that you found out about the root cause of the problem. I will close this issue and open a new ticket to provide the possibility to connect to a Keptn installation via a proxy server.


Tabbed groups "optional arguments" tab not translated

When using tabbed groups in Gooey 1.0.6, the tab title for "Optional Arguments" is shown as:

This appears to be the placeholder string prior to i18n translation.

Closing (fixed by you!)


SPFx project upgrade 1.7.1 to 1.8.2 doesn't suggest react type resolution update

Running the project upgrade command on a 1.7.1 project to get 1.8.2 doesn't suggest an update to the resolutions section of package.json.
Package.json contains:
  "resolutions": {
    "@types/react": "16.4.2"
  },

Command output:
o365$ spfx project upgrade
Execute in command line
-----------------------
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-SE
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-DE
npm dedupe

./.yo-rc.json
-------------
Update version in .yo-rc.json:
{
  "@microsoft/generator-sharepoint": {
    "version": "1.8.2"
  }
}

./tsconfig.json
---------------
Update tsconfig.json extends property:
{
  "extends"<EMAIL_ADDRESS>}

Update tsconfig.json inlineSources value:
{
  "compilerOptions": {
    "inlineSources": false
  }
}

Update tsconfig.json strictNullChecks value:
{
  "compilerOptions": {
    "strictNullChecks": false
  }
}

Update tsconfig.json noUnusedLocals value:
{
  "compilerOptions": {
    "noUnusedLocals": false
  }
}

I expected a suggestion to update package.json to:
  "resolutions": {
    "@types/react": "16.7.22"
  }

Thanks for reporting the issue and the repro steps. I'll have a look if I can reproduce the issue and get back to you as soon as I know more.

I've just tried running the upgrade command on a React web part built using v1.7.1 and I'm getting the recommendation as expected. Could you please try again on a new project so that we can see if it's working there and see if there is anything specific about your other project that cause this command to work incorrectly?

I reinstalled SPFx 1.7.1, created a new project with all the defaults (except that I selected React, of course). This is the output from the spfx project upgrade command:
Execute in command line
-----------------------
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-SE
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-DE
npm dedupe

./.yo-rc.json
-------------
Update version in .yo-rc.json:
{
  "@microsoft/generator-sharepoint": {
    "version": "1.8.2"
  }
}

./tsconfig.json
---------------
Update tsconfig.json extends property:
{
  "extends"<EMAIL_ADDRESS>}

Update tsconfig.json inlineSources value:
{
  "compilerOptions": {
    "inlineSources": false
  }
}

Update tsconfig.json strictNullChecks value:
{
  "compilerOptions": {
    "strictNullChecks": false
  }
}

Update tsconfig.json noUnusedLocals value:
{
  "compilerOptions": {
    "noUnusedLocals": false
  }
}

src\webparts\helloWorld\HelloWorldWebPart.manifest.json
-------------------------------------------------------
Update the supportedHosts property in the manifest:
{
  "supportedHosts": ["SharePointWebPart"]
}

src\webparts\helloWorld\HelloWorldWebPart.ts
--------------------------------------------
Refactor the code to import property pane property from the @microsoft/sp-property-pane npm package instead of the @microsoft/sp-webpart-base package:
import { BaseClientSideWebPart } from "@microsoft/sp-webpart-base";
import { IPropertyPaneConfiguration, PropertyPaneTextField } from "@microsoft/sp-property-pane";

I'm executing on Windows, that might be the issue ;)
I'll go check on macOS, but it'll take some time.

Output on macOS on a newly created project:
o365$ spfx project upgrade
Execute in command line
-----------------------
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-SE
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-DE
npm dedupe

./.yo-rc.json
-------------
Update version in .yo-rc.json:
{
  "@microsoft/generator-sharepoint": {
    "version": "1.8.2"
  }
}

./tsconfig.json
---------------
Update tsconfig.json extends property:
{
  "extends"<EMAIL_ADDRESS>}

Update tsconfig.json inlineSources value:
{
  "compilerOptions": {
    "inlineSources": false
  }
}

Update tsconfig.json strictNullChecks value:
{
  "compilerOptions": {
    "strictNullChecks": false
  }
}

Update tsconfig.json noUnusedLocals value:
{
  "compilerOptions": {
    "noUnusedLocals": false
  }
}

src/webparts/helloWorld/HelloWorldWebPart.manifest.json
-------------------------------------------------------
Update the supportedHosts property in the manifest:
{
  "supportedHosts": ["SharePointWebPart"]
}

src/webparts/helloWorld/HelloWorldWebPart.ts
--------------------------------------------
Refactor the code to import property pane property from the @microsoft/sp-property-pane npm package instead of the @microsoft/sp-webpart-base package:
import { BaseClientSideWebPart } from "@microsoft/sp-webpart-base";
import { IPropertyPaneConfiguration, PropertyPaneTextField } from "@microsoft/sp-property-pane";

I can reproduce the issue. Let me investigate it further and see what's wrong. Thanks for reporting!

Fix for this bug is available in v1.20.0 which should be available in the next few mins


Feat/any collection

rename existing Collection base class as CollectionBase
Create API for collection: registering new type of collection can be done in src/ansys/dpf/core/__init__.py using _CollectionFactory.
Internal implementation uses AnyCollection
Add API to create/cast any from AnyCollection and CustomTypeField

Codecov Report
Attention: Patch coverage is 91.79331% with 27 lines in your changes are missing coverage. Please review.

Project coverage is 86.82%. Comparing base (a2d17c3) to head (0c51621).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1461      +/-   ##
==========================================
+ Coverage   86.71%   86.82%   +0.11%
==========================================
  Files          81       82       +1
  Lines        9565     9617      +52
==========================================
+ Hits         8294     8350      +56
+ Misses       1271     1267       -4

Hey @cbellot000, could you please provide a description of the changes?

Hey @cbellot000, could you please provide a description of the changes?

yes, it's done

rename existing Collection base class as CollectionBase
Create API for collection: registering new type of collection can be done in src/ansys/dpf/core/__init__.py using _CollectionFactory.
Internal implementation uses AnyCollection
Add API to create/cast any from AnyCollection and CustomTypeField

The rename is not going to be retro-compatible, right? But I guess no-one should be using it anyway. Should we make the CollectionBase class private?


Make IBC middleware to block transfer packets if there is large packet timeout queue

Summary
Suppose chain B is offline. Many users on chain A may be unaware, and keep trying to IBC to chain B. So chain A has a large queue of IBC packets, that under chain A's local validity predicate, should very clearly be timed out. Right now, users on chain A can/will keep on submitting more transfer packets, and keep getting their funds stuck in the channel, irrecoverable until either chain B comes online or the channel expires.
This was a problem when Osmosis was down, several front-ends kept allowing IBC sends, and thus had users funds stuck.
Proposal
I suggest we implement a piece of middleware that sits before the transfer module, which says that "if there is a queue of at least {N} packets that have needed to be timed out for duration {D} under local time conditions, refuse to allow other fund transfers". {N} and {D} should be governance-tunable parameters.
Perhaps such a middleware can have an optional argument provided in the transfer memo to override this.
I recommend this middleware be added by default to IBC, with conservative parameterizations, and then chains can make less conservative parameterizations. Proposed initial parameterization
(e.g. N = 100, D = 12 hours)

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Thanks for suggesting this idea, @ValarDragon, and sorry for the late response. I have one question on the top of my head about how this would work.
Let's assume the following scenario:

We have two chains (A and B).
The latest client/consensus state of chain B that chain A has stored is for height h and timestamp t.
Chain B goes offline at height h' (> h) and timestamp t' (> t).

Packets sent before chain B went offline would have a timeout height h + Δ or timeout timestamp t + Δ, otherwise those packets would have been rejected on sendPacket's checks for timeout height or timeout timestamp.
If chain B goes then offline at height h', but the client/consensus state of chain B is not updated on chain A, how could chain A based on its local validity predicate determine that those packets need to be time out? I mean, if chain A compares the timeout height or timeout timestamp of those packets with the latest height and timestamp it has for chain B, the comparison will still indicate that the packets have not timed out, since chain B is offline and its client/consensus state cannot be updated on chain A...
I guess I could see this working on the situation where chain B doesn't go offline, but no relayers are relaying the packets. But even in that scenario, then the relayers would still need to update the light clients, which would be strange (i.e. they update the light clients but do not relay packets...).
I hope this makes sense; otherwise, if I am missing something in my reasoning, please do let me know!

Hrmm, the idea is that on chain A, we can know:

Chain B's last reported block time is T_B
Chain A's current time is T_A, and T_A > T_B
Chain A has attempted to send at least k packets to B since T_B, 0 of which have had a life cycle completion. (Definitionally)

Say delta_T = T_A - T_B. The proposal is if delta_T > {parameter} and k > {parameter} then mark chain B as offline and dis-allow further sends on the channel


Extend validator for mol data templates

Description
As a developer, I want to have reliable validation for the data templates to avoid validation on loading.
Validation rules: https://www.ebi.ac.uk/seqdb/confluence/display/MouseInformatics/Data+Validation
Acceptance criteria

[x] extend context and syntax validation in mol data templates
[x] extend command line interface

done

this is duplicate Epic of #602


Missing build.sh

Hello
Your installation instructions mention running "build.sh". Should this be present in the repo?

@theburningmonk I'm also curious about this. Cannot follow the instructions without this bash script.

@elpres101 Did you follow these instructions despite the lack of build.sh or find a solution elsewhere?


No way to set index settings on replicas

AFAIK, there is no way to currently set index settings on replicas.
I can add an ScoutIndex for my replica, and call indexSettings on it, and the scout/settings/update command works great.
However, if you then try and sync, you'll get an algolia error, because you aren't allowed to push objects to a replica index.
[2019-11-17 18:00:22] craftcms.ERROR: Algolia\AlgoliaSearch\Exceptions\BadRequestException: cannot apply a add object request on a replica index in /app/vendor/composer/algolia/algoliasearch-client-php/src/RetryStrategy/ApiWrapper.php:210 Stack trace: #0 /app/vendor/composer/algolia/algoliasearch-client-php/src/RetryStrategy/ApiWrapper.php(158): Algolia\AlgoliaSearch\RetryStrategy\ApiWrapper->handleResponse(Object(GuzzleHttp\Psr7\Response), Object(Algolia\AlgoliaSearch\Http\Psr7\Request)) #1 /app/vendor/composer/algolia/algoliasearch-client-php/src/RetryStrategy/ApiWrapper.php(92): Algolia\AlgoliaSearch\RetryStrategy\ApiWrapper->request('POST', '/1/indexes/gear...', Object(Algolia\AlgoliaSearch\RequestOptions\RequestOptions), Array, 30, Array) #2 /app/vendor/composer/algolia/algoliasearch-client-php/src/SearchIndex.php(280): Algolia\AlgoliaSearch\RetryStrategy\ApiWrapper->write('POST', '/1/indexes/gear...', Array, Object(Algolia\AlgoliaSearch\RequestOptions\RequestOptions)) #3 /app/vendor/composer/rias/craft-scout/src/engines/AlgoliaEngine.php(82): Algolia\AlgoliaSearch\SearchIndex->clearObjects() #4 /app/vendor/composer/rias/craft-scout/src/console/controllers/scout/IndexController.php(37): rias\scout\engines\AlgoliaEngine->flush() #5 /app/vendor/composer/tightenco/collect/src/Collect/Support/Collection.php(475): rias\scout\console\controllers\scout\IndexController->rias\scout\console\controllers\scout\{closure}(Object(rias\scout\engines\AlgoliaEngine), 1) #6 /app/vendor/composer/rias/craft-scout/src/console/controllers/scout/IndexController.php(39): Tightenco\Collect\Support\Collection->each(Object(Closure)) #7 /app/vendor/composer/rias/craft-scout/src/console/controllers/scout/IndexController.php(69): rias\scout\console\controllers\scout\IndexController->actionFlush('') #8 [internal function]: rias\scout\console\controllers\scout\IndexController->actionRefresh('') #9 /app/vendor/composer/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array) #10 /app/vendor/composer/yiisoft/yii2/base/Controller.php(157): yii\base\InlineAction->runWithParams(Array) #11 /app/vendor/composer/yiisoft/yii2/console/Controller.php(164): yii\base\Controller->runAction('', Array) #12 /app/vendor/composer/craftcms/cms/src/console/Controller.php(199): yii\console\Controller->runAction('', Array) #13 /app/vendor/composer/yiisoft/yii2/base/Module.php(528): craft\console\Controller->runAction('', Array) #14 /app/vendor/composer/yiisoft/yii2/console/Application.php(180): yii\base\Module->runAction('scout/index', Array) #15 /app/vendor/composer/craftcms/cms/src/console/Application.php(93): yii\console\Application->runAction('scout/index', Array) #16 /app/vendor/composer/yiisoft/yii2/console/Application.php(147): craft\console\Application->runAction('scout/index', Array) #17 /app/vendor/composer/yiisoft/yii2/base/Application.php(386): yii\console\Application->handleRequest(Object(craft\console\Request)) #18 /app/bin/craft(7): yii\base\Application->run() #19 {main} {"trace":[],"memory":27655616,"category":"Algolia\\AlgoliaSearch\\Exceptions\\BadRequestException","exception":"[object] (Algolia\\AlgoliaSearch\\Exceptions\\BadRequestException(code: 403): cannot apply a add object request on a replica index at /app/vendor/composer/algolia/algoliasearch-client-php/src/RetryStrategy/ApiWrapper.php:210)"} []

I even tried putting in a bogus criteria that would never match anything, but I still got the error:
        ScoutIndex::create('gearByPriceAsc')
            ->criteria(function (EntryQuery $query) {
                return $query->id(false);
            })
            ->indexSettings(
                (clone $baseGearIndexSettings)
                    ->customRanking([
                        'asc(price.min)',
                    ])
            ),

Couple of ideas for a fix:

make ScoutIndex::critiera null by default, and bail on any object pushing
add a ScoutIndex::replica boolean that prevented any object syncing
Expand IndexSettings to accept more than just an array of strings. It could optionally be a nested set of ScoutIndex, whose settings would get synced with the scout/settings/update command. eg:

<?php
return [
  'indices' => [
    ScoutIndex::create('gear')
    ->attributesForFaceting([
      'reviewAverage',
      'price.min',
    ])
    ->indexSettings(
        IndexSettings::create()
        ->replicas([
            ScoutIndex::create('gearByPriceAsc')->indexSettings(IndexSettings::create()->customRanking(['asc(price.min)'])),
            ScoutIndex::create('gearByPriceDesc')->indexSettings(IndexSettings::create()->customRanking(['desc(price.min)'])),
            ScoutIndex::create('gearByReviewRatingAsc')->indexSettings(IndexSettings::create()->customRanking(['asc(reviewRating.min)'])),
            ScoutIndex::create('gearByReviewRatingDesc')->indexSettings(IndexSettings::create()->customRanking(['desc(reviewRating.min)'])),
        ])
    ),
  ]
];

The latter diverges the most from the Algolia Index setSettings API, but is probably the most useful for this use-case.
Let me know what you think and I may have time for a PR.
FWIW - I'm currently hacking around this by only adding my replica indices with a condition:
if (Craft::$app->request->getIsConsoleRequest() &&
    in_array('scout/settings/update', Craft::$app->request->params)) {

I think you're one of the few that's actually using this functionality, so to be honest I'll leave it up to you to decide what you think is the best solution.
I like the idea of a ->replicas function on the indexSettings, that could encapsulate the logic for updating those nicely as well.
Would love a PR for this, make sure to add a test for it as well then.

I like the idea of a ->replicas function on the indexSettings, that could encapsulate the logic for updating those nicely as well.

It shall be done!

There was an error in the forwarding to replicas just fixed by @jalendport, but this feature can still be useful for setting distinct settings for each replica

Curious, is this still in development or has it been released?

@santi6291 I'm hoping to have a PR in the next week.

Any updates?

hey looks its @rsanchez!
Perhaps that will inspire me to make good on my PR promise…thanks for the nudge.

👀
any update on this? Definitely have a need on my current project.

Thanks for the nudges…and sorry for the delays.
Up and had a baby and got a bit behind. 👶
Still on my list, and I'm looking at it tonight!

Dang babies, always getting in the way of everything 😂

Oh, and I forgot to say, let me know if I can help at all with testing.

Just wanted to bump this one!
Our workaround:

Define indexSettings() for each replica index in the indices config
Comment them out whenever you're not running ./craft scout/settings/update

We would also love to see this fixed. Happy to take a shot at a PR if you're open to it

Hey @tomdavies, happy to review & test a PR if you'd like to get this done. Feel free to submit one and/or ping me on Discord if you'd like to discuss further.

@janhenckens I think this can be closed now that #275 is merged


Streamalert deployment; terraform init issue

Initializing the backend...
Backend configuration changed!
Terraform has detected that the configuration specified for the backend
has changed. Terraform will now check for existing state in the backends.
Terraform detected that the backend type changed from "local" to "s3".
Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
[INFO 2019-08-11 23:44:18,106 (stream_alert_cli.terraform.handlers:94)]: Deploying Lambda Functions
[INFO 2019-08-11 23:44:18,107 (stream_alert_cli.manage_lambda.deploy:80)]: Deploying: alert alert_merger athena classifier rule
[INFO 2019-08-11 23:44:18,107 (stream_alert_cli.manage_lambda.package:68)]: Creating package for rules_engine
[INFO 2019-08-11 23:44:18,152 (stream_alert_cli.manage_lambda.package:178)]: Installing libraries: pathlib2, policyuniverse, policyuniverse==<IP_ADDRESS>, backoff==1.7.0, netaddr==0.7.19, boto3==1.9.50
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
ERROR: Double requirement given: policyuniverse==<IP_ADDRESS> (already in policyuniverse, name='policyuniverse')
[ERROR 2019-08-11 23:44:18,939 (stream_alert_cli.helpers:68)]: An error occurred while running: pip install pathlib2 policyuniverse policyuniverse==<IP_ADDRESS> backoff==1.7.0 netaddr==0.7.19 boto3==1.9.50 --upgrade --target /tmp/rules_engine
['pip', 'install', u'pathlib2', u'policyuniverse', 'policyuniverse==<IP_ADDRESS>', 'backoff==1.7.0', 'netaddr==0.7.19', 'boto3==1.9.50', '--upgrade', '--target', '/tmp/rules_engine']
[ERROR 2019-08-11 23:44:18,939 (stream_alert_cli.manage_lambda.package:77)]: Failed to install necessary libraries
None

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
ERROR: Double requirement given: policyuniverse==<IP_ADDRESS> (already in policyuniverse, name='policyuniverse')

Hi, not a stream alert maintainer or associated with AirBNB but would like to say sorry for this.
I surfaced this issue in https://github.com/airbnb/streamalert/pull/962. you can resolve by manually removing this line. I will PR a fix.
Also please note that StreamAlert advises using the stable tag in their documentation to avoid these issues.

thanks @gavinelder! yes, @cninja1 please follow gavin's advice :)

@gavinelder @ryandeivert Thank you for your time, Will test that out.

@gavinelder any word on a PR to fix this?


Regarding ESP8266WiFi.h

Greetings,
On Arduino version 1.6.9, I manage to install ModbusIP library and compile provided examples.
I would like to implement modbus_esp8266.
Unfortunately I have faced some issues.
When I try installing modbus-esp8266 via >Sketch>Include Library>add. ZIP library, Arduino ide complains with the followings:
Arduino: 1.6.9 (Windows 7), Board: "NodeMCU 1.0 (ESP-12E Module), 80 MHz, 115200, 4M (3M SPIFFS)"
Specified folder/zip file does not contain a valid library

What can be possible reason of this error message?
Regards,

Hi,Copy ModBus and ModbusIP_ESP8266  folders to library Folder of Arduino IDE


Is there any "waitForTapable" analog but for element's visibility?

driver's methods for visibility are not working for me, as I understand that's because of flutter app's element nature and I need to implement something like waitForVisibility, can I do it somehow ?

Afaik, no, since https://api.flutter.dev/flutter/flutter_driver/flutter_driver-library.html (this driver's dependent lib) does not provide such functionality. So far, tappable or just wait for (if an element exists) is what can do in the FLUTTER context.