Make cryptogen and configtxgen non-internal modules

Current Status
Both cryptogen and configtxgen import internal go modules.
Meanwhile cmd/cryptogen and cmd/configtxgen seem tightly-encoupled to using yaml files.  Using yaml files would result in decreased maintainability as the app scales up.
As there are some bits and pieces of the code in e.g., internal/cryptogen/ca, csp, msp, etc. that are useful for generating certificates, it would be nice to know the reasoning behind them being internal modules, or else would be nice to have them available publicly, such that we developers can make use of those functionalities more dynamically, without being constraint to either generating a yaml for the sake of generating crypto materials, or porting over the internal code to the project.
Expected
Both cryptogen and configtxgen are capable of importing non-internal go modules available to public.
Solution
Both cryptogen and configtxgen are capable of importing non-internal go modules available to public.
Please let us know if you plan to work on this.
If the devs don't have specific time to make this refactoring change, I would love to if you would like me to contribute.

The utility code is internal because it is not designed to be used by other consumers. Fabric repository is versioned as a set of executable binaries rather than a typical Go module that is intended to be consumed. If you build an application that depends on internal Fabric code you may experience unexpected breaking changes as Fabric evolves.
Concerning configtxgen, for programatic update of channel configuration, the intent was to utilize the library in https://github.com/hyperledger/fabric-config, and then have a set of client applications that imported the fabric-config module. Although the fabric-config library was completed, the project has not yet utilized fabric-config in other client applications, although that is still the intent for https://github.com/hyperledger/fabric-admin-sdk. You are welcome to build your own client applications around fabric-config as an alternative to the yaml-based configtxgen. Alternatively, you could collaborate on https://github.com/hyperledger/fabric-admin-sdk. Regardless, I would suggest to first look into fabric-config to see if it has libraries that you are interested in.
Cryptogen is a different story, it is intended to be a lightweight utility to generate certificates for test environments. It is not intended to be used in production networks, is limited in function, is not expected to be enhanced, and may change at any time. In a nutshell, not something I'd recommend depending on.


Update Onebranch pipelines to reference templates

Which issue this PR addresses:
Fixes https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/9772377
What this PR does / why we need it:
These changes will reduce the number of pipeline definitions that will need to be updated by referencing templates. A change to the template will then be applied to all three.  However, if any jobs/stages need to be added to the base pipeline, those changes will also have to be made manually on the remaining pull/official pipeline definitions.
Test plan for issue:
Tested both development pipelines against the templates
https://msazure.visualstudio.com/AzureRedHatOpenShift/_build/results?buildId=41724395&view=results
https://msazure.visualstudio.com/AzureRedHatOpenShift/_build/results?buildId=41724291&view=results
Is there any documentation that needs to be updated for this PR?
Clean up / tech debt

@jewzaam This looks very domain specific. Ok to merge but need to make sure we have all the knowhow in the team as we will get into same issue as with our old pipelines where it so complicated and without knowhow we had to refactor.

/avp run CI

/azp run CI

/azp run E2E

/azp run CI

@mjudeikis we have a meeting getting setup to share knowledge in this space.  If you're OK with merging could you take care of that in your day tomorrow?  I wanted to look at this today but have run out of time.  Thank you!

@jewzaam sorry gh notifiations got filled :D


What is a math pad?

@designsaves has been auditing the current interface and preparing for upcoming front-end work. We couldn't access the math pad feature that is described in this PR https://github.com/ipfs-shipyard/peer-pad-core/pull/2. It looks like the work has already been done in the code though. Is this a feature that you'd like to keep? cc @pgte

A math pad is a markdown pad that accept the markdown math extensions.
It's currently available in production by choosing "Math pad" in the pad type dropdown:

Yes, I would like to keep this feature.


Background-grid/debug doesnt work

I get a bus error: 10, when I have both of these in my scss file. Any help on getting this to work would be great. Below is my scss:
@include add-grid(12);
@include add-gutter(1/3);
@include sgs-change('debug',true);

.container {
    @include background-grid;
}

I can create grids, I just can't get the background grid to show up...

Duplicate of #211


I believe it is working

Overview
This PR creates a django command python manage.py toggle.
The toggle command queries the github api for all repositories which has the topic:civictechindex.
It loops through the entire database organization table.

For any matching orgnization name from the api call that exist in the database

it sets the cti_contributor column value to true

For organization name in the database that does not exist in the rv of the api call

it sets the cti_contributor column value to true

Lastly for any organization name from the api call that does not exist in the db
Not fully implemented yet. Will be implemented after approval and review of the above two sections

it creates a new github issue listing out the names of the organization that needs to be added to the db

toggle function logs
root@c27c5c39fa43:/code# cat manage_toggle.log
INFO: 2021-05-01 05:55:56,904 ==========Script Start==========
INFO: 2021-05-01 05:56:05,187 civictechindex ogranizations from api call -> [['100 Automations', 'BetaNYC', 'Civic Tech Index', 'Code for Buffalo', 'Code for Chapel Hill', 'Code for PDX', 'Code for Tulsa', 'EnCiv', 'Hack for LA', "Hack for LA's Sandbox", 'OpenOakland', 'Yale OpenLab']]
INFO: 2021-05-01 05:56:05,201 org [BetaNYC] in database exist in org name from api and db value is false, so it is being set to true
INFO: 2021-05-01 05:56:05,212 org [Code for Buffalo] in database exist in org name from api and db value is false, so it is being set to true
INFO: 2021-05-01 05:56:05,215 org [Code for Chapel Hill] in database exist in org name from api and db value is false, so it is being set to true
INFO: 2021-05-01 05:56:05,217 org [Code for PDX] in database exist in org name from api and db value is false, so it is being set to true
INFO: 2021-05-01 05:56:05,219 org [Code for Tulsa] in database exist in org name from api and db value is false, so it is being set to true
INFO: 2021-05-01 05:56:05,221 org [Hack for LA] in database exist in org name from api and db value is false, so it is being set to true
INFO: 2021-05-01 05:56:05,223 Created new issue for organization [['100 Automations', 'Civic Tech Index', 'EnCiv', "Hack for LA's Sandbox", 'OpenOakland', 'Yale OpenLab']]
INFO: 2021-05-01 05:56:05,224 ==========Script End==========
INFO: 2021-05-01 05:56:08,498 ==========Script Start==========
INFO: 2021-05-01 05:56:15,772 civictechindex ogranizations from api call -> [['100 Automations', 'BetaNYC', 'Civic Tech Index', 'Code for Buffalo', 'Code for Chapel Hill', 'Code for PDX', 'Code for Tulsa', 'EnCiv', 'Hack for LA', "Hack for LA's Sandbox", 'OpenOakland', 'Yale OpenLab']]
INFO: 2021-05-01 05:56:15,785 org [BetaNYC] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:15,785 org [Code for Buffalo] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:15,786 org [Code for Chapel Hill] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:15,786 org [Code for PDX] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:15,786 org [Code for Tulsa] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:15,787 org [Hack for LA] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:15,787 Created new issue for organization [['100 Automations', 'Civic Tech Index', 'EnCiv', "Hack for LA's Sandbox", 'OpenOakland', 'Yale OpenLab']]
INFO: 2021-05-01 05:56:15,787 ==========Script End==========
INFO: 2021-05-01 05:56:18,342 ==========Script Start==========
INFO: 2021-05-01 05:56:25,377 civictechindex ogranizations from api call -> [['100 Automations', 'BetaNYC', 'Civic Tech Index', 'Code for Buffalo', 'Code for Chapel Hill', 'Code for PDX', 'Code for Tulsa', 'EnCiv', 'Hack for LA', "Hack for LA's Sandbox", 'OpenOakland', 'Yale OpenLab']]
INFO: 2021-05-01 05:56:25,386 org [BetaNYC] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:25,386 org [Code for Buffalo] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:25,387 org [Code for Chapel Hill] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:25,387 org [Code for PDX] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:25,387 org [Code for Tulsa] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:25,387 org [Hack for LA] in database exist in org name from api and db value is true, remove org from civictechindex_org_container
INFO: 2021-05-01 05:56:25,388 Created new issue for organization [['100 Automations', 'Civic Tech Index', 'EnCiv', "Hack for LA's Sandbox", 'OpenOakland', 'Yale OpenLab']]
INFO: 2021-05-01 05:56:25,388 ==========Script End==========

db output
cti=# SELECT id,name,github_name,cti_contributor FROM data_organization WHERE cti_contributor='t';
 id  |         name         |     github_name      | cti_contributor
-----+----------------------+----------------------+-----------------
  40 | Code for Tulsa       | codefortulsa         | t
  18 | Code for Buffalo     | CodeForBuffalo       | t
  41 | Code for PDX         | codeforpdx           | t
 124 | Hack for LA          | hackforla            | t
  17 | BetaNYC              | betanyc              | t
  22 | Code for Chapel Hill | code-for-chapel-hill | t
(6 rows)

@cnk all the changes requested sounds good. I will remove logging and apply stdout writes as well as make the if statement nested.

@cnk Implemented change request as above. Ready for review


