python310Packages.snowflake-connector-python: 2.7.7 -> 2.7.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.snowflake-connector-python is: "Snowflake Connector for Python"
meta.homepage for python310Packages.snowflake-connector-python is: "https://www.snowflake.com/"
meta.changelog for python310Packages.snowflake-connector-python is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 2.7.8 with grep in /nix/store/kqg8xmw9iv2xdpz5anbj6mskz4c00lv5-python3.10-snowflake-connector-python-2.7.8
found 2.7.8 in filename of file in /nix/store/kqg8xmw9iv2xdpz5anbj6mskz4c00lv5-python3.10-snowflake-connector-python-2.7.8

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
python310Packages.snowflake-connector-python
python310Packages.snowflake-sqlalchemy
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kqg8xmw9iv2xdpz5anbj6mskz4c00lv5-python3.10-snowflake-connector-python-2.7.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.snowflake-connector-python https://github.com/r-ryantm/nixpkgs/archive/01e74c5aca70f9b531e16d64d2ba242149b80672.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kqg8xmw9iv2xdpz5anbj6mskz4c00lv5-python3.10-snowflake-connector-python-2.7.8
ls -la /nix/store/kqg8xmw9iv2xdpz5anbj6mskz4c00lv5-python3.10-snowflake-connector-python-2.7.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

python310Packages.snowflake-connector-python
python310Packages.snowflake-sqlalchemy
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy

Maintainer pings

Result of nixpkgs-review pr 174908 run on x86_64-linux 1

4 packages built:

python310Packages.snowflake-connector-python
python310Packages.snowflake-sqlalchemy
python39Packages.snowflake-connector-python
python39Packages.snowflake-sqlalchemy


After 2022.8 faith_pd_vector.qza comes with a #SampleID index/column name

After 2022.8 I noticed that the table output of core-metrics' faith_pd_vector.qza has a #SampleID as its first column name, while the other vectors continue to have a blank column/index name. Not an issue within the Q2 environment but it does break some external pipelines, for example if you are importing into R expecting them all to be similar in structure.

Thanks @mestaki, that's super strange, we'll need to reproduce this on our end, as it doesn't really make sense that this would happen.

Oh, it may be the unifrac package adding this actually.

I think you may be right, I vaguely remember arriving at the same conclusion, I think default unifrac changed at that release to the faster one?

Hi @mestaki! Thanks for reporting this - I was able to reproduce on my end using 2023.7. This will be a 'good first issue' candidate for a new RSE1 we have joining the team in a few weeks, so I'm going to add some additional details below for their troubleshooting.
Steps to reproduce this issue:

Install/activate a QIIME 2 environment that is >2022.8 (I used 2023.7)
Grab sample metadata and feature table/rooted tree artifacts from the Moving Pictures tutorial.
Run qiime diversity-lib faith-pd using the feature table and rooted tree artifacts.
Unzip the resultant artifact, and open the alpha-diversity.tsv file within the data directory.

The #SampleID value will be present as the column name above the sample IDs in this table.
Another way to reproduce this issue would be to run qiime diversity core-metrics-phylogenetic using the metadata and artifacts listed above, and then unzipping the faith-pd artifact that is one of the outputs from running this pipeline. The results will be the same, since this is using the same underlying method.
The #SampleID value should be removed, so that there is no column header for the sample IDs.

Adding this back to Triage so It doesn't get lost because a user noticed on the forum today. Forum ref

I just ran into this too

This is perfect for a Good First Issue if we are doing those

Turns out this one is a bit trickier than we initially anticipated - notes from an old pairing session can be found on this branch for reference. We will address this when @cherman2 and I are back from Europe!

We will address this issue in our next release, so I am moving this to our 2024.10 release project board.

This has been fixed, thanks @mestaki for reporting! If you need the updated functionality prior to our next release (2024.10) you can install a development environment once this weekend's new environment files are built.


Include the cores from terminator2k2 separately

Since it's rather unlikely that the changes that terminator2k2 did will be streamlined into the cores he forked it from I would love for terminator2k2's forked cores of SNES and Neo Geo to be included separately (with their own core info json) into the updater.
I already did this with his SNES core fork of agg23 in the past but since he now also released a Neo Geo fork, I thought this would make sense for the auto-updaters.
His GitHub is here: https://github.com/terminator2k2 (@terminator2k2)
A little bit of context:
YouTube Pixel Cherry Ninja brought to my attention that terminator2k2 forked Adam's SNES core and applied some fixes on top of it, especially for certain rom hacks to be playable on the Analogue Pocket. Since by default those are to be copied and overwritten over the core from Adam, those fixes would basically be reverted with each new update from Adam (and it's likely that Adam won't include them). Therefore it should be kept as a separate core imho. Same applies to his newly released Neo Geo core fork which enables three additional games to be compatible.

if he wants them included, cores can be submitted to the inventory here: https://github.com/openfpga-cores-inventory/analogue-pocket/issues/new/choose
this is what the updaters pull their lists from

but in order for these to work he needs to actually build his own releases
they can't be "agg23.SNES" etc anymore

probably should be brought up in issues on t2k2's repos, if you want to get his stuff on there

im hoping these commits make there way into the official repo's soon, so ill leave as is for now


Concert usage Issues in slow network environment

Tested with 0.5sec latency robot.