Docker build fails :(

Hi! thanks for making great book 👍
but... I think docker build fails on latest master
I'm on mac os monterey 12.3
docker-compose build web
[+] Building 175.8s (10/11)
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 189B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/python:3.8                                                                                4.0s
 => [auth] library/python:pull token for registry-1.docker.io                                                                                0.0s
 => [1/6] FROM docker.io/library/python:3.8@sha256:f9af3c8c4614d955495d23a665760abe3b37d4310bf9c33ea1ebf9f18991d8fe                                                                                92.8s
 => => resolve docker.io/library/python:3.8@sha256:f9af3c8c4614d955495d23a665760abe3b37d4310bf9c33ea1ebf9f18991d8fe                                                                                0.0s
 => => sha256:f9af3c8c4614d955495d23a665760abe3b37d4310bf9c33ea1ebf9f18991d8fe 1.86kB / 1.86kB                                                                                0.0s
 => => sha256:fa2a4081e81d2ac65a9e622ede295f84e18cb0359a588bbea4105dd69faf7bfd 2.22kB / 2.22kB                                                                                0.0s
 => => sha256:8022b074731d9ecee7f4fba79b993920973811dda168bbc08636f18523b90122 53.70MB / 53.70MB                                                                                43.4s
 => => sha256:91a934163d324049bba626dc29942dc17df1ee0646c8491ec08339e6c0fa06c7 7.95kB / 7.95kB                                                                                0.0s
 => => sha256:7971239fe1d69763272ccc0b2527efa95547d37c53630ed0a71db4e00d3ef964 5.15MB / 5.15MB                                                                                3.6s
 => => sha256:26c861b53509d61c37240d2f80efb3a351d2f1d7f4f8e8ec2e5004c1d86af89c 10.87MB / 10.87MB                                                                                12.1s
 => => sha256:1714880ecc1c021a5f708f4369f91d3c2c53b998a56d563d0a9aa9be2488d794 54.68MB / 54.68MB                                                                                38.0s
 => => sha256:895a945a1f9ba441c2748501c4d46569edfbc2bfbdb9b47d41e753e752247fdc 189.73MB / 189.73MB                                                                                87.2s
 => => sha256:2a83fe9e3053a5f52e699f1078c2abeaad849bb81da9068f1aa541bb5673a21f 6.40MB / 6.40MB                                                                                42.5s
 => => sha256:9fab1e817d7e301293133a70df52de98c881db200f6a87c508354aba37c202ab 15.47MB / 15.47MB                                                                                47.8s
 => => extracting sha256:8022b074731d9ecee7f4fba79b993920973811dda168bbc08636f18523b90122                                                                                1.7s
 => => sha256:a5cd1ca01318d087b11fd017b43646eabfeea1199d9c088c9d93c09118cc4b94 244B / 244B                                                                                43.7s
 => => sha256:24c24e538c8de9c742de4d3d71ecb4bf81f5748f9c79c246517856eaa0e63f83 2.91MB / 2.91MB                                                                                47.8s
 => => extracting sha256:7971239fe1d69763272ccc0b2527efa95547d37c53630ed0a71db4e00d3ef964                                                                                0.2s
 => => extracting sha256:26c861b53509d61c37240d2f80efb3a351d2f1d7f4f8e8ec2e5004c1d86af89c                                                                                0.3s
 => => extracting sha256:1714880ecc1c021a5f708f4369f91d3c2c53b998a56d563d0a9aa9be2488d794                                                                                2.1s
 => => extracting sha256:895a945a1f9ba441c2748501c4d46569edfbc2bfbdb9b47d41e753e752247fdc                                                                                4.5s
 => => extracting sha256:2a83fe9e3053a5f52e699f1078c2abeaad849bb81da9068f1aa541bb5673a21f                                                                                0.2s
 => => extracting sha256:9fab1e817d7e301293133a70df52de98c881db200f6a87c508354aba37c202ab                                                                                0.4s
 => => extracting sha256:a5cd1ca01318d087b11fd017b43646eabfeea1199d9c088c9d93c09118cc4b94                                                                                0.0s
 => => extracting sha256:24c24e538c8de9c742de4d3d71ecb4bf81f5748f9c79c246517856eaa0e63f83                                                                                0.1s
 => [internal] load build context                                                                                38.2s
 => => transferring context: 349.84MB                                                                                38.1s
 => [2/6] RUN mkdir /code                                                                                0.5s
 => [3/6] WORKDIR /code                                                                                0.0s
 => [4/6] COPY requirements.txt /code/                                                                                0.0s
 => ERROR [5/6] RUN pip install -r requirements.txt                                                                                78.2s
------
 > [5/6] RUN pip install -r requirements.txt:
#0 1.107 Collecting appdirs==1.4.3
#0 1.170   Downloading appdirs-1.4.3-py2.py3-none-any.whl (12 kB)
#0 1.198 Collecting boto==2.49.0
#0 1.211   Downloading boto-2.49.0-py2.py3-none-any.whl (1.4 MB)
#0 1.455      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.4/1.4 MB 5.8 MB/s eta 0:00:00
#0 1.765 Collecting boto3==1.9.45
#0 1.861   Downloading boto3-1.9.45-py2.py3-none-any.whl (128 kB)
#0 1.880      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 128.5/128.5 KB 8.7 MB/s eta 0:00:00
#0 2.272 Collecting botocore==1.12.45
#0 2.283   Downloading botocore-1.12.45-py2.py3-none-any.whl (4.8 MB)
#0 3.706      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.8/4.8 MB 3.4 MB/s eta 0:00:00
#0 3.969 Collecting bz2file==0.98
#0 4.001   Downloading bz2file-0.98.tar.gz (11 kB)
#0 4.010   Preparing metadata (setup.py): started
#0 4.211   Preparing metadata (setup.py): finished with status 'done'
#0 4.238 Collecting certifi==2018.10.15
#0 4.250   Downloading certifi-2018.10.15-py2.py3-none-any.whl (146 kB)
#0 4.277      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 146.3/146.3 KB 5.5 MB/s eta 0:00:00
#0 4.295 Collecting chardet==3.0.4
#0 4.330   Downloading chardet-3.0.4-py2.py3-none-any.whl (133 kB)
#0 4.371      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.4/133.4 KB 3.4 MB/s eta 0:00:00
#0 4.397 Collecting cycler==0.10.0
#0 4.441   Downloading cycler-0.10.0-py2.py3-none-any.whl (6.5 kB)
#0 4.525 Collecting Django==2.2.27
#0 4.570   Downloading Django-2.2.27-py3-none-any.whl (7.5 MB)
#0 7.795      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.5/7.5 MB 2.3 MB/s eta 0:00:00
#0 7.854 Collecting django-extensions==2.1.3
#0 8.196   Downloading django_extensions-2.1.3-py2.py3-none-any.whl (216 kB)
#0 8.326      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 216.4/216.4 KB 1.7 MB/s eta 0:00:00
#0 8.361 Collecting docutils==0.14
#0 8.396   Downloading docutils-0.14-py3-none-any.whl (543 kB)
#0 8.677      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 543.2/543.2 KB 1.9 MB/s eta 0:00:00
#0 8.998 Collecting gensim==3.6.0
#0 9.010   Downloading gensim-3.6.0.tar.gz (23.1 MB)
#0 17.28      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 23.1/23.1 MB 3.5 MB/s eta 0:00:00
#0 17.67   Preparing metadata (setup.py): started
#0 25.31   Preparing metadata (setup.py): finished with status 'done'
#0 25.34 Collecting idna==2.7
#0 25.35   Downloading idna-2.7-py2.py3-none-any.whl (58 kB)
#0 25.37      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 58.2/58.2 KB 6.1 MB/s eta 0:00:00
#0 25.39 Collecting jmespath==0.9.3
#0 25.40   Downloading jmespath-0.9.3-py2.py3-none-any.whl (23 kB)
#0 25.49 Collecting kiwisolver==1.0.1
#0 25.50   Downloading kiwisolver-1.0.1.tar.gz (31 kB)
#0 25.52   Preparing metadata (setup.py): started
#0 25.62   Preparing metadata (setup.py): finished with status 'done'
#0 25.79 Collecting matplotlib==3.0.2
#0 25.80   Downloading matplotlib-3.0.2.tar.gz (36.5 MB)
#0 44.07      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 36.5/36.5 MB 2.0 MB/s eta 0:00:00
#0 45.03   Preparing metadata (setup.py): started
#0 46.20   Preparing metadata (setup.py): finished with status 'done'
#0 46.35 Collecting numpy==1.22.2
#0 46.37   Downloading numpy-1.22.2-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (13.4 MB)
#0 52.46      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 13.4/13.4 MB 2.2 MB/s eta 0:00:00
#0 52.66 Collecting pandas==1.4.1
#0 52.68   Downloading pandas-1.4.1-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (11.0 MB)
#0 56.84      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.0/11.0 MB 2.6 MB/s eta 0:00:00
#0 56.90 Collecting packaging==16.8
#0 56.91   Downloading packaging-16.8-py2.py3-none-any.whl (23 kB)
#0 56.96 Collecting pyparsing==2.3.0
#0 56.96   Downloading pyparsing-2.3.0-py2.py3-none-any.whl (59 kB)
#0 56.98      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.0/59.0 KB 7.8 MB/s eta 0:00:00
#0 57.00 Collecting python-dateutil==2.8.2
#0 57.04   Downloading python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
#0 57.12      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 247.7/247.7 KB 3.3 MB/s eta 0:00:00
#0 57.18 Collecting pytz==2021.3
#0 57.20   Downloading pytz-2021.3-py2.py3-none-any.whl (503 kB)
#0 57.50      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 503.5/503.5 KB 1.6 MB/s eta 0:00:00
#0 57.61 Collecting requests==2.20.1
#0 57.62   Downloading requests-2.20.1-py2.py3-none-any.whl (57 kB)
#0 57.63      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 58.0/58.0 KB 4.8 MB/s eta 0:00:00
#0 57.65 Collecting s3transfer==0.1.13
#0 57.66   Downloading s3transfer-0.1.13-py2.py3-none-any.whl (59 kB)
#0 57.69      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.6/59.6 KB 2.1 MB/s eta 0:00:00
#0 57.85 Collecting scipy==1.8.0
#0 57.86   Downloading scipy-1.8.0-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (39.0 MB)
#0 75.04      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 39.0/39.0 MB 2.5 MB/s eta 0:00:00
#0 75.12 Collecting seaborn==0.8.1
#0 75.13   Downloading seaborn-0.8.1.tar.gz (178 kB)
#0 75.27      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 178.9/178.9 KB 1.3 MB/s eta 0:00:00
#0 75.29   Preparing metadata (setup.py): started
#0 75.39   Preparing metadata (setup.py): finished with status 'done'
#0 75.41 Collecting six==1.11.0
#0 75.42   Downloading six-1.11.0-py2.py3-none-any.whl (10 kB)
#0 75.44 Collecting sklearn==0.0
#0 75.45   Downloading sklearn-0.0.tar.gz (1.1 kB)
#0 75.46   Preparing metadata (setup.py): started
#0 75.56   Preparing metadata (setup.py): finished with status 'done'
#0 75.80 Collecting smart-open==1.7.1
#0 75.82   Downloading smart_open-1.7.1.tar.gz (38 kB)
#0 75.83   Preparing metadata (setup.py): started
#0 75.94   Preparing metadata (setup.py): finished with status 'done'
#0 76.18 Collecting stop-words==2<IP_ADDRESS>
#0 76.33   Downloading stop-words-2<IP_ADDRESS>.tar.gz (18 kB)
#0 76.34   Preparing metadata (setup.py): started
#0 76.46   Preparing metadata (setup.py): finished with status 'done'
#0 76.53 Collecting tqdm==4.28.1
#0 76.54   Downloading tqdm-4.28.1-py2.py3-none-any.whl (45 kB)
#0 76.55      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 46.0/46.0 KB 4.4 MB/s eta 0:00:00
#0 76.59 Collecting urllib3==1.26.5
#0 76.60   Downloading urllib3-1.26.5-py2.py3-none-any.whl (138 kB)
#0 76.63      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 138.1/138.1 KB 5.0 MB/s eta 0:00:00
#0 76.90 Collecting pyLDAvis==2.1.1
#0 76.92   Downloading pyLDAvis-2.1.1.tar.gz (1.6 MB)
#0 77.52      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.6/1.6 MB 2.7 MB/s eta 0:00:00
#0 77.59   Preparing metadata (setup.py): started
#0 77.72   Preparing metadata (setup.py): finished with status 'done'
#0 77.81 INFO: pip is looking at multiple versions of boto3 to determine which version is compatible with other requirements. This could take a while.
#0 77.81 INFO: pip is looking at multiple versions of boto to determine which version is compatible with other requirements. This could take a while.
#0 77.81 INFO: pip is looking at multiple versions of appdirs to determine which version is compatible with other requirements. This could take a while.
#0 77.81 ERROR: Cannot install -r requirements.txt (line 4) and urllib3==1.26.5 because these package versions have conflicting dependencies.
#0 77.81
#0 77.81 The conflict is caused by:
#0 77.81     The user requested urllib3==1.26.5
#0 77.81     botocore 1.12.45 depends on urllib3<1.25 and >=1.20; python_version >= "3.4"
#0 77.81
#0 77.81 To fix this you could try to:
#0 77.81 1. loosen the range of package versions you've specified
#0 77.81 2. remove package versions to allow pip attempt to solve the dependency conflict
#0 77.81
#0 77.81 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
#0 77.91 WARNING: You are using pip version 22.0.4; however, version 23.0.1 is available.
#0 77.91 You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
------
failed to solve: executor failed running [/bin/sh -c pip install -r requirements.txt]: exit code: 1

the conflict is with the urllib3 and dependency conflict of botocore depend on urllib3 ver < 1.25 . Try installing lower version of urllib3

At the end what worked for me was not to use the latest python / using now a 3.8.x worked fine for me with the other adaption mentioned.
documenting it here for someone who might also search for a solution.


Create vga controller

Sorry, but I don't understand the purpose of this pull request.
Can you explain why this should be added to the display controller?

I've not heard back in over a month, so will close this request.


I would like to have permission to publish your app on the Windows Store

Hi, I'm part of the UWP Open Source Community (https://github.com/UWP-Open-Source-Community). Our intent is to take Win32 Open Source applications and convert them into UWP apps through the Windows Bridge (Project Centennial).
We like your app and that's why we decided to convert it.
In case you would like to take charge of this app and publish it yourself on the store (make us very pleased) contact us the first possible please! Otherwise, we may be responsible for publishing your app.
If you do not want to take over the publication on the Store, can you give us permission to do so?
Sorry for my poor English.
Thanks for your help.

Thanks for your interest in Atom!
We don't have any plans on publishing Atom to the Windows Store (or any other platform's store-like feature) at this time. The primary reason being that all of them place restrictions on apps that are problematic with regard to Atom's use as a programmer's editor, whether restricting free access to the user's entire file system or restrictions on downloadable extensions like the packages made available on https://atom.io. We also feel that the Atom installer and auto-update process makes the primary benefits of the Windows Store, easy installation and updating, unnecessary.
With regard to granting permission for others to publish Atom to the Windows Store, the source code license grants you permission to fork the Atom source code. But "Atom" and the Atom logo are trademarks of GitHub, Inc and we are not granting permission for others to publish their fork using the Atom name or logo. So, no, I cannot grant permission for you to publish Atom to the Windows Store. And while, technically, you are within your rights under the license to completely rebrand the source code and publish it under a new name and logo, we believe that the users are best served obtaining Atom only through the official mechanisms, namely via https://atom.io. If you have any further questions, please feel free to contact us at<EMAIL_ADDRESS>Thanks again for reaching out!

Thank forum tour response!!!

@lee-dohm
Hi! I'm Francesco Venuti and I founded UWP Open Source Community, dgsimone15 already contacted you about UWP, but you didn't seem to understand our intentions, so let me explain better ...
We are a team of Windows lovers and developers without any scope of make money. We would only improve our OS ... in the last year Windows 10 has improved a lot, for example today also incorporates a Linux Subsystem (WSL)... Now Microsoft also engaged the mobile challenge, it seems that they would change the concept of mobile computing ... so not just a smartphone, but real desktop experience that could run on ARM devices like tablets and smartphones (connected with a monitor).
We saw the preview of "Windows Colud Edition", this could be the next edition of Windows for education PC (like Chromebooks). Unfortunately for running win32 software on this edition, the software must be converted into UniversalWindowsPlatform app; after conversion, the software could run even on regular Windows 10 editions. If this could be a problem, you should consider the opportunities like: all UWP could use a telemetry to send information about problems to developer, guarantee automatic update every time you emprove your software, could impact on a larger and younger user base that can give You feedback and also start developing your software.
Furthermore distributing your software as UWP mean that your software run in a sandbox that don't compromise the OS if there are problems.
We don't want make a copy of your work, rather we prefer YOU start publish also on Windows Store as alternative distribution to traditional installer.
We tried the online tool made by Microsoft for convert win32 software to UWP app, if you would use our work to start your experience on Microsoft Store we are pleased to give you all materials and information. Don't be scared about shadow costs, for publish on Microsoft Store you pay only the first time as developer registration, because your app will FLOSS, so there are not fee!
For us is important start Windows Cloud with a large amount of open source apps available for every one.
Scuse me for poor English...😉

Hello Francesco. I believe I understand your intentions. Thank you for the extra information. Let me address your points one at a time:

but real desktop experience that could run on ARM devices like tablets and smartphones (connected with a monitor).

The editor that we want Atom to be isn't designed for mobile devices. Though we have investigated running Atom on low-power desktop ARM devices such as the Raspberry Pi, and some community enthusiasts are building a version that works there, see https://github.com/atom/atom/issues/7822 for details.

could impact on a larger and younger user base that can give You feedback and also start developing your software.

You may be correct that building an editor that runs on a different type of device would tap into a different market or user base, but that's still not the kind of product we want to make.

use a telemetry to send information about problems to developer

We already have this via our metrics and exception-reporting packages.

guarantee automatic update every time you emprove your software

We also have this capability built-in. Additionally, we don't have to go through a third-party's review process in order to publish these updates. If we fix a bug, we can publish it right away and our users can get it the next time they launch Atom. (Or they can disable that if they want too, for example when they have to pay for bandwidth use.)

your software run in a sandbox that don't compromise the OS if there are problems.

That is actually one of the restrictions that prevents Atom from being used as a programmer's text editor that I mentioned in my previous post: "restricting free access to the user's entire file system". We agree that running in a sandbox is probably best for the majority of apps, just not for a software developer's text editor like Atom. If we wanted a sandbox, we wouldn't have invested all the effort in circumventing the built-in sandbox of the web technologies we employ to build Atom.
I appreciate your enthusiasm. Your suggestion isn't the first time we've heard this feedback. This is something that we have thought a lot about over the years, the kind of editor that we want to build, that we want Atom to be and how to best make it available to people. We don't want to make an editor for mobile devices. We do want to make Atom available to the widest reasonable audience we can on desktop-style machines, that's why we support Windows, macOS and Linux. And we already have the capabilities that you're offering on all three major desktop platforms.
Because of all of the above, we have no plans currently to offer Atom via the Windows Store (or any other platform's equivalent). Thanks again for your well-written feedback :+1:

Centennial apps (i.e. Win32 apps on Store) don't actually get sandboxed user filesystems (mostly), Atom could be put into the Windows Store and mostly work with some effort. You also don't have to go through any real review process either, it's quite fast.
That being said, I don't really see any advantage to being in the Store either other than being a dog whistle to Microsoft enthusiasts (a legitimate plus if you're targeting that market!), and it'd just be another platform that you'd have to deal with and test.

Scuse me for the duplicate.
@lee-dohm

The editor that we want Atom to be isn't designed for mobile devices. Though we have investigated running Atom on low-power desktop ARM devices such as the Raspberry Pi, and some community enthusiasts are building a version that works there, see #7822 for details.

@paulcbetts

That being said, I don't really see any advantage to being in the Store either other than being a dog whistle to Microsoft enthusiasts (a legitimate plus if you're targeting that market!), and it'd just be another platform that you'd have to deal with and test.

@lee-dohm  The only part of your tought that I'm disagree is in the underestimation of potential about Windows on arm. As you can see in the next links, Microsoft is in partnership with Qualcomm and start using ARM architecture for her servers. Microsoft has also demostrated that Windows On Arm could run Photoshop on a Snapdragon 820 processor, that is largely used on smartphones. Check it: http://www.zdnet.com/article/windows-server-on-arm-its-happening/

http://www.theverge.com/2016/12/8/13881800/microsoft-demonstrates-full-windows-10-with-photoshop-on-arm-chips
Furthermore the barrier between mobile device and personal computer is every year more tight...
check for example this solutions that use Continuum mode to transform a display or a portable display with keybord in a "traditional pc":
https://www.youtube.com/watch?v=hBU84C9tSao
this example was made with windows10mobile that is a pure mobile OS, but the next step is a complete windows experience with Windows on Arm.
Something similar is made also on Android by Samsung with DeX:
https://www.youtube.com/watch?v=G_Zdq0AjhXo
So I think you need to ask you some questions...where go the future? new generations have more affinity with apps than with pc software...when I was young the informatics students want know Linux, nowdays the students want know how write apps...
I suppose that windows is in your interests if you distribute .exe installer...so, what is the problem to distribute .appx on store?
Any other technical objection is correct, but can be overcome...

Centennial apps don't run on ARM, and WOA is mooooostly dead

@paulcbetts I'm sorry but in my opinion you are not well informed. UWP (Centennial or native) work everywhere there is a complete Windows10 experience: WindowsOnArm is a complete desktop experience and is very different from Windows10mobile(which also run on ARM). I know that in past also WindowsRT was called WoA, but actually Windows on Arm is quite different. So Centennial UWP can't run on Windows 10 Mobile but only on Windows 10 (with or without ARM architecture).
If you see the link above, you can see a regular Adobe Photoshop run on ARM, you can't distinguish a Centennial UWP from a regular desktop software when starting it!

Hi @lee-dohm ! Have you tought to the situation? I don't think that is correct see this situation like: "our Vs your vision" because there are different people needs differents solutions and not exist a correct or wrong. Are you agree?

@duble0 I've given you the answer that I have for you which is that we have no plans currently to publish Atom to the Windows Store.
It's obvious that you disagree with our reasoning but as I said before, you're not presenting anything new. The Atom maintainer team is made up of a diverse group of industry professionals, some of us have even worked at Microsoft in the past. We're aware of the trends in the industry, the shift in consumer use away from desktop-style hardware and applications to mobile-style hardware and apps [1], and the use of ARM as a processor architecture. Given all of that, we still have come to a different conclusion from you. Sometimes disagreements between equally informed, equally knowledgeable and equally experienced people do occur. This is one of those times.
[1] As a matter of fact, I even wrote a blog post seven years ago predicting this shift