[x] Pending -> Uninvited(https://github.com/robotics-in-concert/rocon_concert/issues/299, https://github.com/robotics-in-concert/rocon_concert/issues/302)
[x] Joinging -> Invited(https://github.com/robotics-in-concert/rocon_concert/issues/299, https://github.com/robotics-in-concert/rocon_concert/issues/302)
[x] Client cannot connect to hub (https://github.com/robotics-in-concert/rocon_multimaster/blob/indigo/rocon_hub_client/src/rocon_hub_client/hub_client.py#L92) (https://github.com/robotics-in-concert/rocon_multimaster/commit/e025d91da8725dcd59cb13728ea9b77f98843f76)
[ ] Adding flip rules before removing previous flip rules (https://github.com/robotics-in-concert/rocon_multimaster/issues/299)
[ ]  Release issue requested resource by scheduler because of watchdog timeout in slow network

https://github.com/robotics-in-concert/rocon_app_platform/issues/296
https://github.com/robotics-in-concert/rocon_app_platform/issues/297


flush shoud flush delegate?

i think so.when i test TextFileOutput,it can't flush.

:white_check_mark: Build finished in 28m 26s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3682, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Fixed es indexing for hosts with auth

Also, removed using type, and fixed some more es related misc issues.

@bengland2 please review


Python model reports cosmetics

pdstools version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pdstools.

Issue description

Classifier should show the "active range" similar to the R version. This helps identifiying problems with individual models. The cum gains and lift chart should also be using this active range.
X-ticks of classifier should probably be tilted (like the individual binnngs) or just replaced with index (table is available anyways) and layout should autofit - currently cuts off sometimes.
Predictor categories should be propagated and used to highlight/color the various predictor overviews
Predictor Overview should add column with # of responses, as this sometimes varies and when it does, thats interesting info
Predictor Overview should make use of predictor groups and group them, similar to R version
Predictor Binning plots should do auto-layout of y-axis, sometimes cut off or overlapping

Reproducible example
n/a

Expected behavior
at par or better than R version of model reports, we currently still have to pull those for additional info
Installed versions
n/a

I think the Python model reports are now more feature-complete than the R version, so I think we can safely close this issue.
Fyi @yusufuyanik1, it may be worth checking if any of these mentioned issues still persist, but I get the feeling that most of them are covered by now.


function timeouts when following links

Hello,
I've been playing with this trying to get an existing app tested. Right off the bat, I get an error when I try to follow a link as seen below.  Any pointers as to what might be the reason for this to fail?
[17:04:41] Starting 'cucumber'...
.F-

Failures:

1) Scenario: search with valid query shows results # features/demo.feature:6
   ✔ Given I am on the homepage # node_modules/cucumber-mink/src/mink.js:21
   ✖ When I follow "Sobre" # node_modules/cucumber-mink/src/mink.js:21
       Error: function timed out, ensure the promise resolves within 5000 milliseconds
           at Timeout._onTimeout (/Users/paulo/Projects/UX/biscate/biscate.co.mz/node_modules/cucumber/lib/user_code_runner.js:93:22)
           at ontimeout (timers.js:458:11)
           at tryOnTimeout (timers.js:296:5)
           at Timer.listOnTimeout (timers.js:259:5)
   - Then I should see "Maputo" # node_modules/cucumber-mink/src/mink.js:21

1 scenario (1 failed)
3 steps (1 failed, 1 skipped, 1 passed)
0m09.441s
[17:05:17] 'cucumber' errored after 36 s
[17:05:17] Error in plugin "gulp-shell"
Message:
    Command `./node_modules/.bin/cucumber-js` failed with exit code 1

Thanks

Cucumber's setDefaultTimeout can be used.
cucumber.setDefaultTimeout(30 * 1000);

Thanks


MainApplication class

Hi,
Your plugin contain MainApplication class with [Application] attribute.
I want to have my own MainApplication in my application but I cannot do this because an application cannot use more than one class with [Application] attribute.
Is there any way to achieve this?
Regards

Simply merge the two together.
I have minimal code in mine to set the current activity.


Changes needed to train on COCO

To setup and train:
Install required packages into a virtualenv with pipenv
pip install pipenv
pipenv run pip install pip==18.0
pipenv install

Download the COCO data
sh data/scripts/COCO2014.sh

Run the training
pipenv shell  # enters the virtualenv created above
python train.py --dataset COCO --batch_size 10

Thanks, and any idea about how to evaluate trained model on COCO? @davidlmorton

Unfortunately no, sorry.

Hi~how many iterations and how long does it take for you to train on COCO?


Incorrect display of a million

Creating a schema:
type MyCls {
    pair: array<tuple<str, float32> { default := <array<tuple<str, float32>>>[]; }
};

Write code:
insert MyCls {
   pair := [("my_str_1", 1000000), ("my_str_2", 1200000)]
};

select MyCls { * };

Output:
{
  MyCls {
    id: 03d54678-1b6c-11ee-967d-33f758c1f0b6,
    pair: [
      ("my_str_1", 1),
      ("my_str_2", 12)
    ],
  }
}

I see that there are a couple of issues with the code you presented here.
First, the schema should have int64, not int
type MyCls {
    pair: array<tuple<str, int64>> { default := <array<tuple<str, int64>>>[]; }
};

Second, the insert query cannot refer to its own property, that's something you can only do in an update:
insert MyCls {
   pair := [("my_str_1", 1_000_000), ("my_str_2", 1_200_000)]
};

Trying the above schema and the above query produces the correct result (in EdgeDB 3.0):
edgedb> select MyCls { * };
{
  default::MyCls {
    id: e4990598-1b79-11ee-a77e-afec19a4facc,
    pair: [('my_str_1', 1000000), ('my_str_2', 1200000)],
  },
}

So it looks like the original erroneous result was produced in a different and more complex schema and likely a different query. However, it could also be that the original query contained a typo. Can you please confirm whether you can still reproduce the odd result? If it's reproducible, please provide the exact query that reproduces it.

@vpetrovykh Oh, sorry! You are absolutely right on all points. I wanted to simplify the code as much as possible and made errors in the description. Fixed.
Check exactly from the UI. From the CLI works awesome.


You cannot access insightsengineering/teal.devel at host https://github.com

docker run ghcr.io/insightsengineering/rstudio:latest
git clone https://github.com/insightsengineering/teal.code
z <- staged.dependencies::dependency_table()

effect
Copying local dir /home/rstudio/test/teal.data to cache dir /home/rstudio/.staged.dependencies/packages_cache/local_insightsengineering_teal.data_39f26acbb991125a81ff5392c742cf86
clone https://github.com/insightsengineering/teal.code.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.code_f5c7ee90093dd244b11b1acde2d5098a
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.code_f5c7ee90093dd244b11b1acde2d5098a
clone https://github.com/insightsengineering/teal.logger.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.logger_db3be93ac2413ef16521b0cf8fe202ad
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.logger_db3be93ac2413ef16521b0cf8fe202ad
clone https://github.com/insightsengineering/teal.slice.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.slice_69fabf5d920c35ab0e950fac1a49b372
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.slice_69fabf5d920c35ab0e950fac1a49b372
clone https://github.com/insightsengineering/teal.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal_e38093f352c184cf676b1dd47551848c
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal_e38093f352c184cf676b1dd47551848c
clone https://github.com/insightsengineering/teal.modules.general.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.general_6683cd12f2051b8649bc34a3a5b86bd1
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.general_6683cd12f2051b8649bc34a3a5b86bd1
clone https://github.com/insightsengineering/teal.modules.clinical.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.clinical_7480b81982f393c223354b432013836e
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.clinical_7480b81982f393c223354b432013836e
clone https://github.com/insightsengineering/teal.transform.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.transform_7dbb21e492260b8f5bd20354278faa2c
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.transform_7dbb21e492260b8f5bd20354278faa2c
clone https://github.com/insightsengineering/teal.osprey.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.osprey_9d88421efa7fd7b6fcece04c431bbe47
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.osprey_9d88421efa7fd7b6fcece04c431bbe47
clone https://github.com/insightsengineering/teal.modules.hermes.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.hermes_15b1e307810ca8699d3fc80b887a2add
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.hermes_15b1e307810ca8699d3fc80b887a2add
clone https://github.com/insightsengineering/teal.modules.helios.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.modules.helios_737600447efe0473ee9d8c8ca851127e
clone https://github.com/insightsengineering/teal.goshawk.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.goshawk_23d2065f4fbd2bc73b043ff69b62027b
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.goshawk_23d2065f4fbd2bc73b043ff69b62027b
clone https://github.com/insightsengineering/teal.widgets.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.widgets_8f92a3d7b00ae5fadadf0ffc4492c7f2
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.widgets_8f92a3d7b00ae5fadadf0ffc4492c7f2
clone https://github.com/insightsengineering/teal.reporter.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.reporter_2c5a990a10b0c9b8f7bccf13bd04db2a
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.reporter_2c5a990a10b0c9b8f7bccf13bd04db2a
clone https://github.com/insightsengineering/nestcolor.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_nestcolor_2b763bd91b720d7414fc50e163378834
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_nestcolor_2b763bd91b720d7414fc50e163378834
clone https://github.com/insightsengineering/tern.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern_05d8cd0d757a67b0d1c893284424007a
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern_05d8cd0d757a67b0d1c893284424007a
clone https://github.com/insightsengineering/rtables.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_rtables_f0f6291eb2b1f6976bb05ff26dfa212d
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_rtables_f0f6291eb2b1f6976bb05ff26dfa212d
clone https://github.com/insightsengineering/tern.mmrm.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern.mmrm_ee1a7fba6deed5dd13ca0466e1c4e968
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern.mmrm_ee1a7fba6deed5dd13ca0466e1c4e968
clone https://github.com/insightsengineering/tern.gee.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern.gee_3aaa7fadfce37dee6734b561dcbf376c
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern.gee_3aaa7fadfce37dee6734b561dcbf376c
clone https://github.com/insightsengineering/rlistings.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_rlistings_7c08b1222c8163799de3c79a683ecc9c
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_rlistings_7c08b1222c8163799de3c79a683ecc9c
clone https://github.com/insightsengineering/formatters.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_formatters_2af660375fccd6c369329f665710ecae
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_formatters_2af660375fccd6c369329f665710ecae
clone https://github.com/insightsengineering/osprey.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_osprey_fd4956fcddf407f7776ca93a88340830
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_osprey_fd4956fcddf407f7776ca93a88340830
clone https://github.com/insightsengineering/hermes.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_hermes_c774027dbd79477ddd2093c770a88021
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_hermes_c774027dbd79477ddd2093c770a88021
clone https://github.com/insightsengineering/goshawk.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_goshawk_ca859ec43e2cee0eae1bf7222663c98c
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_goshawk_ca859ec43e2cee0eae1bf7222663c98c
clone https://github.com/insightsengineering/chevron.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_chevron_22a6dec8d97d5eb2c4cca8dbf1a885ed
clone https://github.com/insightsengineering/biomarker-catalog.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_biomarker-catalog_810ab5cb0ce7a100ecea7d78ad128f7d
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_biomarker-catalog_810ab5cb0ce7a100ecea7d78ad128f7d
clone https://github.com/insightsengineering/citril.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_citril_09d841be8f86395466af1f649ab829c1
clone https://github.com/insightsengineering/scda.test.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_scda.test_763fd6f0f55f5186da061770106c1612
clone https://github.com/insightsengineering/tern.rbmi.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern.rbmi_6a1fe99ca79df0966c0be53c96d0d6af
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tern.rbmi_6a1fe99ca79df0966c0be53c96d0d6af
clone https://github.com/insightsengineering/tlg-catalog.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tlg-catalog_6e297f1cdf8b224b494b4fe1f057d5d1
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_tlg-catalog_6e297f1cdf8b224b494b4fe1f057d5d1
clone https://github.com/openpharma/mmrm.git to directory /home/rstudio/.staged.dependencies/packages_cache/openpharma_mmrm_c14d28304e10a1542c52a0103838d41f
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/openpharma_mmrm_c14d28304e10a1542c52a0103838d41f
clone https://github.com/insightsengineering/scda.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_scda_6ea836b807b2d80ac7feb032e00c8aa2
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_scda_6ea836b807b2d80ac7feb032e00c8aa2
clone https://github.com/insightsengineering/scda.2022.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_scda.2022_fae81d8a1331fd1546c933c074ca8409
   - checkout branch origin/main in directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_scda.2022_fae81d8a1331fd1546c933c074ca8409
clone https://github.com/insightsengineering/teal.devel.git to directory /home/rstudio/.staged.dependencies/packages_cache/insightsengineering_teal.devel_df57b5f07d223d3cfb704fc28e033b08
Warning messages:
1: In value[[3L]](cond) :
  You cannot access insightsengineering/teal.modules.helios at host https://github.com. If you expect to be able to access this repo then check that repo and token in envvar 'GITHUB_PAT' are correct.
The response's content was:
Bad credentials
https://docs.github.com/rest Staged dependencies will continue, ignoring this repository. Some packages may not be able to be installed and its package name is assumed to match repository name.
2: In value[[3L]](cond) :
  You cannot access insightsengineering/chevron at host https://github.com. If you expect to be able to access this repo then check that repo and token in envvar 'GITHUB_PAT' are correct.
The response's content was:
Bad credentials
https://docs.github.com/rest Staged dependencies will continue, ignoring this repository. Some packages may not be able to be installed and its package name is assumed to match repository name.
3: In value[[3L]](cond) :
  You cannot access insightsengineering/citril at host https://github.com. If you expect to be able to access this repo then check that repo and token in envvar 'GITHUB_PAT' are correct.
The response's content was:
Bad credentials
https://docs.github.com/rest Staged dependencies will continue, ignoring this repository. Some packages may not be able to be installed and its package name is assumed to match repository name.
4: In value[[3L]](cond) :
  You cannot access insightsengineering/scda.test at host https://github.com. If you expect to be able to access this repo then check that repo and token in envvar 'GITHUB_PAT' are correct.
The response's content was:
Bad credentials
https://docs.github.com/rest Staged dependencies will continue, ignoring this repository. Some packages may not be able to be installed and its package name is assumed to match repository name.
5: In value[[3L]](cond) :
  You cannot access insightsengineering/teal.devel at host https://github.com. If you expect to be able to access this repo then check that repo and token in envvar 'GITHUB_PAT' are correct.
The response's content was:
Bad credentials
https://docs.github.com/rest Staged dependencies will continue, ignoring this repository. Some packages may not be able to be installed and its package name is assumed to match repository name.

I'm concerned about teal.devel
Retrying with GITHUB_PAT set to my own


stackblitz counter is not working for me in chrome

stackblitz counter is not working for me in chrome or IE
I went to https://ngxs-simple.stackblitz.io/
clicked the button, and do not see any numbers incrementing. It is hitting the action.

This is because the state name is required. The demo doesn't yet provide the name in the AppState.
Should be:
@State({
  name: 'app',
  defaults: {
    count: 0
  }
})
export class AppState {
  @Action(Add)
  add({ getState, setState }) {
    const state = getState();
    setState({ count: state.count + 1 });
  }
}

Fixed.


Build: ng prod build bundle size is larger than ng build

OS
Mac OSX - Sierra
Versions.
@angular/cli: 1.0.0-beta.32.3
node: 6.9.4

Repro steps.
This is the repo for the code : https://github.com/ashwin-sureshkumar/gmail-clone-for-blog
It is a very simple gmail clone for purpose of explaining angular concepts.
ng build
gmail-clone$ ng build
Hash: bf6abf3b965e06908e7d
Time: 10887ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 153 kB {4} [initial] [rendered]
chunk    {1} **main.bundle.js, main.bundle.js.map (main) 133 kB** {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.js.map (styles) 31.3 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 3.52 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]

ng build --prod --aot
gmail-clone r$ ng build --prod --aot
Hash: b2cd2a202a280466e874
Time: 24812ms
chunk    {0} **main.005c2ffc467f19c9340f.bundle.js (main) 700 kB** {3} [initial] [rendered]
chunk    {1} polyfills.836e3aece0e7149ec524.bundle.js (polyfills) 153 kB {4} [initial] [rendered]
chunk    {2} styles.37c59cb6f5e610c45cfc.bundle.css (styles) 69 bytes {4} [initial] [rendered]
chunk    {3} vendor.3e14e30aaca91e4984d3.bundle.js (vendor) 2.31 MB [initial] [rendered]
chunk    {4} inline.08d5e9d4a1623033a7ec.bundle.js (inline) 0 bytes [entry] [rendered]

AoT compilation will create the necessary ngfactorys and compiled templates, amongst other things. These can be larger than your original file due to complexity moving away from the Angular Compiler, ngc, and into your component and new *.ngfactory.ts file.
The CLI bundles all of the artifacts generated from the compilation and places that in the main bundle. AoT also removes the need for the ngc which is why you notice the over 1MB drop in the vendor bundle.
More info on AoT can be found here:
http://blog.mgechev.com/2016/08/14/ahead-of-time-compilation-angular-offline-precompilation/

@delasteve's answer is spot on 👍
The only thing I'd add is that your app will always run faster since templates are not being compiled in the browser as well.

Thanks for the explanation @delasteve and @filipesilva. Appreciate it!


firefox: increase timeout to 86400s (24h)

Motivation for this change
Fixes: #129115
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I'm not convinced this will help: we're hitting the nix max-silent-time timeout, not the overall build timeout - so we should be setting meta.maxSilent, not meta.timeout:
https://sourcegraph.com/github.com/NixOS/hydra@b6921c20068b41aa083af7da3da584289a665311/-/blob/src/hydra-eval-jobs/hydra-eval-jobs.cc?L172:22

I'm not convinced this will help: we're hitting the nix max-silent-time timeout, not the overall build timeout - so we should be setting meta.maxSilent, not meta.timeout:
https://sourcegraph.com/github.com/NixOS/hydra@b6921c20068b41aa083af7da3da584289a665311/-/blob/src/hydra-eval-jobs/hydra-eval-jobs.cc?L172:22

Ah, indeed. I'll make a PR, thanks!


Add building guide for the ggml plugin

Explanation
Add docs for building ggml plugins.
Related issue
Fixes #203
What type of PR is this
/kind documentation

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


Remove type piracy, fix aqua test

Closes #1750.

It seems the tests failed. @dennisYatunin would know why we need this piece of code.

It seems the tests failed. @dennisYatunin would know why we need this piece of code.

Ah, I thought it was in the latest release, this should work after we make a new ClimaCore release

bors r+


fix: LEAP-939: Fix langchain ML backend

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

Project coverage is 45.09%. Comparing base (bf8a785) to head (5a6a3cd).
Report is 3 commits behind head on master.

Files
Patch %
Lines

...studio_ml/examples/langchain_search_agent/_wsgi.py
33.33%
6 Missing :warning:

...studio_ml/examples/langchain_search_agent/model.py
50.00%
5 Missing :warning:

label_studio_ml/model.py
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #490      +/-   ##
==========================================
- Coverage   53.25%   45.09%   -8.17%
==========================================
  Files          30       21       -9
  Lines        2056     1315     -741
==========================================
- Hits         1095      593     -502
+ Misses        961      722     -239

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Replacing caused by (CHMO:0010021) with a RO relation?

The 'caused by' (CHMO:0010021) relation contains the comment:

this is a placeholder. Not sure why this isn't covered by BFO or RO tbh.

In RO there are quite a few relations under 'causal relation between processes' (RO:0002501). Is there a reason the CHMO placeholder term is not replaced with one of these?

You're right - it's best to replace this placeholder with one of the RO relations, even if they too are placeholders. Many thanks!

From the curator note on RO:0002501, I think only this is a placeholder/grouping relation not its children.
So far the CHMO 'caused by' is only used for the subclassing of 'injury by flying debris' (CHMO:0010022) with the axiom:
'caused by' some 'laboratory uncontrolled explosion'
In this case, I think the definition of 'causally upstream of' RO:0002411 fits best.


Categorize changes based on distribution mechanism

[skip ci]

Added another big section in CocoaPods and SwiftPM related to migrating away from the beta Swift libraries. PTAL


Fixed the install directory for the windows hosted machine (#7082)

Fixed the install directory for the windows hosted machine

Fix for Unit Test

Looks good to me.


Support DUMP Command

Close #1946
Command Desc：

Adds support for the Dump command, which can be used as dump key.
Currently, the supported data types include: String, Hash, List, Set, ZSet. Redis also supports Stream and Module types; however, due to significant differences between kvrocks and Redis, Stream and Module types are not supported at this time.
Since kvrocks does not support encoding methods such as listpack and lzf, most types calculate the dump payload string using the RAW method.

Redis Documentation: https://redis.io/commands/dump/

@AntiTopQuark Running the ./x.py format should fix the linting issues.

Since kvrocks does not support encoding methods such as listpack and lzf, most types calculate the dump payload string using the RAW method.

I feel good about this, and we can make it work first and then improve.


Add helper function to output to native tables

With the Typst 0.11.0 version, tables have gotten a lot more powerful than before.
I think there should now be an equivalent to the to-tablex function for the native tables now.

This is a great idea -- I've been wanting to do it for awhile, but haven't had the time to make it happen yet...


luci-light: move firewall and ppp to luci collection

Allow luci compilation without firewall and ppp proto. A Firewall or ppp is not needed for the AP basic functions.
This way it is possible to save memory and flash space in low memory enviroments.

I don't like the removal of the firewall. It is so commonly used.
You probably didn't notice, but your change would have removed the firewall also from both LuCI SSL collections, as they depend on luci-light.
If you really need minimal LuCI, just select the individual components but not firewall.

I did not notice that collections are not mandatory. And all needed Luci component can be also individually selected.
I'll close this PR


add PyErr::display

When looking at 3.12 FFI changes I saw the new PyErr_DisplayException and this inspired me to add PyErr_Display for all versions.
While looking at this I noticed that PyErr_PrintEx will call sys.excepthook, so I added the
I think we generally want to be using .display() instead of .print() in tests because there's no meaning to calling sys.excepthook there, so I updated the callsites.

so I added the ...

There seems to be something missing from the above?

so I added the ...

There seems to be something missing from the above?

Yes, I meant to say "added to the documentation", got distracted halfway writing 🤦


People Duplicate for Movies

When I request people with the given endpoint https://api.trakt.tv/movies/tt4154796/people for the movie Avengers: Endgame, I get duplicates in the response like this one having two different jobs and thus, being in the response 2 times (part of the production array) :
 {
                "job": "Casting",
                "jobs": [
                    "Casting"
                ],
                "person": {
                    "name": "Nicholas A. Mudd",
                    "ids": {
                        "trakt": 675687,
                        "slug": "nicholas-a-mudd",
                        "imdb": null,
                        "tmdb": 1653683,
                        "tvrage": null
                    }
                }
            },
            {
                "job": "Casting Associate",
                "jobs": [
                    "Casting Associate"
                ],
                "person": {
                    "name": "Nicholas A. Mudd",
                    "ids": {
                        "trakt": 675687,
                        "slug": "nicholas-a-mudd",
                        "imdb": null,
                        "tmdb": 1653683,
                        "tvrage": null
                    }
                }
            },

Is that a caching issue or some migration bug since as I recall, this endpoint only provided a job property before and is now providing a jobs array ?

Not sure about the duplicate entry, but the reason it has both job and jobs is for backward compatibility since the new people updates (https://github.com/trakt/api-help/issues/74)
Sent with GitHawk

I know why there's both job and jobs, I was mentioning cache issue/migration because of that precisely.
The thing is, why is there 2 entries of Nicholas A. Mudd instead of having something like :
 {
                "job": "Casting , Casting Associate",
                "jobs": [
                    "Casting",
                    "Casting Associate"
                ],
                "person": {
                    "name": "Nicholas A. Mudd",
                    "ids": {
                        "trakt": 675687,
                        "slug": "nicholas-a-mudd",
                        "imdb": null,
                        "tmdb": 1653683,
                        "tvrage": null
                    }
                }
            },

Maybe this is more explicit than my first comment 🙂

Sorry, yeah I read it as if you weren’t aware of the changes but reading it again knowing you were makes more sense 😄.
From what I can see, it looks like the crew aren’t displayed explicitly on the Trakt website (other than Directors and writers at the top) and the “duplicates” in the API seem to be in crew only, not cast. Eg. Chris Evans in the cast has “Steve Rogers, Captain America” as expected, but in the crew section, each “job” is treated as one person entry even though it can be an array. Stephen McFeely has two jobs in “Writing” and one in “Production” also (perhaps others too, I didn’t look further). Maybe it was done/left that way for a reason, but in that case the addition of the jobs array wasn’t necessary.
Sent with GitHawk

Good catch on this, it was a bug. I'll have a fix out later in the week and it will correctly combine people with the same role (in this example production) and the jobs array will correctly have both of that person's jobs. This bug affected movies and episodes.


fix: "Skip CA Secret Upsert for Namespace in Terminating state."

Signed-off-by<EMAIL_ADDRESS>Issue - Vault-Operator fails to create vault-tls secret for new namespaces if any existing namespace is in Terminating State.
Fix -> Skip the namespaces in terminating state.

@akijakya Not sure why but dco check is still failing even after rebasing and adding signoff. I have created a new PR with similar changes. https://github.com/bank-vaults/vault-operator/pull/395 . I am closing this PR for that.


Don't flat ObjectId's

Hello community,
What do you think about including and extra flag so that flatten won't flat an object if it is an ObjectId (from mongo)?
I'm having this issue where I pass a ObjectId to the csv export and it flattens it into smaller fields: _bsontype and id (with incomprehensible characters).
If you agree with this I can go forward and create the PR for it.

Sounds reasonable, go for it.

That pull request to the flat library should fix this issue if it get's accepted.
I'll submit shortly a PR to json2csv with the necessary change in this library.

Btw, in the meantime, what I currently do is json2csv(JSON.parse(JSON.stringify(myObject)))
A bit hackish but do the job...


Mutation : Variables is a not a valid JSON object

Hi !
I'm adding my first mutation to my project and the request fails (it's not even sent) with the following error:
2021-08-10 19:18:25.262474+0200 MyProject[16878:1617980] [API] Starting mutation DE7BB14B-7CE4-4D11-9661-E9EFFD836990
Got failed event with error APIError: Variables is a not a valid JSON object

I spent the day on this and I'm starting to think there either is a bug or I missed something really big.
All the queries are working fine. It only happens on mutations.
The relevant part of the schema looks like this:
type File {
    id: ID!
    name: String
    type: String
    mime: String
    createdAt: AWSDateTime
    data: String
}

input FileInput {
    name: String
    type: String
    mime: String
    data: String
}

type ChatMessage {
    id: ID!
    authorName: String!
    authorIsPatient: Boolean!
    createdAt: AWSDateTime!
    body: String!
    files: [File]!
}

input ChatMessageInput {
    body: String
    files: [FileInput]
}

    [...]

type Query {
    [...]
}

type Mutation {
    sendTcChat(message: ChatMessageInput): ChatMessage @aws_cognito_user_pools
}

schema {
    query: Query
    mutation: Mutation
}

I have a GraphQLRequest extension that looks like this:
extension GraphQLRequest {
    public static func sendTcChat(mutation: SendTcChatMutation) -> GraphQLRequest<ChatMessage> {
        let request = GraphQLRequest<ChatMessage>(document: SendTcChatMutation.operationString,
                                                  variables: mutation.variables as [String : Any],
                                                 responseType: ChatMessage.self,
                                                 decodePath: "sendTcChat")
        return request
    }
[...]
}

and I'm invoking the mutation like this:
private func sendTcChat() -> AnyCancellable {
        let input = ChatMessageInput(body: "Lorem ipsum", files: [])

        let sink = Amplify.API.mutate(request: .sendTcChat(mutation: SendTcChatMutation(message: input)))
            .resultPublisher
            .sink {
                if case let .failure(error) = $0 {
                    print("Got failed event with error \(error)") // <==== This is where the error message comes from
                }
            }
            receiveValue: { result in
                switch result {
                case .success(let message):
                    print("Got success")
                case .failure(let error):
                    print("Got failed result with \(error.errorDescription)")
                }
            }
        return sink
    }

Does anyone has any clue? It's driving me crazy...

what does SendTcChatMutation  and the variables property look like? The error you're seeing is a client side validation check done using JSONSerialization.isValidJSONObject(variables) here

SendTcChatMutation is generated by codegen:
public final class SendTcChatMutation: GraphQLMutation {
  public static let operationString =
    "mutation SendTcChat($message: ChatMessageInput) {\n  sendTcChat(message: $message) {\n    __typename\n    id\n    authorName\n    authorIsPatient\n    createdAt\n    body\n    files {\n      __typename\n      id\n      name\n      type\n      mime\n      createdAt\n      data\n    }\n  }\n}"

  public var message: ChatMessageInput?

  public init(message: ChatMessageInput? = nil) {
    self.message = message
  }

  public var variables: GraphQLMap? {
    return ["message": message]
  }
[...+ 200 lines of autogenerated stuff...]

I printed the content of "variables" at the line that throws the error (from your link).
I'm sorry if this is some dumb debug job, but I'm a beginner with amplify and I'm not familiar with what's going on under the hood just yet...
Printing description of variables:
▿ Optional<Dictionary<String, Any>>
  ▿ some : 1 element
    ▿ 0 : 2 elements
      - key : "message"
      ▿ value : Optional<JSONEncodable>
        ▿ some : ChatMessageInput
          ▿ graphQLMap : 2 elements
            ▿ 0 : 2 elements
              - key : "body"
              ▿ value : Optional<JSONEncodable>
                - some : "Ghgfj"
            ▿ 1 : 2 elements
              - key : "files"
              ▿ value : Optional<JSONEncodable>
                - some : 0 elements

hey @quentinhayot, is SendToChatMutation generated in the file called API.swift ? If so, that's used with the older AppSync SDK. For the question to generate API.swift when you run amplify push should be "No"
? Do you want to generate code for your newly created GraphQL API
    `No`

you can run amplify codegen models to generate the Amplify model classes.
The workflow for setting it up looks like this https://docs.amplify.aws/lib/graphqlapi/getting-started/q/platform/ios#install-amplify-libraries
What does your annotated GraphQL schema? is it File and ChatMessage with the @model directive on the ChatMessage?
type File {
    id: ID!
    name: String
    type: String
    mime: String
    createdAt: AWSDateTime
    data: String
}

type ChatMessage @model {
    id: ID!
    authorName: String!
    authorIsPatient: Boolean!
    createdAt: AWSDateTime!
    body: String!
    files: [File]!
}

@lawmicha I indeed use API.swift and I use amplify codegen AND amplify codegen models too.
Also,

My backend resources are NOT created by amplify (I have an existing infrastructure built with Serverless Framework). I copy my appsync graphql schema in amplify's directory before executing codegen. (I'm not supposed to use amplify push in this case, right ?)
I had the @model and @connection directives, but I removed them because I'm not using DynamoDB (https://docs.amplify.aws/cli/graphql-transformer/model). All my calls are routed to lambda resolvers with custom actions (I don't use create delete `get'
The documentation is a bit confusing for my use case and I had a hard time having the queries work. For example, this part clearly asks to install the AppSync SDK: https://docs.amplify.aws/cli/graphql-transformer/codegen#ios-usage

Please advise

Thanks for explaining! I tried replicating a similar set up with the Todo schema that the CLI provides. I can see that mutation.variables doesn't contain a valid JSON object
public var variables: GraphQLMap? {
    return ["input": input, "condition": condition]
  }

since input is the actual CreateTodoInput object that contains graphQLMap: GraphQLMap. AppSync SDK probably serializes it differently, while Amplify.APi is expecting a valid JSON object. Could you build your own variables with the GraphQLMap like so?
let variables = ["input": mutation.input.graphQLMap, "condition": mutation.condition?.graphQLMap]

extension GraphQLRequest {
    public static func createTodo(mutation: CreateTodoMutation) -> GraphQLRequest<Todo> {
        let variables = ["input": mutation.input.graphQLMap, "condition": mutation.condition?.graphQLMap]
        let request = GraphQLRequest<Todo>(document: CreateTodoMutation.operationString,
                                           variables: variables as [String : Any],
                                           responseType: Todo.self,
                                           decodePath: "createTodo")
        return request

    }
}

It works! Thank you !
Is there a way to clean this up and remove the old AppSync SDK to only use Amplify with my use case (using an AppSync api not deployed with Amplify) ?
It's not too late to recreate everything with Amplify... the thing is that all our other services are build and deployed with Serverless so it was a natural choice to do the same with this project.

Hi @quentinhayot, glad it's working for you. There isn't a migration path for developers using AppSync SDK to migration to Amplify.API, however the workflow i'd recommend is to start afresh with a new project and use your existing schema. amplify add api to provision the backend, amplify codegen models to generate the Model files used with Amplify.API. I recall you may have some custom GraphQL requests, so you could use a combination of Amplify.API APIs and constructing the GraphQLRequest object yourself, described in the advanced workflows.

Thanks, I'll check !

@lawmicha I'm sorry to reopen this, but I get the same issue when I have a nested input in my mutation variables.
If I extract the nested inputs in new variables in the mutation it works fine with your workaround.
This won't work (Variables is a not a valid JSON object):
input FooInput  {
    nestedProp: BarInput
    propA: String
}

input BarInput  {
    propB: String
}

type Mutation {
    testMutation(foo: FooInput!): String @aws_cognito_user_pools
}

but this will:
input FooInput  {
    propA: String
}

input BarInput  {
    propB: String
}

type Mutation {
    testMutation(foo: FooInput!, bar: BarInput): String @aws_cognito_user_pools
}

Hi @quentinhayot, it's unlikely we'll modify how API.swift is generated since the whole AppSync SDK is going to be deprecated for Amplify.API / Amplify.DataStore. If taking API.swift and the workaround doesn't work as expected for the nested predicates, and you want to keep the nested inputs, i think the best approach is to handwrite the custom GraphQL variables object. Otherwise, the workaround to un-nest them can be the solution if it is scalable for your use case.
Could you try recursively translating variables: GraphQLMap? to a valid JSON object before using it? For example, taking your schema with nested inputs,
input FooInput  {
    nestedProp: BarInput
    propA: String
}

input BarInput  {
    propB: String
}

type Mutation {
    testMutation(foo: FooInput!): String
}

(removed the @aws_cognito_user_pools since i was provisioning this with API key- not sure if it would have worked with the annotation).
I haven't tested this against the service, but only made sure the nested variables is a valid json as per JSONSerialization.isValidJSONObject
extension GraphQLMap {
    func toJSON() -> [String: Any?] {
        var json = [String: Any?]()
        self.forEach { (key, value) in
            if let graphQLMapConvertible = value as? GraphQLMapConvertible {
                json.updateValue(graphQLMapConvertible.toJSON(), forKey: key)
            } else {
                json.updateValue(value, forKey: key)
            }
        }
        return json
    }
}

extension GraphQLMapConvertible {
    func toJSON() -> [String: Any?] {
        graphQLMap.toJSON()
    }
}

Test code
func testCreatingValidJSON() {
        let mutation = TestMutationMutation(foo: FooInput(nestedProp:
                                                            BarInput(propB: "b"),
                                                          propA: "a"))
        if !JSONSerialization.isValidJSONObject(mutation.variables) {
            print("mutation.variables is not valid json: \(mutation.variables)")
        }
        var validJSON = mutation.variables?.toJSON()
        if JSONSerialization.isValidJSONObject(validJSON) {
           print("Valid json: \(validJSON)")
        }
    }

output
mutation.variables is not valid json: Optional(["foo": Optional(amplify1377.FooInput(graphQLMap: ["propA": Optional("a"), "nestedProp": Optional(amplify1377.BarInput(graphQLMap: ["propB": Optional("b")]))]))])
Valid json: Optional(["foo": Optional(["nestedProp": Optional(["propB": Optional("b")]), "propA": Optional("a")])])

This way, you can use toJSON() in your static GraphQLRequest builder methods like
// Before
let variables = ["input": mutation.input.graphQLMap, "condition": mutation.condition?.graphQLMap]

// with the extension
let variables = ["input": mutation.input.graphQLMap.toJSON(), "condition": mutation.condition?.graphQLMap.toJSON()]

Closing due to inactivity.


Additions for keypair conversion from ed25519 to curve25519

http://doc.libsodium.org/advanced/ed25519-curve25519.html

Thanks for the pull request. We've had some discussion on this functionality in issue #85, and I decided to not add it until someone could present a valid use-case for the functionality. The reason being that I don't feel confident in adding something that could open up to cross-protocol attacks unless there's a real need for it from developers. Do you have a specific use-case you need?

Pond uses these when initializing v2 of its ratchet, but Pond is not written in Rust and it didn't need them really.  I could imagine Axolotl initialization with TripleDH might tend towards using these when you're trying to squeeze a bunch of preliminary ratchet state onto a business card QR code or something.

I'm not familiar with the Pond ratchet, but AFAIK the Axolotl ratchet only uses diffie-hellman, e.g. crypto_scalarmult() and doesn't use public key signatures, crypto_sign() so there would be no need to convert between ed25519 and curve25519 key types for it. I might be wrong though, I don't know if the Axolotl ratchet has been updated since I last looked at it.

Pond uses Axolotl.  Imho, it's not worth going into how Pond uses these.
Yes, Axolotl normally uses TripleDH for deniability, but there are situations where you might want full/manual ratchet initialization, like a phones initiating connectivity in physical proximity or a business card with a QR code.  Those applications benefit from a signing key that can be verified elsewhere, so they save 32 bytes using this.
There are applications in implicit signatures like elliptic curve qu-vanstone that save 64 bytes, but that requires exposing even more.  https://en.wikipedia.org/wiki/Implicit_certificate#Generating_implicit_certificates

I'm closing this issue for now since we're mostly discussing hypothetical use cases for a feature that brings with it potential for cross protocol attacks. I'm open to revisiting this issue if more concrete use-cases are found. Thanks to all of you that have brought valuable input to this issue.

Just curious. It is not the case that sodiumoxide is intended to be a generic wrapper for libsodium?
On 11/30/2015 at 4:30 AM, "dnaq"<EMAIL_ADDRESS>wrote:

I'm closing this issue for now since we're mostly discussing
hypothetical use cases for a feature that brings with it potential
for cross protocol attacks. I'm open to revisiting this issue if
more concrete use-cases are found. Thanks to all of you that have
brought valuable input to this issue.

Reply to this email directly or view it on GitHub:
https://github.com/dnaq/sodiumoxide/pull/89#issuecomment-160570135

sodium is a bit more opinionated.
If you are looking for a low-level, generic wrapper for libsodium, https://github.com/rustyhorde/sodium-sys and https://github.com/zonyitoo/libsodium-sys might be better options.

One of those might be a better fit for me. Thanks for the links.
On 11/30/2015 at 8:47 AM, "Frank Denis"<EMAIL_ADDRESS>wrote:

sodium is a bit more opinionated.
If you are looking for a low-level, generic wrapper for libsodium,
https://github.com/rustyhorde/sodium-sys and
https://github.com/zonyitoo/libsodium-sys might be better options.

Reply to this email directly or view it on GitHub:
https://github.com/dnaq/sodiumoxide/pull/89#issuecomment-160631478

It is not the case that sodiumoxide is intended to be a generic wrapper for libsodium?

sodiumoxide is a bit more opinionated. Hope you find what you're looking for elsewhere. However, I asked you for a use case for the functionality you requested, but you didn't provide me one. Still if you have a specific use case that you want to discuss we could discuss it further.


Update/Add Helm 3

Tool information

Tool name: Helm 3
Add or update? Update
Desired version: https://v3.helm.sh/, https://helm.sh/
Approximate size:
If this is an add request:

Brief description of tool: The package manager for Kubernetes
URL for tool's homepage: https://v3.helm.sh

Area for Triage:
Containers, Go
Virtual environments affected

[+] macOS 10.15
[+] Ubuntu 16.04 LTS
[+] Ubuntu 18.04 LTS
[+] Windows Server 2016 R2
[+] Windows Server 2019

You can use helm 3 inside docker container
docker run -i --rm -v $GITHUB_WORKSPACE/.kubeconfig:/root/.kube/config -v $GITHUB_WORKSPACE/chart:/root/chart alpine/helm upgrade NAME /root/chart --install --set image.tag=${{ github.sha }}

Currently, helm 3 is installed on Ubuntu only.
@alepauly , do we want to add Helm 3 to Windows and macOS for consistency?

@maxim-lobanov I think we should yeah. Thanks!

Hello, thank you for your response. Pull requests with helm were merged and changes would be added in next images rollout.

Hello, helm was added to all images. If you have any concerns please feel free to reopen the issue.


Fix deprecated API peek/see

Fix deprecated API peek/see in Yazi v0.4.0

Now scrollable in preview panel

Now can press ctrl+e/ctrl+y to scroll in preview panel, and toggle line wrap


UI-7645 - Start implementing migration from 5.0 to 5.1

Starting the actual migration script implementation so that we can start testing the CLI on real cases.

@Nouzbe this PR does two things:

it introduces the migrateFilters and migrateContextValues 5.0 --> 5.1 migration functions. It triggers them in the migrateDashboard and migrateWidget functions.
it introduces a deserialization/serialization mechanism: to manipulate more easily the content objects, we thought it would be better to deserialize them at first.

There are two problems with the deserialization/serialization mechanism:

the deserialization mechanism from AUI-5 uses produce from immer, hence returns immutable objects. It causes us not to be able to directly mutate the deserialized states. That's why we moved produce from wrapping the callback in the getMigrateXyz functions to being used at a lower level, inside the migrateXyz functions, after the deserialization. An alternative we also thought of but liked less:

add an autoFreeze boolean to the AUI deserialization functions, using this immer concept. Would require some investigation of how it works though

as migrateWidget starts by deserializing the widget state, it can't be called like this in migrateWidgetsWithinDashboard anymore, because the passed widget state is already deserialized at this point. Hence why we introduced mutateWidget, which triggers all the widget state modifications after deserialization, and be reused in migrateWidgetsWithinDashboard. For consistency, we introduced mutateDashboard too. Alternatives we also thought of but liked less:

passing an doesRequireToDeserialize boolean to migrateWidget --> doesn't look clean at all
serializing the widget state before migrateWidgetsWithinDashboard is called --> causes extra useless serialization+deserialization step

There's a couple other things that I noticed we forgot to do in this PR:

migrateFilters shouldn't have been introduced that way. It should have been called migrateFilter, used in a forEach in migrateDashboard and migrateWidget, as well as passed in a callback to the function returned by getMigrateSavedFilters.
after the introduction of mutateWidget, migrateWidget will only be used for saved widgets, so it should be renamed migrateSavedWidget
we might want to have the same deserialization/serialization mechanism for filters too, using parse/stringify.

migrateFilters shouldn't have been introduced that way. It should have been called migrateFilter, used in a forEach in migrateDashboard and migrateWidget, as well as passed in a callback to the function returned by getMigrateSavedFilters

I disagree with this because saved filters have a different form than filters within a widget/dashboard state.


Require net_bind_service capability

CRIs have different sets of default capabilities.
There is also always an option that CRI can be configured by an administrator
of Kubernetes cluster or operator deployed in cluster.
Therefore let's explicitly request net_bind_service where it is required.
What this PR does / why we need it:
Special notes for your reviewer:
Release note:
None

/retest

@xpivarc do you have some places, e.g. ci runs with crio and/or documentation where we can see that this is needed?

We are not directly impacted. This is just to ensure that we work on all possible configurations. I believe you can have CRI with no default capabilities. We were impacted by capabilities on 1.20 lane where crio didn't have capabilities that virtiofs requires.

/retest
Seems like flake

/cc @petrkotas

/lgtm

Do we still want to do this ? imo, its worth it.
We'll need to find a reviewer w/ approve powers willing to take a look at it.

Other than the small remark that not all bridge interfaces require the DHCP server (not sure if differentiating these scenarios is feasible), I miss an explanation on the commit msg of why bridge, masquerade, and slirp require this set of capabilities (bridge & masquerade have a dhcp server that binds on port 67, ...).
That information is helpful to understand why the capability was explicitly added, and eventually will be a good input to the network developer's guide.

The guide probably requires a bigger refresh.

Other than the small remark that not all bridge interfaces require the DHCP server (not sure if differentiating these scenarios is feasible), I miss an explanation on the commit msg of why bridge, masquerade, and slirp require this set of capabilities (bridge & masquerade have a dhcp server that binds on port 67, ...).
That information is helpful to understand why the capability was explicitly added, and eventually will be a good input to the network developer's guide.

The guide probably requires a bigger refresh.

True. I can volunteer to update it, not exactly sure when I'll find the time for it.
I was just asking for a couple of lines that I can copy paste from to make it easier :)

Also I see in four lanes the same test failing:

Tests  Suite: [Serial][sig-compute]SecurityFeatures Check virt-launcher  capabilities [test_id:4300]has precisely the documented extra  capabilities relative to a regular user pod expand_less
16s

tests/security_features_test.go:219 Capabilities in compute was [NET_BIND_SERVICE NET_ADMIN SYS_NICE] Expected     : 3 to equal     : 2 tests/security_features_test.go:240

Also I see in four lanes the same test failing:
Tests Suite: [Serial][sig-compute]SecurityFeatures Check virt-launcher capabilities [test_id:4300]has precisely the documented extra capabilities relative to a regular user pod expand_less	16s
tests/security_features_test.go:219 Capabilities in compute was [NET_BIND_SERVICE NET_ADMIN SYS_NICE] Expected : 3 to equal : 2 tests/security_features_test.go:240

Good catch. I was too eager w/ the lgtm.
/lgtm cancel

Sorry guys, somehow I made a mistake while rebasing...

/approve

/lgtm

/retest


Where to download cos_data image？we can only download chain-of-spot.json

Hi! Thanks for your interest in our work. Our Chain-of-Spot is constructed on LLaVA-1.5 by further fine-tuning LLaVA-1.5 for one epoch. Therefore, our training data is identical to LLaVA-1.5 and we only need the JSON file to customize our training. So just prepare the LLaVA-1.5 dataset here and then you can start the training. You can leave comments should you have any further questions on launching the fine-tuning.


feat: add method to check if a service is active

Closes #14.

Let's bump on the next PR. I implemented the hostname functionality, I just need to add some tests first.


Automatic PR from RestAPI-PR1730

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1730

Codecov Report

Merging #1469 into master will increase coverage by <.01%.
The diff coverage is 70%.

@@            Coverage Diff            @@
##           master   #1469      +/-   ##
=========================================
+ Coverage    55.1%   55.1%   +<.01%
=========================================
  Files        3417    3419       +2
  Lines       83477   83495      +18
=========================================
+ Hits        45996   46008      +12
- Misses      37481   37487       +6

Impacted Files
Coverage Δ

azure-graphrbac/azure/graphrbac/models/__init__.py
100% <100%> (ø)
:arrow_up:

.../graphrbac/models/application_create_parameters.py
35.71% <50%> (-2.75%)
:arrow_down:

.../graphrbac/models/application_update_parameters.py
30.76% <50%> (-2.57%)
:arrow_down:

...azure/graphrbac/models/required_resource_access.py
71.42% <71.42%> (ø)

...raphrbac/azure/graphrbac/models/resource_access.py
71.42% <71.42%> (ø)

Continue to review full report at Codecov.

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


no love for windows users?

i know this can be converted for use on windows cause i have that version. but it has not been updated for a few years now. i see this version was updated a few days ago and seems to get alot more attention. would be awesome if we could get this version working on windows.

Hey @smoothnobody
Sorry but I just take care of the macOS version. The Windows version, while sharing the name, shares pretty much nothing code wise as 99% of Aerial's code is platform specific.


Question regarding query params

Hi, I have a question regarding query params, I have some paginable methods, so I've created a class named PaginationRequest with page and size params, this way I add PaginationRequest to all my paginable methods, and also I can add more params as ordination, filters, etc...
But in swagger-ui this is the result:

If I ignore the param with @ApiIgnore and I add the @ApiImplicitParams the result is ok, but I want to avoid the @ApiImplicitParams annotation.
My controller mehod:
@RequestMapping(method = RequestMethod.GET)
@ResponseStatus(HttpStatus.OK)
public PublicationsResponse fooBar(
    @Valid PaginationRequest paginationRequest
    @Valid OrdinationRequest ordinationRequest
    ....) {

}

My PaginationRequest class:
@ApiModel
public class PaginationRequest extends BaseRequest {

    @ApiModelProperty(value = "The number of the requested page, from api model")
    @Min(value = 1, message = "error.pagination.page.min")
    private Integer page;

    @ApiModelProperty(value = "The size of the requested page, from api model")
    @Min(value = 10, message = "error.pagination.size.min")
    private Integer size;

}

Is there a solution to this?

Couple of things that seem off about your fooBar operation

a GET cannot have a body post, or atleast its not guaranteed to be supported by any server implementation of HTTP
even if its a POST, it is not possible to have multiple bodys in a request. It should probably be modeled as RequestParts with multipart/form-data as the consumes media type.

In any case, If it were me I'd model it as such
@RequestMapping(method = RequestMethod.GET)
@ResponseStatus(HttpStatus.OK)
public PublicationsResponse fooBar(
    @Valid @ModelAttribute QueryRequest querRequest
    ....) {

}

and make QueryRequest a list of all the query related query string params.

Hi, I think I didn't explain myself.
attributes inside of paginationrequest and ordinationrequest are part of the querystring. currently I'm using @ApiImplicitParam to set page and size as querystring params in swagger, also my api is expecting page and size as querystring.
So with springmvc I can use many object in the params of a method as I showed in my first post and it will expect them as querystring if request method is set to Get, but I would like to avoid the ApiImplicitParam annotation.

Maybe I wasn't being clear.  These are the steps you need to do.

Remove ApiImplicitParams Annotation.
Make PaginationRequest and OrdinationRequest beans with getters and setters. There is no need to annotate them with ApiModel etc.
annotate your parameters with @ModelAttribute (In addition to @valid

Great! Thank you very much!


[3.0] Gizmos loose their colors

Tested on Godot 3.0 master c37fad650f92845a6f59740fea2fea1b46f56db1
Windows 10 64 bits
Sometimes gizmos get coloured in very transparent black, making it hard to tell which axis is which. I don't know yet how it happened but that was quick, after I started adding a few meshes to a scene and creating materials. Closing the scene and reopening doesn't fix it. It also affects the grid.

It also happens when you turn off default lightning. Gizmos and grid are affected the same way as regular objects placed in the scene; for example using dof, gizmos and grid get blurred as well.

It also happens when you turn off default lightning. Gizmos and grid are affected the same way as regular objects placed in the scene; for example using dof, gizmos and grid get blurred as well.

Likely related to #8485.

I think this is fixed, gizmos should stay on top and colored always..

I can confirm that it works now on my Win10 a8a1f2e2a864e6b58d5bcf1c7e53a43cdb6d95d9

yeah!


Opening a nonexistent user crashes the app

Version 1.5.0 (1330)
Device: iPhone 7 Plus (iOS 10.3.3)
Was reading the Rebranding issue and tapped the @GitHawk... and the app crashed.

🤔, apparently the user does exist. Does this crash for every mention then?

It doesn't. Let me investigate

This is pretty bad. URLs like "github.com" or "twitter.com" crash the app, as they are not prefixed with "http://" or "https://".
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'The specified URL has an unsupported scheme. Only HTTP and HTTPS URLs are supported.'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000109844b0b __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x00000001092a9141 objc_exception_throw + 48
	2   CoreFoundation                      0x00000001098ad625 +[NSException raise:format:] + 197
	3   SafariServices                      0x000000010a5cff8a -[SFSafariViewController initWithURL:entersReaderIfAvailable:] + 450
	4   Freetime                            0x0000000107b20b47 _TTOFCSo22SFSafariViewControllercfT3urlV10Foundation3URL_S_ + 55
	5   Freetime                            0x0000000107b1bb01 _TFCSo22SFSafariViewControllerCfT3urlV10Foundation3URL_S_ + 65
	6   Freetime                            0x0000000107b6418e _TFE8FreetimeCSo16UIViewController13presentSafarifT3urlV10Foundation3URL_T_ + 62
	7   Freetime                            0x0000000107b64462 _TToFE8FreetimeCSo16UIViewController13presentSafarifT3urlV10Foundation3URL_T_ + 66
	8   Freetime                            0x0000000107b6c79c _TFE8FreetimeCSo16UIViewController9didTapURLfT4viewCS_20AttributedStringView3urlV10Foundation3URL_T_ + 76
	9   Freetime                            0x0000000107b6c827 _TToFE8FreetimeCSo16UIViewController9didTapURLfT4viewCS_20AttributedStringView3urlV10Foundation3URL_T_ + 87
	10  Freetime                            0x0000000107a78fb0 _TTDFE8FreetimeCSo16UIViewController9didTapURLfT4viewCS_20AttributedStringView3urlV10Foundation3URL_T_ + 80
	11  Freetime                            0x0000000107a78f49 _TTWCSo16UIViewController8Freetime28AttributedStringViewDelegateS0_FS1_9didTapURLfT4viewCS0_20AttributedStringView3urlV10Foundation3URL_T_ + 57
	12  Freetime                            0x0000000107b16390 _TFC8Freetime20AttributedStringView5onTapfT10recognizerCSo22UITapGestureRecognizer_T_ + 1248
	13  Freetime                            0x0000000107b167fa _TToFC8Freetime20AttributedStringView5onTapfT10recognizerCSo22UITapGestureRecognizer_T_ + 58
	14  UIKit                               0x000000010ac3af59 -[UIGestureRecognizerTarget _sendActionWithGestureRecognizer:] + 57
	15  UIKit                               0x000000010ac42d57 _UIGestureRecognizerSendTargetActions + 109
	16  UIKit                               0x000000010ac4070b _UIGestureRecognizerSendActions + 225
	17  UIKit                               0x000000010ac3f9ce -[UIGestureRecognizer _updateGestureWithEvent:buttonEvent:] + 981
	18  UIKit                               0x000000010ac2c152 _UIGestureEnvironmentUpdate + 1219
	19  UIKit                               0x000000010ac2bc43 -[UIGestureEnvironment _deliverEvent:toGestureRecognizers:usingBlock:] + 484
	20  UIKit                               0x000000010ac2ae0a -[UIGestureEnvironment _updateGesturesForEvent:window:] + 274
	21  UIKit                               0x000000010a776eea -[UIWindow sendEvent:] + 4092
	22  UIKit                               0x000000010a723a84 -[UIApplication sendEvent:] + 352
	23  FLEX                                0x00000001088de0a2 __35+[FLEXKeyboardShortcutManager load]_block_invoke.108 + 1026
	24  UIKit                               0x000000010af075d4 __dispatchPreprocessedEventFromEventQueue + 2926
	25  UIKit                               0x000000010aeff532 __handleEventQueue + 1122
	26  CoreFoundation                      0x00000001097eac01 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	27  CoreFoundation                      0x00000001097d00cf __CFRunLoopDoSources0 + 527
	28  CoreFoundation                      0x00000001097cf5ff __CFRunLoopRun + 911
	29  CoreFoundation                      0x00000001097cf016 CFRunLoopRunSpecific + 406
	30  GraphicsServices                    0x000000011188ea24 GSEventRunModal + 62
	31  UIKit                               0x000000010a706134 UIApplicationMain + 159
	32  Freetime                            0x0000000107acaad7 main + 55
	33  libdyld.dylib                       0x000000010db1765d start + 1
	34  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException

This would be such an ugly fix, not knowing if you should use http or https. 😐

Ha. I just learned as well that links like these are opened like relative paths in your GitHub repo on GitHub itself. (eg. githawk.com)

@BasThomas Alwayshttps ;)

But that doesn't guarantee that all those links work, as not every website has switched to https.

Will work on a fix for this, easy to repro

test bump

@BasThomas I understand that. I was suggested to an easy fix where https was considered safest. I would assume you could do a HEAD request to the https-first and if this fails fallback to http


Add Harry M to contributors

@harimm, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

@Roshanjossey, Though this is the first time I'm contributing to a repo using the pull request workflow, I was already familiar with git and I do have a few personal projects as well. I do feel that it's wonderful even for the truly rookies to understand how GitHub works and start contributing! Many thanks for maintaining this repo!

@harimm, I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com


Continuous Integration (CI) Best Practices with SAP – Introduction and Navigator

Thank you for the SAP tutorial.
After I deploy a Fiori application in cloud foundry environment and try to start the application, It is getting crashed. I tried to solve the issue with troubleshooting guide from the link below but couldn't solve the issue.
https://docs.cloudfoundry.org/devguide/deploy-apps/troubleshoot-app-health.html
Below is the error log

2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.4.0-111-generic 2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start" 2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! node v6.12.3
2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! npm v3.10.10 2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! missing script: start 2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! 2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR! If you need help, you may report this error at:
2018-04-04T14:58:11.32-0400 [APP/PROC/WEB/0] ERR npm ERR!
https://github.com/npm/npm/issues 2018-04-04T14:58:11.33-0400 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file with any support request: 2018-04-04T14:58:11.33-0400 [APP/PROC/WEB/0] ERR npm ERR! /home/vcap/app/npm-debug.log

Thanks,
Sankeerth

Please check your package.json if the start script fits.


Migrate on dio5

@matthewelwell please take a look

any updates?

Hi @dkrutskikh, @Dan-Crane, we will get to this shortly. Please bear with us. Thanks!

Hi @dkrutskikh, I noticed that the workflows were only being triggered on merges (and had been failing) so I've updated that in the main branch now - could you please rebase / merge our main branch branch into this PR so that we can verify that the workflows pass?

@matthewelwell done


Add demo for Angular and VueJS

In postclone workflow apps are created from app templates -
https://github.com/NativeScript/nativescript-plugin-seed/issues/128


New Version

Git repos
Notifications
Theme manager
Script execution with realtime STDOUT feed to front
Download/Installation of ide
Workspaces management
Database integration with Typeorm

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Project Milestone 3 Peer Review

All looking great. I like the idea of the load balancing. The wiki of load balancing is well documented. Good work.

Thanks Jitendra. You can close the issue, if you are done testing.


Allow use styleOverrides to target parts in new component variants

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Allow use of styleOverrides in custom variants so we can target and theme component parts (e.g. root, listbox) that are not accessible by specificity from root.
Examples 🌈
Global component overrides can theme component parts via styleOverrides.
const theme = createTheme({
  components: {
    MuiAutocomplete: {
      styleOverrides: {
        listbox: background: 'red';
      },
    },
  },
});

However, when creating new component variants you are put into root.
const theme = createTheme({
  components: {
    MuiAutocomplete: {
      variants: [
        {
          props: { newVariant: true },
          style: {
            // how do I theme MuiAutocomplete-listbox as it isn't enclosed by root?
          },
        },
     ]
    },
  },
});

The current workaround is to use the global style overrides syntax with styleOverrides and a callback with ownerState. This results in variant logic in two syntaxes and spread outside the variants array.
const theme = createTheme({
  components: {
    MuiAutocomplete: {
      styleOverrides: {
        // component variant logic mixed with global
        listbox: ({ ownerState }) => ({
          ...(ownerState.newVariant === true && {
            background: 'red',
          }),
        }),
      },
      variants: [
        // other variants ...
     ]
    },
  },
});

I propose we allow the use of the styleOverrides syntax with custom variants.

Cleaner than the callback syntax
Keeps variant logic in the variants array
Reuses styleOverrides syntax
Cleaner targeting of component parts instead of drilling through CSS specificity

const theme = createTheme({
  components: {
    MuiAutocomplete: {
      variants: [
        {
          props: { newVariant: true },
          styleOverrides: {
            listbox: {
              background: 'red',
            },
          },
        },
     ]
    },
  },
});

Motivation 🔦
MuiAutocomplete uses several parts by portal that are inaccessible via CSS specificity from the root component. By allowing the use of styleOverrides in the new component variants we can target and theme those parts just as we do in global style overrides. This avoids putting variant logic in callbacks outside of the variants array.

Cleaner than the callback syntax

I'd recommend that if you don't need to serve your theme as static files, always go with styleOverrides. It is more flexible and robust because you have full control of the conditional expression on what gets into styles and what's not.


Name matching on workshop request forms

When we get a workshop request form, we have the option to add the the person who requested it to the database if they are not already in.
@pbanaszkiewicz Can you clarify the conditions for having a person considered to be a matching person?  We've come across cases where the name may not be an exact match but the email is an exact match  (i.e., "John Smith" vs "John J. Smith" both have the email address<EMAIL_ADDRESS>-- and it does not recognize a matching person.    We then have the option "This person is not in the database. Click to add them."
Could we have AMY suggest a possible matching person, and then let us select a matching person if that was not a correct match? I'm thinking something like what we do when we match an instructor training application to an existing person.
Note: this issue replaces an issue raised by @Talishask  that included actual names/emails of people.  I deleted that to avoid publicly sharing personal inforamation.  Talisha, please feel free to respond here as to whether I've captured your original intent.  Piotr- if you want to see some real examples of what we're talking about I can share those by email.

@maneesha - This is great. Thanks

Hi @Talishask and @maneesha  - the matching criteria are defined in CommonRequest.host() as below:
person.personal = request.personal AND
person.family = request.family AND
person.email = request.email

A single match is returned, or nothing.
The problem, I think, is that we don't link any of the 3 workshop requests (workshop request, workshop inquiry, self-organised submission) to the person in AMY who submitted them. So this message "This person is not in the database. Click to add them." is purely informational. I could change this information to show all possible matches in current DB.

We definitely need an update of some type, but what exactly the criteria should be is what I'm trying to think about. @maneesha  feel free to chime in here on my thoughts:
I think the most reliable indicator will be email, although there are rare occasions when someone submits from a secondary email in which case we would need to consider both email addresses (primary or secondary). I'm not sure if we want to say email needs to match for sure and the other variables are optional, just so that we can see some possibilities?

Could we do something that is a case by case basis, like:

If email and personal and family match = Matched Person
If email and family match  = Matched Person
Then if neither of the above for sure matching person cases exists suggest possible matches based on personal and family match?

Hi @Talishask

Could we do something that is a case by case basis, like:
* If email (primary or secondary) and personal and family match = Matched Person

* If email (primary or secondary) and family match  = Matched Person _[note: since first names are usually where nick names come in]_
  Then if neither of the above for sure matching person cases exists suggest possible matches based on personal and family match?

This is definitely possible to implement.

I love this! Thanks for providing the options @Talishask . This will be great!

Hey, I have located another thing related to this issue, so I hope it is okay to add it here. Let me know if a new issue should be created.
Currently, Case sensitive matching of the Host institution and possibly also names is blocking matching. Here is one workshop submission that did not match a host institution because the name in AMY used all lowercase and the person used mixed cases in their submission. Although these should have matched at least based on the URL of the organisation.

https://amy.carpentries.org/requests/selforganised_submission/815/

I think I noticed the similar thing for names. Is this something we can update?

Tagging @lauryndbrown  and @fmichonneau  in this also, as this relates to creating new Person profiles and the consents required for doing so.  Is there anything we should consider from that perspective?


Installing problem

I try to install this extension and get the next:
D:\Projects\quasor\qsanche>quasar ext add ssg
App · Installing "ssg" Quasar App Extension
App · Retrieving "quasar-app-extension-ssg"...
App · [sync] Running "npm install --save-dev quasar-app-extension-ssg"
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t https://github.com/freddy38510/critters.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
App · ⚠  Command "npm" failed with exit code: 1
App · ⚠  Failed to install quasar-app-extension-ssg

@shaxper It seems that you need to install Git on your system.
I guess that you are on Windows, you can follow this guide.


Update edit-report-filter.md

Fixed a typo on L26, changed commbar bar to command bar

Learn Build status updates of commit 51523d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/user/edit-report-filter.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 85a402f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerapps-docs/user/edit-report-filter.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


[Create New Issue]: K means algorithm

Description
There will be brief theory along with code examples for defining k means algorithm  and how we can use this to solve real life problems.
Domain
Datascience with Python
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

This issue is already done. If you want audio / video you can comment on the respective issue. So this issue has to be closed.
@shreyarai05


Add device_class to example templates in readme

This fixes the energy dashboard complaining about not knowing what sort of device class these templates are using.

Thanks.


Revise docs for Mailboxes

Although there are few grammar and code changes, a lot of this is subjective.
Some of it is even formatting style. (I really dislike surround code with
parens; it looks very lisp-y.) Hopefully there are some changes you like, and we
can go back and forth until we work something out.

Overcome by #315 and elm-lang/elm-plans#7.


Emit login logout event on rootscope

Sending login/logout events on rootscope could be convenient.

+1

There was a discussion about $rootScope in the past but I think it was decided not to go through with it: https://github.com/sahat/satellizer/issues/152 and https://github.com/sahat/satellizer/issues/55
Don't know if you guys can tell, but there are a lot of open issues, and with my limited time on this project I would rather fix existing issues than work on adding new features that could potentially break something else.


Hard crash which doesn't get logged

Hi @all,
I have an ASP.net Core application which crashes only on release mode. Despite having installed and configured NLog, in this special case no log information gets written to a file.
I registered a global Exception handler on Startup:
public class Startup
{
	private static NLog.Logger logger = NLog.LogManager.GetCurrentClassLogger();

	// ...

	public void Configure(IApplicationBuilder app, IHostingEnvironment env)
	{
		if (env.IsDevelopment())
		{
			app.UseDeveloperExceptionPage();
		}

		app.UseMvc();

		app.UseExceptionHandler(
		 options => {
			 options.Run(
			 async context =>
			 {
				 context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
				 context.Response.ContentType = "text/html";
				 var ex = context.Features.Get<IExceptionHandlerFeature>();
				 if (ex != null)
				 {
					 var err = $"
Error: {ex.Error.Message}
{ex.Error.StackTrace }";
					 await context.Response.WriteAsync(err).ConfigureAwait(false);
					 logger.Fatal(ex);
				 }
			 });
		 }
		);
	}
}

In Program I register NLog as logger:
public class Program
{
	public static void Main(string[] args)
	{
		// NLog: setup the logger first to catch all errors
		var logger = LogManager.LoadConfiguration("nlog.config").GetCurrentClassLogger();
		try
		{
			logger.Debug("init main");
			BuildWebHost(args).Run();
		}
		catch (Exception ex)
		{
			//NLog: catch setup errors
			logger.Error(ex, "Stopped program because of exception");
			throw;
		}
		finally
		{
			// Ensure to flush and stop internal timers/threads before application-exit (Avoid segmentation fault on Linux)
			NLog.LogManager.Shutdown();
		}
	}

	public static IWebHost BuildWebHost(string[] args)
	{
		return WebHost.CreateDefaultBuilder(args)
			.UseStartup<Startup>()
			.UseKestrel(options =>
			{
				options.Listen(IPAddress.Any, 55555)
			.UseNLog()  // NLog: setup NLog for Dependency injection
			.Build();
	}
}

My nlog.config:
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      internalLogLevel="info"
      internalLogFile="c:\temp\internal-nlog.txt">

  <targets>

    <target xsi:type="File" name="allfile" fileName="QlcLog-All-${shortdate}.log"
            layout="${longdate}|${event-properties:item=EventId_Id}|${uppercase:${level}}|${logger}|${message} ${exception:format=tostring}" />

    <target xsi:type="File" name="ownFile-web" fileName="QlcLog-Own-${shortdate}.log"
            layout="${longdate}|${event-properties:item=EventId_Id}|${assembly-version}|${uppercase:${level}}|${logger}|${callsite}|${callsite-linenumber}|${message} ${exception:format=tostring}|url: ${aspnet-request-url}|action: ${aspnet-mvc-action}" />
  </targets>

  <rules>

    <logger name="*" minlevel="Error" writeTo="allfile" />

    <logger name="Microsoft.*" maxLevel="Error" final="true" />

    <logger name="*" minlevel="Warn" writeTo="ownFile-web" />
  </rules>

  <extensions>
    <add assembly="NLog.Web.AspNetCore"/>
  </extensions>
</nlog>

When an Exception occurs, normally I see them in the console and in the log file, but as I said: Sometimes I get a hard crash in release mode and nothing gets written.
I speculate, that this might be caused by unmanaged code which I use indirectly (SQLite encryption lib).
Never the less: I think that Kestrel shouldn't crash without logs. Is there any way to get the stack trace?
These are the relevant package versions which I use.
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.6" />
<PackageReference Include="Microsoft.AspNetCore.Server.Kestrel" Version="2.0.2" />
<PackageReference Include="Microsoft.AspNetCore.Server.Kestrel.Https" Version="2.0.2" />

Thanks in advance!

Never the less: I think that Kestrel shouldn't crash without logs. Is there any way to get the stack trace?

Kestrel is a library in your application, it doesn't crash, your application is crashing. If you crash on a background thread (non request thread) there's nothing kestrel can do to save you.
The usual suspects are async void methods or fire and forget style operations being started from request threads then crashing.

Ok, thx. I'm closing this issue.


Autohide navbar when scrolling

Ionic version: (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ... (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When scrolling down, header keeps in place.
Expected behavior:
When scrolling a list down, header should be hidden, and scrolling up should show. Like safari, instagram, etc..
Steps to reproduce:
N/A
Related code:
Here is an example to how this was done in ionic 1: https://github.com/driftyco/ionic/issues/1381
Other information:
This issue continues this closed one - https://github.com/driftyco/ionic/issues/10482
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
 ordova CLI: 6.4.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.1
Xcode version: Not installed

This is already possible and is in out test
https://github.com/driftyco/ionic/tree/master/src/components/content/test/header-scroll
We should probably be a bit more vocal about it

Thank you, I couldn't find it before, probably didn't look for the correct thing

@mhartington
Test the code you posted and the onScroll Event is not firing for me?

Hey, this directive looks good, can I use it already or is it still in test?


Add logic that cleans the virtual services from cloud director

It deletes the virtual services belonging to the cluster that is about to be deleted
Signed-off-by: Jiri Kremser<EMAIL_ADDRESS>Checklist
~- [ ] Update changelog in CHANGELOG.md.~ (no releases yet)

Not sure if it's planned but I think we should probably make sure we delete the PVCs before the LB ?

Not sure if it's planned but I think we should probably make sure we delete the PVCs before the LB ?

How are they related?

If we kill the LB we no longer have access to the cluster to remove the disks.

We are not deleting any disk in this operator now. CAPVCD doesn't delete them via WC API too. CAPVCD deletes them from cloud-director API directly.  I didn't get the point.

the disks' leftovers in cloud director should be deleted first, the calls may be async so there can be non-deterministic order what happens first (I haven't checked). However, I don't think that deleting virtual services may be any issue and would make the cluster inaccessible. We are not cleaning the LB per se in the PR, but virtual services that are created if user creates a service that is "LBed". The LB itself will be untouched by this.
Cleaner for disks will be done in another PR (+ the order)🖖

@jkremser According to our tests, we don't need to delete volumes. They are deleted by capvcd manager somehow. Isn't it the case?

They are deleted by capvcd manager somehow. Isn't it the case?

@erkanerol it was broken on Wed so no idea, the PVs for PVCs were not able bound. But when you were showing me the issue, I recall you talking about some leftovers from PVs. But hey, this PR is not about volumes at all, so can I get the review on this one? ;)


Adding coyote and chickens javascript multiplayer game

Describe the project you want to add with tech stack

I'd add a javascript 2-d game in which there would be a coyote whose task is to catch all of his chickens, which are scattered around the 2-d space. He moves his position, and as a result of which, the chickens also move. His task is to move as and collect all of his chickens in minimum possible steps and create high scores. This is a multiplayer game in which one user plays as coyote and the other plays as chicken. The chickens also have the option to attack coyote and reduce his health.
Screenshots (optional)

@MohitGupta121 @pranjay-poddar @TusharKesarwani please assign me this