Thank you @lee-dohm! An answer is ever better than silent...we are writing to others developers for other softwares, someone is interested and others, like you, don't beliving in this technology...for us isn't a terrible discovery. The important thing is that you are conscious of possibilities.


Countless results node improvements

This is definitely a pull request from a feature branch, yep
Contains a discrete number of improvements for results nodes without counts (now that we have skipCount):

Add a hasMore flag to context.response, which is determined by trying to fetch one more result than the page size dictates and seeing if we got anything
If an actual record count is not available, results nodes will now populate context.response.totalRecords with an approximation of the total using the highest-numbered endRecord seen so far (also needs an update in contexture-client to force totalRecords back to zero when the node is refreshed by someone else)
Split out the code to generate the response object into a getResponse function (mostly for testing)

Warnings

:warning:
The README has not been updated. Please update the README.

Messages

:book:
Could not find any browser results.

  Generated by :no_entry_sign: dangerJS against d148c9aee037f3a3214466b8f8dfe016a40552bd


Load and merge multiple properties files

I've browsed the props documentation and Javadocs but I don't think this is supported. I'm looking to re-write my service's configuration loader and Jodd popped up onto my radar. One thing my current loader does is it loads multiple YAML files (I'm not tied to YAML) and merges them so that the data from all files can be accessed as one.
This might be a good addition to Jodd props. I suppose the API could be:
load(String[] filenames)
or load(File[] files)
Jodd would load them all - my current loader loads 5 or 6 files, each with 10 lines or less.
The API would still work as before, but you would be pulling data from the merged configuration:
    Props p = new Props();
    p.load(new File[] { new File("example.props"), new File("example2.props") } );
    ...
    String story = p.getValue("story");

Cheers

Wait a minute! Is this already supported? I need to try it out. The answer might be in the code example I posted above:
    Props p = new Props();
    p.load(new File("example.props"));
    p.load(new File("example2.props"));
    String story = p.getValue("story");

This is how it works?

Ok, I created a test app and this functionality already exists. I didn't realise (lack of caffeine) that the "..." in the documentation meant I could load multiple files. My bad.

Hey @stodge no worries, I should make that more clear :)

No worries - I wasn't thinking straight.  :)


Do not run calico-node on AWS EKS Fargate nodes

Description
Resolves https://github.com/projectcalico/calico/issues/4731
AWS Fargate with Amazon EKS is an amazon service that allows users to run a kubernetes cluster without any standard nodes and rather use AWS Fargate (a serverless container service provided by AWS under ECS) to run the pods. These fargate nodes can only run a single pod and have many limitations as compared to normal nodes making it impossible for calico-node pods to run on them.
The node is tainted to prevent pods like typha and kube-controllers from running there, but Calico-node tolerates all taints. And this results in many pending calico pods that can never run on those nodes.
This PR sets a node affinity to prevent calico pods from being scheduled on these fargate nodes. The PR has been implemented very similar to https://github.com/tigera/operator/pull/1048 which does the same but for AKS's virtual nodes.
affinity:
  nodeAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      nodeSelectorTerms:
      - matchExpressions:
        - key: eks.amazonaws.com/compute-type
          operator: NotIn
          values:
          - fargate

For PR author

[x] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

 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.

Looks like CI is failing with this:
The following files are dirty01:12
 .../crd.projectcalico.org_kubecontrollersconfigurations.yaml   | 10 ++++++++++01:12
 1 file changed, 10 insertions(+)01:12
Makefile:359: recipe for target 'dirty-check' failed

I think this should be resolved by a rebase on master

@caseydavenport rebased the branch. All checks passed now. Thanks ! 😄


Modify dim level in Dialog

As stated, how do i change the dim level behind the dialog on IOS target?

DialogProperties.scrimColor

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


Fix grammer in defintion in chem conc yaml address #35

Unable to run sudo ./run.sh make all_modules on my mac, found these threads about how to fix it or just run it on linux. https://stackoverflow.com/questions/54421706/docker-error-error-response-from-daemon-mounts-denied-on-os-x#54422724 https://stackoverflow.com/questions/45122459/mounts-denied-the-paths-are-not-shared-from-os-x-and-are-not-known-to-docke/45123074#45123074


[P1] Control-Plane app needing 5 minutes to remove FrameSplitter POD after camera is removed from control plane app.

[UPDATED] Read the latest message. IT's working but it need 5 minutes to delete the FramrSplitter POD. We should do it in a few secs, right?
Repro:
I removed the camera that was working, it's empty now:

However, MEC-Accelerator was still getting new ALERTS, like if it didn't delete the provisioning for that camera (FRame-splitter, etc. should be deleted for that camera, right?).
It was still processing. I there are no cameras provisioned in control-plane there should not be ALERTS coming through?...

However, I think this is NOT a bug... I think there were many ALERTS queued in MQTT since it was creating many, all the time...
After a few minutes, the ALERTS stopped being created... So, I think the behavior is correct.
Please, confirm this is the case. :)

I still think that it takes too long to delete the pods processing the camera... I deleted the camera 5 minutes ago and it's still getting ALERTS... so I think it needs too much time to delete the related pods? - Please, confirm...

Once I delete the camera in the "Control Plan App", I see that the FrameSplitter related pod is still alive in K8s:

But after approximately 5 minutes, the ALERTS stop appearing and the POD is now deleted:

So, can we delete the PODs in just a few seconds instead of 5 minutes?

Answer with the AKRI issue description and we'll contact the AKRI team asking for workaround.

Let's keep it as P1 until we get an answer from the AKRI team, ok?


Create accurarcy column for one epoch

What we actually want is the precision and not the accuracy The accuracy is a measure of the overall performance of a classifier whereas the precision is a measure for comparing classifications of classes with each other.

Done with PR #24.


Capture picture over P2P

Please add an option to take a snapshot  over P2P session
Thank you!

Hi @yooo1999
I am not sure whether @bropat would like to add the necessary dependencies to his library. I would think that this is merely out of scope of this project and more a use case for projects using this library.
But then again he can say himself if he thinks otherwise.
Nevertheless I'd like to point you to this example code how we handled this requirement in the homebridge plugin. Maybe this helps you.

Agree completely with @thieren.


[jest-runtime] Allow to import native addon modules (binary files) created by node-gyp

Summary
Without this commit
NODE_OPTIONS="--es-module-specifier-resolution=node --experimental-vm-modules --experimental-modules" npm exec jest

on a .(m)js file (ESM)
export default (
  await import('../Release/SomeProject.node')
).default;

results in
    Unterminated string.
      at @:1:155

      at @:1:155
      at stringLiteral (node_modules/cjs-module-lexer/lexer.js:1262:9)
      at parseSource (node_modules/cjs-module-lexer/lexer.js:201:9)
      at parseCJS (node_modules/cjs-module-lexer/lexer.js:43:5)
      at build/src/SomeProject.js:12:17

because jest-runtime has ordered cjs-module-lexer
to parse a binary file (already converted to UTF-8 by readFile) as JavaScript.
Test plan
I've attached a nodeGypTestCase.tar.gz (997 bytes)
mkdir /tmp/nodeGypTestCase
cd /tmp/nodeGypTestCase
wget https://github.com/facebook/jest/files/9229734/nodeGypTestCase.tar.gz
tar xf nodeGypTestCase.tar.gz

then
npm install
npm run build
npm run test

or
yarn
yarn build
yarn test

I don't know whether my change is a feature or a fix, so I didn't touch the changelog.

Can you add an integration test?

I don't know whether my change is a feature or a fix, so I didn't touch the changelog.

Feature, I think 👍

@arzeth ping 🙂


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24561

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/30231

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67705


"Refused to load..."  Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.
www.hugonewbie.com/:1 Refused to load the image 'https://hugonewbie.com/apple-touch-icon.png' because it violates the following Content Security Policy directive: "img-src 'self' data:".
www.hugonewbie.com/:1 Refused to load the image 'https://hugonewbie.com/favicon-32x32.png' because it violates the following Content Security Policy directive: "img-src 'self' data:".
www.hugonewbie.com/:1 Refused to load the image 'https://hugonewbie.com/favicon-16x16.png' because it violates the following Content Security Policy directive: "img-src 'self' data:".
www.hugonewbie.com/:1 Refused to load the script 'https://hugonewbie.com/js/highlight.min.c393194……85ffc81….js' because it violates the following Content Security Policy directive: "script-src 'self'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
www.hugonewbie.com/:1 Refused to load the script 'https://hugonewbie.com/main.min.7ab5231……4f0ce75….js' because it violates the following Content Security Policy directive: "script-src 'self'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
www.hugonewbie.com/:1 Refused to load the script 'https://hugonewbie.com/index.min.503f5fc……7137d88….js' because it violates the following Content Security Policy directive: "script-src 'self'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
www.hugonewbie.com/:1 Refused to load manifest from 'https://hugonewbie.com/site.webmanifest' because it violates the following Content Security Policy directive: "manifest-src 'self'".
www.hugonewbie.com/:1 Refused to load the image 'https://hugonewbie.com/favicon-32x32.png' because it violates the following Content Security Policy directive: "img-src 'self' data:".
www.hugonewbie.com/:1 Refused to load the image 'https://hugonewbie.com/favicon-16x16.png' because it violates the following Content Security Policy directive: "img-src 'self' data:".
www.hugonewbie.com/:1 Refused to load the stylesheet 'https://hugonewbie.com/main.0d8cd4d……f7e56be….css' because it violates the following Content Security Policy directive: "style-src 'self'". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.
www.hugonewbie.com/:1 Refused to load manifest from 'https://hugonewbie.com/site.webmanifest' because it violates the following Content Security Policy directive: "manifest-src 'self'".

Steps to reproduce
deploy to netlify, after having had another documentation teme on there before (not sure if that's relevant)
Expected result
site should look right and not have all those unloadable files
Actual result
site not implementing theme, and generating a lot of "Refused to load..." errors
Environment
the netflify build command is hugo --gc --minify -b $URL
% npm run check

><EMAIL_ADDRESS>precheck
> npm version

{
  'doks-child-theme': '0.2.3',
  npm: '7.7.6',
  node: '15.14.0',
  v8: '8.6.395.17-node.28',
  uv: '1.41.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.1',
  modules: '88',
  nghttp2: '1.42.0',
  napi: '8',
  llhttp: '2.1.3',
  openssl: '1.1.1k+quic',
  cldr: '38.1',
  icu: '68.2',
  tz: '2020d',
  unicode: '13.0',
  ngtcp2: '0.1.0-DEV',
  nghttp3: '0.1.0-DEV'
}

><EMAIL_ADDRESS>check
> hugo version

hugo v0.82.1-60618210+extended darwin/amd64 BuildDate=2021-04-20T11:02:50Z VendorInfo=gohugoio

This seems related: https://github.com/h-enk/doks/pull/242

See: https://github.com/h-enk/doks/discussions/337

Alas, I had already done that. I notice that in one place I used https and in the other http. I've made them both consistent, and it doesn't seem to fix the problem :(
Might you have any other ideas? I am soooo hoping to make this work, as I like everything else about this project! I definitely want to become an adopter.

I am not familiar with Content Security Policies... but I see this line in _headers. I guess I need to figure out what this all means.
Content-Security-Policy: default-src 'self'; frame-ancestors https://jamstackthemes.dev; manifest-src 'self'; connect-src 'self'; font-src 'self'; img-src 'self' data:; script-src 'self'; style-src 'self'

I changed my baseurl to https://www.hugonewbie.com from https://hugonewbie.com and that fixed all the CSP errors. HOWEVER, my implementation of this https://github.com/h-enk/doks/discussions/343 effort to move /docs to the home page doesn't work. The original home page still appears, which is weird, because locally I was successful moving docs to the home page.


use make for typecheck

Previously, there appeared to be two ways to invoke typechecking: the Makefile and npm/package.json. This commit reduces ambiguity by moving CI typechecking to the Makefile, where all the other build steps live.

@robertknight not sure if this was actually something you had done intentionally. If so, it might be worth adding a comment?


Include language specification on website

fix #941

I get 404 when I use the try website link and click on specification and get to https://cadlwebsite.z1.web.core.windows.net/prs/1322/specification

hhm let me check

Ok works now but azure storage doesn't let you link back to that page it doesn't load without .html extension

Hmm, should we change the link to use .html? It would be more comforting and convenient if we can preview things without changing URLs.

Thing it not specific to this url, if you try to refresh teh website anywhere it fails

Doh! Ok.

Maybe file an issue to track finding a workaround?

Filled https://github.com/microsoft/cadl/issues/1324


fix: fall detection bugs

update the code to work on this issue

Hello @bhavikapanara! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/ambianic/pipeline/ai/fall_detect.py:

Line 269:25: E265 block comment should start with '# '
Line 270:25: E265 block comment should start with '# '
Line 270:80: E501 line too long (89 > 79 characters)
Line 271:80: E501 line too long (83 > 79 characters)

In the file src/ambianic/pipeline/store.py:

Line 100:29: E128 continuation line under-indented for visual indent
Line 101:29: E128 continuation line under-indented for visual indent
Line 102:29: E128 continuation line under-indented for visual indent
Line 117:80: E501 line too long (82 > 79 characters)
Line 118:29: E128 continuation line under-indented for visual indent
Line 119:29: E128 continuation line under-indented for visual indent
Line 120:29: E128 continuation line under-indented for visual indent
Line 217:49: W292 no newline at end of file

In the file tests/pipeline/test_store.py:

Line 207:1: E302 expected 2 blank lines, found 1

Hello @bhavikapanara! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/ambianic/pipeline/ai/fall_detect.py:

Line 269:25: E265 block comment should start with '# '
Line 270:25: E265 block comment should start with '# '
Line 270:80: E501 line too long (89 > 79 characters)
Line 271:80: E501 line too long (83 > 79 characters)

In the file src/ambianic/pipeline/store.py:

Line 100:29: E128 continuation line under-indented for visual indent
Line 101:29: E128 continuation line under-indented for visual indent
Line 102:29: E128 continuation line under-indented for visual indent
Line 117:80: E501 line too long (82 > 79 characters)
Line 118:29: E128 continuation line under-indented for visual indent
Line 119:29: E128 continuation line under-indented for visual indent
Line 120:29: E128 continuation line under-indented for visual indent
Line 217:49: W292 no newline at end of file

In the file tests/pipeline/test_store.py:

Line 207:1: E302 expected 2 blank lines, found 1

Two main issues here:

We need to discuss and define a new data format that the edge and UI can agree on for passing detection event information. @muka your input would be welcome here.
Fall detection tests should cover all key parameters, such as keypoints. Look at the test coverage report and see what other code logic we may not be testing for.

@ivelin
Can you please finalize a data format for fall detection?


E2E tests on testnet

Issue Number
ADP-607
Overview
Moving E2E tests from https://github.com/piotr-iohk/cardano-wallet-rb to cardano-wallet.
Comments

only e2e tests of cardano-wallet are moved, any tests related only to cardano-wallet-rb are not moved here.
the ruby wrapper over cardano-wallet stays for now in original repository https://github.com/piotr-iohk/cardano-wallet-rb

Any testnet wallets required for needed for these testcaes ought to be defined in an external file which is loaded as a github actions secret. Empty wallets for testing should be generated from new mnemonics each time.

That's the case for empty wallets. Advantage of having mnemonics for other fixture wallets in code is that all tests can be easily run locally.

It looks like many test cases are quite similar to what we already have in the hspec integration tests. I would be inclined to drop any rspec tests which are the same as a hspec test. (Perhaps in a subsequent PR though).

Yes. I think some can be dropped.

Using this, we should be able able to replace all the manual tests with rspec tests, right? (Except for test/manual/FlakyTest.md, but I don't think that one has much value anyway).

I think it mainly extends coverage by running e2e tests in conditions closer to mainnet. Those manual tests are mostly corner cases that are cumbersome to automate. Those e2e tests touch on some aspects of those manual tests (like SyncingInByronEra.md) but they do not replace them 1-1.

We could/should use the real testnet token metadata server in these tests right?

Yes, that's the goal.

There is a file with a big list of addresses - is that needed?

That's used by one test importing 130k addresses to Byron wallet. I think it can be dropped, as there is similar test in local integration suite.

If the fixture wallet mnemonics are checked in to git, then anyone could mess with them and make our tests fail.
It's possible to have the fixture wallets in a separate file, not checked in.
I am sure we can automate those manual tests. They are also cumbersome to run manually - especially on 3 platforms.

Is it possible to configure the directory where data is stored?
I usually prefer to keep chain dbs, etc outside of my git work tree.

If the fixture wallet mnemonics are checked in to git, then anyone could mess with them and make our tests fail.
It's possible to have the fixture wallets in a separate file, not checked in.

Ok, fair enough. :+1: I'll change this.

Is it possible to configure the directory where data is stored?
I usually prefer to keep chain dbs, etc outside of my git work tree.

Yes, via env variables NODE_DB and WALLET_DB, there's this script checked in illustrates this -> https://github.com/input-output-hk/cardano-wallet/blob/da0349b67fd1fdb398a7fdbe06e7cbed72cdeb50/test/e2e/run_all_tests but I'll add a note to readme.

I am sure we can automate those manual tests. They are also cumbersome to run manually - especially on 3 platforms.

Yeah, probably they can be automated but I'm not sure about the cost vs. benefit, because they are a bit specific. For the release I'll still would like to run some smoke/sanity manual tests on each platform.

@rvl it seems I don't have permissions to define GH actions secrets on cardano-wallet repo. Can you give me permissions?

bors r+

bors retry


Update sample app

thanks for the update! 👍
Saw this PR after I edited README. mind rebase again? and then I will merge ;)

rebased

👍


ci change gitlab runner for benchmarking

This PR changes GitLab runners where benchmarks will be executed on. Those linux-docker-bench runners specially tuned to have only 1 active job running at a time so must provide more trustworthy results

CRITERION BENCHMARKS

BENCHMARK
MASTER
PR
Diff

compile_and_validate_v1
7.0358 ms
7.0205 ms
:white_circle:  +0.1364%

execute_count_until_v1
3.9306 ms
3.9322 ms
:white_circle:  +0.3779%

execute_factorial_iterative_v1
2.0438 µs
2.0457 µs
:white_circle:  +0.3835%

execute_factorial_recursive_v1
2.2990 µs
2.3029 µs
:white_circle:  -0.0152%

execute_fib_iterative_v1
12.198 ms
12.204 ms
:white_circle:  -0.0292%

execute_fib_recursive_v1
20.440 ms
20.699 ms
:red_circle:  +1.2131%

execute_global_bump_v1
5.0551 ms
4.8562 ms
:green_circle:  -3.9487%

execute_host_calls_v1
35.062 µs
33.902 µs
:white_circle:  -0.0991%

execute_memory_fill_v1
10.442 ms
10.585 ms
:red_circle:  +1.3429%

execute_memory_sum_v1
9.4550 ms
9.4621 ms
:white_circle:  +0.0358%

execute_memory_vec_add_v1
18.964 ms
19.147 ms
:white_circle:  +0.9117%

execute_recursive_is_even_v1
3.3662 ms
3.3423 ms
:white_circle:  -0.8200%

execute_recursive_ok_v1
418.36 µs
405.71 µs
:green_circle:  -3.1975%

execute_recursive_scan_v1
535.93 µs
536.84 µs
:white_circle:  +0.3163%

execute_recursive_trap_v1
40.114 µs
40.990 µs
:red_circle:  +2.3151%

execute_regex_redux_v1
3.7546 ms
3.7981 ms
:white_circle:  +0.9617%

execute_rev_complement_v1
3.6017 ms
3.6034 ms
:white_circle:  +0.0234%

execute_tiny_keccak_v1
3.1851 ms
3.1792 ms
:white_circle:  -0.1571%

execute_trunc_f2i_v1
4.3550 ms
4.3300 ms
:white_circle:  -0.5293%

instantiate_v1
77.544 µs
76.619 µs
:white_circle:  -1.0918%

Link to pipeline


Use standalone GMock, fix docker builds.

Fixes the GMock issue for all Docker builds.
This the follow up for https://github.com/googlecartographer/cartographer/pull/1017.
FIXES=#776

Note that this drops Ninja support for ROS Indigo. (The docker file builds with Make.)

Abandoned in favor of https://github.com/googlecartographer/cartographer/pull/1011


MavenParser should support profile activation mechanism

Within a maven settings.xml maven users may specify that a profile is active when a particular file is present on the filesystem at build time.
A settings.xml I received from design partner 1 has a profile that makes use of this feature, but in an unimportant profile not relevant to our scenarios. As such this is currently a low priority issue for us.

What is the priority of this issue? Are they blocked without this?


[Bug] Use qualified names in snowflake__get_rename_x_sql macros

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The snowflake__get_rename_x_sql macros are using unqualified names for the rename target. This ultimately led to an error in #1016 — although I'm glad it did, because if it hadn't, it might have masked the real underlying issue, which is that dbt can no longer recognizes dynamic tables based on the output of show terse objects and is full-refreshing them on every run.
Still, I would expect that these macros return:
alter table "ANALYTICS"."DBT_JCOHEN_DEV"."MY_DYNAMIC_TABLE" rename to "ANALYTICS"."DBT_JCOHEN_DEV".MY_DYNAMIC_TABLE__dbt_backup;

Instead:
alter table "ANALYTICS"."DBT_JCOHEN_DEV"."MY_DYNAMIC_TABLE" rename to MY_DYNAMIC_TABLE__dbt_backup;

Expected Behavior
{%- macro snowflake__get_rename_table_sql(relation, new_name) -%}
    alter table {{ relation }} rename to {{ relation.incorporate(path={"identifier": new_name}) }}
{%- endmacro -%}

{%- macro snowflake__get_rename_view_sql(relation, new_name) -%}
    alter view {{ relation }} rename to {{ relation.incorporate(path={"identifier": new_name}) }}
{%- endmacro -%}

Steps To Reproduce
Reproduction case in #1016 — the specific error actually surfaces because the temp relation being dropped (qualified name) does not match the temp relation being created (unqualified name)
Relevant log output
08:31:27  On model.my_dbt_project.foo_2024_03_enabled: /* {"app": "dbt", "dbt_version": "1.7.14", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo_2024_03_enabled"} */
-- get the standard backup name

    -- drop any pre-existing backup

        drop table if exists "DEVELOPMENT_JYEO"."DBT_JYEO"."FOO_2024_03_ENABLED__dbt_backup" cascade

;
08:31:27  Opening a new connection, currently in state closed
08:31:29  SQL status: SUCCESS 1 in 2.0 seconds
08:31:29  Using snowflake connection "model.my_dbt_project.foo_2024_03_enabled"
08:31:29  On model.my_dbt_project.foo_2024_03_enabled: /* {"app": "dbt", "dbt_version": "1.7.14", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo_2024_03_enabled"} */
alter table "DEVELOPMENT_JYEO"."DBT_JYEO"."FOO_2024_03_ENABLED" rename to FOO_2024_03_ENABLED__dbt_backup;
08:31:29  Snowflake adapter: Snowflake query id: 01b413bf-0804-98fe-000d-3783323f397a
08:31:29  Snowflake adapter: Snowflake error: 002002 (42710): SQL compilation error:
Object 'FOO_2024_03_ENABLED__DBT_BACKUP' already exists.

Environment
- OS: 14.4.1
- Python: 3.10.11
- dbt-core: 1.8.0
- dbt-snowflake: 1.8.0

Additional Context
No response

Hi @mikealfare. I still see error Object '{{name}}__DBT_BACKUP' already exists, and I'm using dbt-snowflake v1.8.3.
I see that this issue has been closed completed though, whereas this issue is still open: https://github.com/dbt-labs/dbt-snowflake/issues/1103
Are these not related?


Privatize funcs

Make some internals private because these particular internals, related to URL fetching and pagination, could easily get refactored away.

:+1:


[Proposal] add new types of scopes

Hello,
i think it would be useful to add another type of scopes, currently, it's used to add a condition to the query,
but i think we could have scopes for other things that the query.
For example we could have a CheckboxHtmlScope, to add checkboxes when we need to, without having to do if statements in DataTables to know if checkboxes needs to be enabled or not.
we could have a SkipPagingAjaxScope for example to skip pagination when we need to, on any datatable we want.
to summarize, i think we could have :

QueryScopes
AjaxScopes
HtmlScopes

and in the datatable,
we could have
return $this->applyQueryScopes($query);
return $this->applyAjaxScopes($datatable);
return $this->applyHtmlScopes($builder);

for example.
what do you think ?

Sorry for late reply. The idea looks good. Can you please submit a PR for POC? I may not be able to do some updates atm. Thanks!


Mapping compatible with Surge XT

I think it's microtuned octaves per channel.

I think we have solved this by sending channels and then it can be addressed in a synth's callback function if desired...


solved assignment problem w/ env_id

This solves #79 .
The variable env_id was called before it was assigned.
I solved this by assigning env_id before it was called. See #79 for details.

Code changes:
# Create the evaluation env
eval_env = DummyVecEnv([lambda: gym.make(env_id)])

# TODO: Define the name of the environment
env_id = 'LunarLander-v2'

Here env_id name is called before it is assigned, and leads to error.
This is what it should have been:
# TODO: Define the name of the environment
env_id = 'LunarLander-v2'

# Create the evaluation env
eval_env = DummyVecEnv([lambda: gym.make(env_id)])

Hey there 👋  thanks for finding this and the update, I'm merging it 🤗.


Add support for Provider

import javax.inject.Provider;
import javax.inject.Singleton;

@Singleton
public class FooProvider implements Provider<Foo> {

  private final SomeDependency bar;

  FooProvider(SomeDependency bar) {
    this.bar = bar;
  }

  @Override
  public Foo get() {
    ...
    return new Foo(...);
  }
}

And then Foo is a bean that can be injected into other beans.

The change for this is in kanuka-generator ... the provider get() method is basically the same as:
import io.kanuka.Bean;
import io.kanuka.Factory;

@Factory
public class FooProvider  {

  private final SomeDependency bar;

  FooProvider(SomeDependency bar) {
    this.bar = bar;
  }

  @Bean
  public Foo get() {
    ...
    return new Foo(...);
  }
}


Hard to find "no predicate match" logs in debug level

Expected behaviour
When mountebank finds no predicate match, the related information such as the incoming request would better be reported at level of warning level so that they can be found easily by setting log level to warning.
Actual behaviour
The logs with "no predicate match" are reported at debug level, together with possibly large amount of logs for matched predicate.
Steps to reproduce
...
Software versions used
OS         : macOS 10.15.16
mountebank : v2.0.0

#### Log contents in mb.log when running mb --loglevel debug

<!--
Please review before pasting to ensure no sensitive data is copied
-->

Log contents here

Good suggestion. I met in the middle and made it an "info" log as a number of use cases depend on that behavior for fallback purposes, but it should still pop out without going to debug logs.


Add Bandersnatch curve

A proposition to add bandersnatch curve (in twisted Edwards form) to gnark. This PR implements Bandersnatch as a separate package from twistededwards mainly because each companion curve is identified by the base curve ID (e.g. BLS12-381 for both Bandersnatch and Jubjub). This has the advantage to keep backward compatibility but duplicates the exact same code. The other option is to create in gnark-crypto an ID for companion curves but gnark users should update their code.

Will leave the duplicated code for this release to avoid API changes, but revisit along side #80 .
Track here: #165.


Test Issue created at Mon, 22 Nov 2021 10:06:30 GMT

Test issue body  Mon, 22 Nov 2021 10:06:30 GMT

Comment on issue at Mon, 22 Nov 2021 10:06:32 GMT


Fix for tests in failures in OLCNE environment

The Jenkins job runs the WKO IT tests in OLCNE remote k8c cluster and there were intermittent failures related to introspector deadline timeout and some changes specific for CRIO runtime. This PR is created to address those issues.
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6227/
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6224/testReport/oracle.weblogic.kubernetes/
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6223/
https://build.weblogick8s.org:8443/job/wko-olcne-test/46/testReport/oracle.weblogic.kubernetes/

could you please add Jenkins results?

Added tests results from cri-o runs and kind runs

Do you have a sequential run test result?

Do you have a sequential run test result?

https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6256/testReport/oracle.weblogic.kubernetes/
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6255/testReport/oracle.weblogic.kubernetes/


Cannot install home-manager on OSX Catalina

Nix can be installed on OSX catalina with this script.
Reproduce with:
$ nix-channel --add https://github.com/rycee/home-manager/archive/master.tar.gz home-manager
$ nix-channel --update
$ nix-shell '<home-manager>' -A install
...
install: creating directory '/nix/store/2lwbpnikvmhyri20wb3h386d3mjcrw5v-home-manager/bin'
'/nix/store/anv3cnwrddqqypxlrngnaqlygb8phsdi-home-manager' -> '/nix/store/2lwbpnikvmhyri20wb3h386d3mjcrw5v-home-manager/bin/home-manager'
building '/nix/store/mz2k6fb1yqpm1hjiywb5wkc3b8896zkv-home-manager-files.drv'...
Error installing file '.cache/.keep' outside $HOME
builder for '/nix/store/mz2k6fb1yqpm1hjiywb5wkc3b8896zkv-home-manager-files.drv' failed with exit code 1
cannot build derivation '/nix/store/64dqib8210r1h1ml80sf59wmmd5arljz-home-manager-generation.drv': 1 dependencies couldn't be built
error: build of '/nix/store/64dqib8210r1h1ml80sf59wmmd5arljz-home-manager-generation.drv' failed
...

I haven't had this problem, but I also manually set XDG cache directory:
https://github.com/rpearce/.config/blob/371f2ac0a19c6f65a00634f6beb7b49149a5c3a2/nix/xdg.nix#L1-L9
and then use it here
https://github.com/rpearce/.config/blob/master/nix/home.nix#L14
Does this help you?

Have the same issue after upgrade to Catalina.
Solution suggested by @rpearce don't help.

It didn't seem to help, here is what I did:

Then I ran this again:
bash-3.2$ nix-shell '<home-manager>' -A install
Restored session: Thu Nov 21 10:04:12 CST 2019

Creating initial Home Manager generation...

these derivations will be built:
  /nix/store/34g7d154yxbdsg2bjk2v81zzf0vcmvw8-source.drv
  /nix/store/ksdwdf1all8xzdwv6m69wq6x4qi6brp6-emacs-27.0.50.drv
  ...
  ...
  ...
/nix/store/64dqib8210r1h1ml80sf59wmmd5arljz-home-manager-generation.drv
building '/nix/store/mz2k6fb1yqpm1hjiywb5wkc3b8896zkv-home-manager-files.drv'...
Error installing file '.cache/.keep' outside $HOME
builder for '/nix/store/mz2k6fb1yqpm1hjiywb5wkc3b8896zkv-home-manager-files.drv' failed w
ith exit code 1
cannot build derivation '/nix/store/64dqib8210r1h1ml80sf59wmmd5arljz-home-manager-generat
ion.drv': 1 dependencies couldn't be built
error: build of '/nix/store/64dqib8210r1h1ml80sf59wmmd5arljz-home-manager-generation.drv'
 failed

There are 73 unread and relevant news items.
Read them by running the command 'home-manager news'.

Uh oh, the installation failed! Please create an issue at

    https://github.com/rycee/home-manager/issues

if the error seems to be the fault of Home Manager.

Maybe this worked for @rpearce because he already had home-manager installed and home-manager switch respects home.nix but when home-manager is installed it doesn't respect home.nix?

Looking at home-manager-install I'm not quite sure why I'm getting the Creating initial home manager generation message when my config exists at the path the script looks for here:
bash-3.2$ ls $HOME/.config/nixpkgs/home.nix
/Users/codygman/.config/nixpkgs/home.nix
bash-3.2$ nix-shell '<home-manager>' -A install

Creating initial Home Manager generation...

Trying to be a bit more specific, this is kind of puzzling:
bash-3.2$ tree /Users/codygman/nixpkgs
/Users/codygman/nixpkgs
├── emacs.nix -> ../../dotfiles/emacs.nix
└── home.nix -> ../../dotfiles/home.nix

0 directories, 2 files
bash-3.2$ XDG_CONFIG_HOME=/Users/codygman nix-shell '<home-manager>' -A install

Creating initial Home Manager configuration...
bash: /Users/codygman/nixpkgs/home.nix: No such file or directory

Creating initial Home Manager generation...

No configuration file found. Please create one at /Users/codygman/nixpkgs/home.nix

Uh oh, the installation failed! Please create an issue at

    https://github.com/rycee/home-manager/issues

if the error seems to be the fault of Home Manager.
bash-3.2$ ls /Users/codygman/nixpkgs/home.nix
/Users/codygman/nixpkgs/home.nix

Because it fails to switch to new generation, the error message cleary said it.
https://github.com/rycee/home-manager/blob/f82246171b253801021c6f98cc50fa461cd972e5/modules/files.nix#L251
Here is a line where the check is fails.

Here is my full config and command:
bash-3.2$ ls /Users/codygman/nixpkgs/
home.nix        xdg.nix
bash-3.2$ cat /Users/codygman/nixpkgs/home.nix
{ config, pkgs, home, ... }:

with import <nixpkgs> {};
with lib;

let
  xdg = import ./xdg.nix;
in
{
  xdg = xdg;
  programs = {
    # Let Home Manager install and manage itself.
    home-manager.enable = true;
    # };
  };
}
bash-3.2$ cat /Users/codygman/nixpkgs/xdg.nix

let
  home_dir = builtins.getEnv "HOME";

in {
  enable = true;
  configHome = "${home_dir}/.config";
  dataHome = "${home_dir}/.data";
  cacheHome = "${home_dir}/.cache";
}
bash-3.2$ XDG_CONFIG_HOME=/Users/codygman nix-shell '<home-manager>' -A install

Creating initial Home Manager generation...

these derivations will be built:
  /nix/store/18xaxk5ayahdznmwsbkymq5gfj54lyvd-hm-session-vars.sh.drv
  /nix/store/fgzq9zx9f439z3ajw7v0my7yl0v77cf4-nmd-options.xml.drv
  /nix/store/yfy207v1vx73bmygah9hcyxvckrdsbd6-options-db.xml.drv
  /nix/store/q6azc0l1ss5rm38f179xvri3djz33yzd-nmd-documents.drv
  /nix/store/7jwkkbl683gyi4vim7f9q98774z8zpy1-manual-combined.drv
  /nix/store/gf676ar5xpazaimm30w9rd88iq9cdxr6-home-manager-files.drv
  /nix/store/salnr7lfwn8jqrmgnbxz4qh09brmmnkc-manual-olinkdb.drv
  /nix/store/n5dnc6iqbgnfb0vpyaac9rklbzcwx508-man-pages.drv
  /nix/store/hajcs6ilgd7kvfp6sf3s783dp53zgwam-home-manager-path.drv
  /nix/store/mqakbvqzmjjqgrr5gyc5nyn7c4avzsq7-link.drv
  /nix/store/zbng6sk3jjkg588mrp750zbisl52cmgv-activation-script.drv
  /nix/store/zkkabx5h5r1cirvy51yavljw12z6vs3s-home-manager-generation.drv
building '/nix/store/gf676ar5xpazaimm30w9rd88iq9cdxr6-home-manager-files.drv'...
Error installing file '.cache/.keep' outside $HOME
builder for '/nix/store/gf676ar5xpazaimm30w9rd88iq9cdxr6-home-manager-files.drv' failed
with exit code 1
cannot build derivation '/nix/store/zkkabx5h5r1cirvy51yavljw12z6vs3s-home-manager-gener
tion.drv': 1 dependencies couldn't be built
error: build of '/nix/store/zkkabx5h5r1cirvy51yavljw12z6vs3s-home-manager-generation.dr
' failed

There are 72 unread and relevant news items.
Read them by running the command 'home-manager news'.

Uh oh, the installation failed! Please create an issue at

    https://github.com/rycee/home-manager/issues

if the error seems to be the fault of Home Manager.

Because it fails to switch to new generation, the error message cleary said it.
https://github.com/rycee/home-manager/blob/f82246171b253801021c6f98cc50fa461cd972e5/modules/files.nix#L251
Here is a line where the check is fails.

Interesting, I'm still confused as to why $HOME wouldn't be ~ (or /Users/codygman) for me. When I run echo $HOME in that same terminal I get:
bash-3.2$ echo $HOME
/Users/codygman

I'm add debug output and get
Error installing file '.Xresources' outside $HOME out=/nix/store/8rl6hv71xdjad3bnc46djz980ayh01v5-home-manager-files target=/usr/local/nix/store/8rl6hv71xdjad3bnc46djz980ayh01v5-home-manager-files/.Xresources

In catalina instalation /nix is actually a symlink to /usr/local/nix, so we need just to unwrap link in installation script. I'll try to make PR for this.
lrwxr-xr-x  1 root  wheel  14 Nov 19 11:44 /nix -> /usr/local/nix

That makes sense --- I'm on Catalina but my /nix is
drwxrwxr-x    8 user  256 Nov 13 09:17 nix

so we're working from different places.

How do you install nix itself? I use hack from https://github.com/NixOS/nix/issues/2925#issuecomment-552244858

How do you install nix itself? I use hack from NixOS/nix#2925 (comment)

I've been following that thread since it was created! This was what I did after I upgraded to Catalina & could not use /nix/:
https://github.com/NixOS/nix/issues/2925#issuecomment-539570232

@codygman I guess we can close that issue, due to merged pullrequest. Can you confirm that issue is resolved?

Sure,  I can check in the next hour or so.
On Fri, Nov 22, 2019, 15:55 Anton<EMAIL_ADDRESS>wrote:

@codygman https://github.com/codygman I guess we can close that issue,
due to merged pullrequest. Can you confirm that issue is resolved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rycee/home-manager/issues/919?email_source=notifications&email_token=AABXEN7LL2BJS3OQ23L5V4LQVBIM3A5CNFSM4JQEJDZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE67OWQ#issuecomment-557709146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABXEN6GW47S7RCZ773WVS3QVBIM3ANCNFSM4JQEJDZQ
.

@pltanton It worked after I updated the channel to get the newest home-manager!
bash-3.2$ nix-channel --update
these derivations will be built:
  /nix/store/996ix8abya66kl5smndj1yscd5ajkflj-home-manager.drv
building '/nix/store/996ix8abya66kl5smndj1yscd5ajkflj-home-manager.drv'...
unpacking channels...
created 2 symlinks in user environment
bash-3.2$ nix-shell '<home-manager>' -A install
these derivations will be built:
  /nix/store/ycs2kihvgs1lr0rv09jgclmbg67mz6yq-home-manager.drv
building '/nix/store/ycs2kihvgs1lr0rv09jgclmbg67mz6yq-home-manager.drv'...
install: creating directory '/nix/store/83arygvpqk53vpwx8pdhy20j3s8s2qfj-home-manager'
...
Creating initial Home Manager generation...

these derivations will be built:
...
...
...
All done! The home-manager tool should now be installed and you
can edit

    /Users/codygman/.config/nixpkgs/home.nix

to configure Home Manager. Run 'man home-configuration.nix' to
see all available options.


Consider adding a --show-status flag to display HTTP status codes for discovered endpoints when using the URL option

Suggestion:
When using the URL option, introduce a --show-status flag that outputs the HTTP status codes of the discovered endpoints. This enhancement will help users quickly identify the status of endpoints and make decisions based on the response codes.
Detailed Explanation:

Current Behavior:

When the URL option is used, the tool finds and lists endpoints, but does not display their HTTP status codes.

Proposed Enhancement:

Introduce a new flag --show-status that, when enabled, will display the HTTP status code for each discovered endpoint.
This will help users quickly see which endpoints are returning errors (e.g., 404, 500) or are functioning correctly (e.g., 200).

Future Extension:

In future iterations, consider adding options like --exclude-status to exclude endpoints with specific status codes when delivering results.
This would provide more flexibility and improve the efficiency of the deliver functionality by filtering out unnecessary endpoints.

Benefits:

Saves time by directly displaying the status of endpoints.
Helps users focus on valid and functional endpoints.
Provides a foundation for future enhancements, such as filtering by specific status codes.

@ksg97031
Great idea! It's not a difficult task, so let's get started quickly.


Adding securityContext

This PR is adding securityContext to make the Jobs created by this controller more secure. The default securityContext is set to comply with the Restricted Pod Security Standard profile but it can be further tweaked via the podSecurityContext and the securityContext  fields of the HelmChart Custom Resource.

Looks like one of the tests is failing:
  [FAILED] Expected
      <v1.PodSecurityContext>: {
          SELinuxOptions: nil,
          WindowsOptions: nil,
          RunAsUser: nil,
          RunAsGroup: nil,
          RunAsNonRoot: false,
          SupplementalGroups: nil,
          FSGroup: nil,
          Sysctls: nil,
          FSGroupChangePolicy: nil,
          SeccompProfile: nil,
      }
  to equal
      <v1.PodSecurityContext>: {
          SELinuxOptions: nil,
          WindowsOptions: nil,
          RunAsUser: nil,
          RunAsGroup: nil,
          RunAsNonRoot: false,
          SupplementalGroups: nil,
          FSGroup: nil,
          Sysctls: nil,
          FSGroupChangePolicy: nil,
          SeccompProfile: {
              Type: "RuntimeDefault",
              LocalhostProfile: nil,
          },
      }


Add support for OFED 4.9-<IP_ADDRESS>

Not really much of a contribution since I haven't made any modifications to the patches themselves, but it's handy that it automatically detects the last LTS version.
One thing I did notice: when installing from a local yum repo instead of the script (as a workaround suggested to me here when I was having problems with a recent kernel) I didn't see any missing requirements with dnf check all but I did see conflicts when trying to upgrade OpenMPI:
# dnf install openmpi4-gnu9-ohpc
Last metadata expiration check: 3:17:42 ago on Wed 26 Oct 2022 01:00:21 PM -03.
Package openmpi4-gnu9-ohpc-4.0.5-4.1.ohpc.2.1.x86_64 is already installed.
Error:
 Problem: problem with installed package mlnx-ofed-all-user-only-4.9-<IP_ADDRESS>.rhel8.6.noarch
  - package mlnx-ofed-all-user-only-4.9-<IP_ADDRESS>.rhel8.6.noarch requires libibverbs >= 50mlnx1-1.49510, but none of the providers can be installed
  - cannot install both libibverbs-37.2-1.el8.x86_64 and libibverbs-50mlnx1-1.49510.x86_64
  - cannot install both libibverbs-50mlnx1-1.49510.x86_64 and libibverbs-37.2-1.el8.x86_64
  - package openmpi4-gnu9-ohpc-4.1.1-10.1.ohpc.2.4.x86_64 requires libefa.so.1()(64bit), but none of the providers can be installed
  - cannot install the best candidate for the job

Obviously this was solved when I applied the patch, but I wonder if it was me making a mistake when I initially installed the components or if it's something with the yum local repo install.

@viniciusferrao Noted! I forgot to sign off and inadvertently used my config for Gitlab. I'm making a new PR amending the last commit with a sign-off and the correct email (I made the changes locally and merged my origin branch). I guess this is enough for showing up as a contributor but arguably not very elegant/pretty. If you would prefer another solution let me know and I'll try to make the proper changes.


add custom_token support

#191
#189
this PR adds a first implementation of custom token support feature to log in using a custom token.
Currently a custom token needs to be generated outside of our  addon.
added:
Firebase.Auth.login_with_custom_token(token : String)
If the request is successful, the login_succeeded(auth : Dictionary)  signal will be emitted in the same way as all the other signals, and the client will be automatically authenticated.
This feature needs to be tested

Sorry, for the long delay. I just tested it successful.
I created a Firebase Function, which generates a custom token for my username and I just dropped the received token into the new function login_with_custom_token. It worked, in Firebase I can see the new auth entry with my user-uid I used to create the custom token.
Thanks for the really fast implementation on your side. Now I'm able to create username/password logins instead of email/password logins.

@mars3142 that's awesome, and thank you very much for sharing your approach. It's really interesting and honestly never thought of that personally. :)
We have a wiki here, if you want feel free to share with as your method, even without thecnical details, since it seems to be a very suitable implementation for the function we implemented.
I don't think you need to be directly added to the repo to do so, since you can pull the wiki as any other git repository. You should appear automatically as a Contributor for that.


I can create two datasets based on the same table when it should be banned

Hello,
when a user tries to create a dataset based on a table already in use, the following alert is displayed: "An error occurred while creating datasets: (table_name) Dataset tests already exists"

This is normal to avoid creating duplicates... but I manage to create duplicate datasets using the import feature.
The order of followings operations is important :

Import a CSV without specify schema

The dataset is created

Create manually a dataset on the same table

The dataset is created again

In the case of a Postgres database, the default schema used is "public" if it is not specified.
At the first step, the dataset created does not specify this "public" schema,
which makes it possible to manually create a dataset on this same table of the public schema
Best regards

Have you checked the creating the dataset actually created a table of the same name in the same underlying Postgres database?
You are sure is it is not virtual dataset or one of the types internal to Superset?
If the table was created in the underlying database then you are using a ROLE with table creation rights query the database which you shouldn't.
You are supposed to create a read only ROLE in the underlying database and use that in Superset, not a role with table and/or database creation rights. Perish the thought.

2 datasets (not virtual) are created :

one by data import
one by manual creation

Physically, in the base I have one table (created during the import)

Manual creation should not be allowed because a dataset already exists.
Regards

@betodealmeida @eschutho do you see any concern here?
Also, @xavier-GitHub76 are you able to confirm that this is the case in Superset 3.x?

Hello,
it's OK with version 3.0.0 👍

I close this issue.
Best regards

https://github.com/apache/superset/assets/82046143/7113ba34-dac3-4167-b735-2856acdc6412

CC @yousoph @sadpandajoe just to make sure this is on their radar in case of any concerns.

Doesn't seem like a critical issue to me. In the future we could require a schema on import/export.


Cross-compile on windows

Add windows to the list of cross compilation OS.

Ok, that's enough for this PR. No we're cross-compiling for Windows on Travis and we're running the integration tests on Windows with Appveyor.

I think this PR is a great idea, but conceptually I think you are tied too much to the idea of a CI environment. imho there should be no mention of travis or Appveyor anywhere in the codebase (other than in the yml files that configure those environments).
Also I think it would be great if the conventional way to run all of the restic tests locally would use the exact same code as CI uses (so the runner code itself should work locally just as well as it does on the CI server).
Might even add "go run run_integration_tests.go" to the Makefile so that "make test" does the same as CI.

Good idea in general, but let's tackle that in a second PR and merge this for now.


Implement zap-like functionality in chef core resources and LWRPs

Ref: https://github.com/nvwls/zap
I assume there's been some discussion about it somewhere, since the concept seemed well-presented at ChefConf, but didn't see an issue for it :)
Anyone have any thoughts or things to share on the general premise?
cc: @nvwls @svanharmelen @helgi @damm
cc: @ranjib (curious about your internal library: https://github.com/chef/chef/issues/3616#issuecomment-116914334)

I don't quite like the implementation of zap since it has issues with resources in sub-resource collections inside of resources and providers.   It probably needs to hook the event system to watch for resources running, and then collect a list of the ones that ran, then register an event_handler to do the cleanup at the very end of the run.  It might actually be cleaner to do it in core chef, but I'd like to see an implementation in a cookbook that tried to get it more correct first.

Zap's issues:

use_inline_resource resources inside of providers are missed (PR #1415 attempted to address this)
partial runs (override run_lists) can wind up zapping files that are referenced in recipes not running (i.e. zap should not zap files with override run lists)
aborted runs can wind up with the same problem as files which were not yet managed at the time chef aborts will not be seen on the resource collection, but the delayed notification to the zap cleanup resource will fire and will clean resources it should not (i.e. zap should not zap files if chef client aborts)

In core chef we should also consider a way of incorporating this into existing resources.  For example, the directory resource could take a 'zap true' property instead of having a new zap resource.  Or at any rate the shape of the API should be considered.

I suspect handling case 2 and 3 would be difficult without storing all the resources somewhere (node seems overloaded; this would hyperoverload it)

Well 2 is pretty easy -- when the run_list is overridden just never zap -- similar to node.save being a no-op when that happens.
3 would also be fairly easy if zap-cleanup was implemented as a custom handler rather than a delayed notification (since we're talking about incorporating into core chef, it could look like the reboot handler).
1 is the hard problem that requires tracking all the resources in the run completely.  One way to solve this would be to add pointers to the sub-resource collection hanging off of parent resource collections or hanging off of the run_context in some way so that they wouldn't get garbage collected and could be iterated at the end.  Another possibility is hooking the events system when resources fire and building a parallel container with all the resources that have been evaluated in converge mode.

#8063 exposes the Chef::ActionCollection which is the thing which can be used to address nvwls/zap#35 sub-resource collection concerns.  Not only that but it also captures e.g. manually created file resources from someone just going to town with Chef::Resource::File.new like its still Chef 0.10.8...


Support to DNS, IP and Email SAN fields

This PR depends on #3 but the commit Support to DNS, IP and Email SAN fields can be reviewed.

lgtm

I believe you should omit all those become: yes in tests, I don't think we use them elsewhere. In general, our roles do not make much sense to execute as other user than root or without become.

I believe you should omit all those become: yes in tests, I don't think we use them elsewhere. In general, our roles do not make much sense to execute as other user than root or without become.
IMO we can keep become: yes as it is as these tests will be running in downstream IDM-CI also.


Saving and restoring prototype seems to only save one dimension, and then causes an error placing new tokens

Foundry: v10.286
DnD5e: v2.0.3
Steps to Reproduce:

Drop a token
Scale it with quick-scale
Save the prototype with quick-scale (default `SHIFT-')
Revert to prototype with quick-scale (default \)

Expected Result: The scale is restored
Actual Result: See screenshot; scale is restored in one dimension only.

After the error occurs (and my reproduction steps don't seem to get it 100% of the time :/), attempting to drop any other token on the scene results in this error, until Foundry is refreshed.
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'clear')
[No packages detected]
    at Token5e._refreshTarget (foundry.js:45708:17)
    at Token5e._refresh (foundry.js:45601:10)
    at Token5e.refresh (foundry.js:25015:10)
    at Canvas.highlightObjects (foundry.js:23931:11)
    at DrawingsLayer.deactivate (foundry.js:30215:12)
    at TokenLayer.activate (foundry.js:30184:76)
    at TokenLayer._onDropActorData (foundry.js:36910:10)

After the refresh the token is still squashed, and further copies of the actor dropped on the scene are also squashed. Manually updating the token (or prototype token's) scale by dragging the bar in the settings window seems to resolve the issue, until it is triggered with quick-scale again.

Hmm! Weird. Will take a look tonight, thanks for the ticket.

Fixed in 1.5.3


Fails to compile for Python 3.7 on Mac

I had to add
pyyaml=4.2b4

to requirements.txt in order to compile successfully with Python 3.7 (the version bundled with recent homebrew formula)
See:
https://github.com/yaml/pyyaml/issues/126

Is this still an issue?

Hi @vaibhavsagar .
I have just pulled changes from master branch and recompiled. It worked OK.
Closing issue.
Thanks!


Add migration guide for Python bindings from libolm.

I think that I've managed to catch all the differences and unsupported features

I messaged #e2e:matrix.org about this too: I'm definitely curious to find out exactly how much outdated https://pypi.org/project/vodozemac-python/ is, and what I can do to help get this project updated.
This PR is a huge help already to that end

If you'd like to include this, please open a pull request in the new repo: https://github.com/matrix-nio/vodozemac-python.


ctrl-c odo dev reported as an error in telemetry

/kind bug
When user ctrl-c odo dev it is reported as an error in the telemetry data
this is send to the telemetry
error: Dev mode interrupted by user
error-type: *errors.errorString

user interrupting odo dev is expected behavior and should not be reported as an error

Grooming (2023-06-01)

Interrupting the process should return 0 as exit code (separate issue)

For odo dev:

If an error occurs in cleanup, exit code should not be 0. If no error, exit code should be 0

Do not explicitly exit in odo context. Leverage the cancelable context. Returning an error should propagate as an exit code.


{Network} az network vpn-connection list-connection: the command should be unregistered

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network


Reduce semantic dependencies in contextRequiresStrictConcurrencyChecking

We don't need fully-checked isolation as computed from attributes to
determine whether we're in a concurrency context. Use a cheaper predicate,
which can also avoid spurious cycles.
Fixes rdar://99013488.

@swift-ci please test


CLI: completes command-line analysis of files

dicogis-cli list inventory --language fr --verbose --input-folder tests/

[!WARNING]
Not all formats are working right now. It's not blocking and will be fixed in nearly future PRs.

@sylvainbeo can I merge it?