Unable to create config

🐛 Summary
Getting the following error when trying to run python3 scripts/generate_conf.py
Traceback (most recent call last):
File "C:\Users\username\untitledgoosetool\scripts\generate_conf.py", line 8, in
from goosey.azure_ad_datadumper import AzureAdDataDumper
ModuleNotFoundError: No module named 'goosey'
To reproduce
Steps to reproduce the behavior:
Following the instructions from github, using windows 11

python -m venv .venv
.venv\Scripts\activate

2. ```
git clone https://github.com/cisagov/untitledgoosetool.git
cd untitledgoosetool
python -m pip install .

python scripts/generate_conf.py

Expected behavior
create the config file needed for the tool.
Any helpful log output or screenshots
Paste the results here:
Traceback (most recent call last):
  File "C:\Users\username\untitledgoosetool\scripts\generate_conf.py", line 8, in <module>
    from goosey.azure_ad_datadumper import AzureAdDataDumper
ModuleNotFoundError: No module named 'goosey'

Running Python 3.11.2 on windows 11
Add any screenshots of the problem here.

You have to use python 3.7,8,9 but anyways im getting the same error xD

Try this:
Ensure that pip is running from your python3.9 version rather than python3.10
You will need to manually download the ubuntu wheel for wxPython
wget https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04/wxPython-4.2.0-cp39-cp39-linux_x86_64.whl
Install the wheel
pip install wxPython-4.2.0-cp39-cp39-linux_x86_64.whl
Install tkinter
sudo apt install python3.9-tk
Install goose
python -m pip install .

Try this: Ensure that pip is running from your python3.9 version rather than python3.10 You will need to manually download the ubuntu wheel for wxPython wget https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04/wxPython-4.2.0-cp39-cp39-linux_x86_64.whl Install the wheel pip install wxPython-4.2.0-cp39-cp39-linux_x86_64.whl Install tkinter sudo apt install python3.9-tk Install goose python -m pip install .

Hello, this solution is only for Ubuntu issues.

Running Python 3.11.2 on windows 11
Add any screenshots of the problem here.

Can you make sure to downgrade your Python to one of the supported versions of Python: 3.7, 3.8, 3.9?
Afterwards, please try to do a pip install and let us know if it solves the issue.

Running Python 3.11.2 on windows 11
Add any screenshots of the problem here.

Can you make sure to downgrade your Python to one of the supported versions of Python: 3.7, 3.8, 3.9?
Afterwards, please try to do a pip install and let us know if it solves the issue.

Can you check my issue? i have one similar, i tried with python 3.8 and 3.9 https://github.com/cisagov/untitledgoosetool/issues/16 Thank you!

Do you know if you are running into an error when you run python -m pip install . ? If you don't mind, can you share the output?

Sorry, I meant the output of your python -m pip install .

Sorry there is some errors, see below
(.venv) PS C:\Users\user\untitledgoosetool> python -m pip install . Processing c:\users\user\untitledgoosetool Collecting cryptography<39,>=36.0.1 (from goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/e3/3f/41186b1f2fd86a542d399175f6b8e43f82cd4dfa51235a0b030a042b811a/cryptography-38.0.4.tar.gz (599kB)      |████████████████████████████████| 604kB 2.2MB/s   Installing build dependencies ... done   Getting requirements to build wheel ... done     Preparing wheel metadata ... done Collecting requests (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/d2/f4/274d1dbe96b41cf4e0efb70cbced278ffd61b5c7bb70338b62af94ccb25b/requests-2.28.2-py3-none-any.whl Collecting webdrivermanager (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/3c/75/81b306150423486803c6fd8a28d83fc91b992a089c7059e63c231cdefef1/webdrivermanager-0.10.0.tar.gz   Installing build dependencies ... done   Getting requirements to build wheel ... done     Preparing wheel metadata ... done Collecting aiohttp==3.8.1 (from goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/e4/eb/2e5c66f6ab8bf1fa9743552ec49bd8deb9a8ad385545bbd60c8f50529e21/aiohttp-3.8.1-cp38-cp38-win_amd64.whl (555kB)      |████████████████████████████████| 563kB 6.4MB/s Collecting async-timeout==4.0.2 (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/d6/c1/8991e7c5385b897b8c020cdaad718c5b087a6626d1d11a23e1ea87e325a7/async_timeout-4.0.2-py3-none-any.whl Collecting openpyxl (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/6a/94/a59521de836ef0da54aaf50da6c4da8fb4072fb3053fa71f052fd9399e7a/openpyxl-3.1.2-py2.py3-none-any.whl Collecting azure-mgmt-web (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/be/59/a7fb82c976cd37d3978a224955a9380cc753d3f4330aa5f4183dba21393d/azure_mgmt_web-7.0.0-py3-none-any.whl Collecting azure-mgmt-storage (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/6a/53/dd7f37c78faf77f15ec0acfea3094b317e7183014414ffe737c2e32e6fa7/azure_mgmt_storage-21.0.0-py3-none-any.whl Collecting darkdetect (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/f2/f2/728f041460f1b9739b85ee23b45fa5a505962ea11fd85bdbe2a02b021373/darkdetect-0.8.0-py3-none-any.whl Collecting azure-mgmt-network (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/c8/a3/c84b92413bb6740649e695c5b05ca9e98469f55990f5032b69ee32695dd5/azure_mgmt_network-23.0.0-py3-none-any.whl Collecting colored (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/f3/d6/00203998f27ab30b2417998006ad0608f236740bb129494dd7c5621861e1/colored-1.4.4.tar.gz Collecting azure-mgmt-resource (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/c6/53/6a8118e1063d2b60ea33e8dd16ea2dafd1e89c91ee83a6581f108fdea940/azure_mgmt_resource-23.0.0-py3-none-any.whl Collecting azure-mgmt-monitor (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/88/f9/3c3789b9df4d3563d58b83ff65f1b287731b0db28586e6769999dfc62710/azure_mgmt_monitor-6.0.0-py3-none-any.whl Collecting azure-identity (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/ce/96/942f03d8a80e30e2289496c10d99e3a8b71f10c0b70b5337fd8ec2ae85e5/azure_identity-1.12.0-py3-none-any.whl Collecting azure-mgmt-compute (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/9d/2f/5e773479297c685f1c323120502741e5ffbc7a65ac2379e9541376660729/azure_mgmt_compute-29.1.0-py3-none-any.whl Collecting azure-storage-blob (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/46/cf/ef1daa7b7df2b2d72db82fa2a777bf50133f4797b4bdfa6b3bbea09660fe/azure_storage_blob-12.15.0-py3-none-any.whl Collecting azure-mgmt-security (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/89/a2/14d717fb8e399712c74d35581b1b23f17807c65035985e2beb1c71124cda/azure_mgmt_security-4.0.0-py3-none-any.whl Collecting selenium (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/d9/4b/e964eaca99d249eb3109ac75af551601923ba727c915db43c82311a0b16a/selenium-4.8.3-py3-none-any.whl Collecting selenium-wire (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/eb/7e/9548b365eab16730b6a8da25c6e1f83f3b84fb6092ecd2d4d69933d08a45/selenium_wire-5.1.0-py3-none-any.whl Collecting adal>=1.2.7 (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/49/8d/58008a9a86075827f99aa8bb75d8db515bb9c34654f95e647cda31987db7/adal-1.2.7-py2.py3-none-any.whl Collecting msrestazure (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/5e/3a/7adb08fd2f0ee6fdfd03685fac38477b64f184943dcf6ea0cbffb205f22d/msrestazure-0.6.4-py2.py3-none-any.whl Collecting Gooey==<IP_ADDRESS> (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/21/03/2d0fc5f982f085ab72c56caa27238339a28419c0da716add1c5e1cf2fa99/Gooey-<IP_ADDRESS>-py2.py3-none-any.whl Collecting typing-extensions>=4.1.1 (from goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/31/25/5abcd82372d3d4a3932e1fa8c3dbf9efac10cc7c0d16e78467460571b404/typing_extensions-4.5.0-py3-none-any.whl Collecting cffi>=1.12 (from cryptography<39,>=36.0.1->goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/c9/e3/0a52838832408cfbbf3a59cb19bcd17e64eb33795c9710ca7d29ae10b5b7/cffi-1.15.1-cp38-cp38-win_amd64.whl Collecting idna<4,>=2.5 (from requests->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/fc/34/3030de6f1370931b9dbb4dad48f6ab1015ab1d32447850b9fc94e60097be/idna-3.4-py3-none-any.whl (61kB)      |████████████████████████████████| 71kB ... Collecting certifi>=2017.4.17 (from requests->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl (155kB)      |████████████████████████████████| 163kB 6.4MB/s Collecting urllib3<1.27,>=1.21.1 (from requests->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/7b/f5/890a0baca17a61c1f92f72b81d3c31523c99bec609e60c292ea55b387ae8/urllib3-1.26.15-py2.py3-none-any.whl (140kB)      |████████████████████████████████| 143kB ... Collecting charset-normalizer<4,>=2 (from requests->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/26/20/83e1804a62b25891c4e770c94d9fd80233bbb3f2a51c4fadee7a196e5a5b/charset_normalizer-3.1.0-cp38-cp38-win_amd64.whl (96kB)      |████████████████████████████████| 102kB 6.4MB/s Collecting appdirs (from webdrivermanager->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/3b/00/2344469e2084fb287c2e0b57b72910309874c3245463acd6cf5e3db69324/appdirs-1.4.4-py2.py3-none-any.whl Collecting lxml (from webdrivermanager->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/95/2c/b6326b95954fcd2d1133ff60e7c10af8d7dd17b52d09eaa6db828fd13afb/lxml-4.9.2-cp38-cp38-win_amd64.whl (3.9MB)      |████████████████████████████████| 3.9MB 6.4MB/s Collecting BeautifulSoup4 (from webdrivermanager->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/29/15/236481b1310857378b0d7d00e1a56018fb88e6cab18cc8076d858cdc565b/beautifulsoup4-4.12.1-py3-none-any.whl (142kB)      |████████████████████████████████| 143kB ... Collecting tqdm (from webdrivermanager->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/e6/02/a2cff6306177ae6bc73bc0665065de51dfb3b9db7373e122e2735faf0d97/tqdm-4.65.0-py3-none-any.whl (77kB)      |████████████████████████████████| 81kB ... Collecting aiosignal>=1.1.2 (from aiohttp==3.8.1->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/76/ac/a7305707cb852b7e16ff80eaf5692309bde30e2b1100a1fcacdc8f731d97/aiosignal-1.3.1-py3-none-any.whl Collecting multidict<7.0,>=4.5 (from aiohttp==3.8.1->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/d2/cf/d00992d281fb953a01685d9b2e68f66901c7dee7bcb75dad1a5ef9a879d3/multidict-6.0.4-cp38-cp38-win_amd64.whl Collecting yarl<2.0,>=1.0 (from aiohttp==3.8.1->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/f9/fa/9c746d29462714663d04cf9e34cc44a86efa17705a811c77556643b80f1b/yarl-1.8.2-cp38-cp38-win_amd64.whl (56kB)      |████████████████████████████████| 61kB ... Collecting attrs>=17.3.0 (from aiohttp==3.8.1->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/fb/6e/6f83bf616d2becdf333a1640f1d463fef3150e2e926b7010cb0f81c95e88/attrs-22.2.0-py3-none-any.whl (60kB)      |████████████████████████████████| 61kB ... Collecting frozenlist>=1.1.1 (from aiohttp==3.8.1->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/03/00/febbfd2ec244a0f91707bd879afe6aa278e337dc41cd9d0d25260e6da38e/frozenlist-1.3.3-cp38-cp38-win_amd64.whl Collecting et-xmlfile (from openpyxl->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/96/c2/3dd434b0108730014f1b96fd286040dc3bcb70066346f7e01ec2ac95865f/et_xmlfile-1.1.0-py3-none-any.whl Collecting azure-mgmt-core<2.0.0,>=1.3.1 (from azure-mgmt-web->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/29/99/d06021eb45ff660cd4cf1bf16a60645a8256672edf46ff1976a709a50918/azure_mgmt_core-1.3.2-py3-none-any.whl Collecting msrest>=0.6.21 (from azure-mgmt-web->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/15/cf/f2966a2638144491f8696c27320d5219f48a072715075d168b31d3237720/msrest-0.7.1-py3-none-any.whl (85kB)      |████████████████████████████████| 92kB 5.8MB/s Collecting azure-common~=1.1 (from azure-mgmt-web->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/62/55/7f118b9c1b23ec15ca05d15a578d8207aa1706bc6f7c87218efffbbf875d/azure_common-1.1.28-py2.py3-none-any.whl Collecting isodate<1.0.0,>=0.6.1 (from azure-mgmt-network->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/b6/85/7882d311924cbcfc70b1890780763e36ff0b140c7e51c110fc59a532f087/isodate-0.6.1-py2.py3-none-any.whl (41kB)      |████████████████████████████████| 51kB ... Collecting msal<2.0.0,>=1.12.0 (from azure-identity->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/cc/86/9900755d4be6e36b48603f9056ffca341d42139297df6f7e143fa96e6ed7/msal-1.21.0-py2.py3-none-any.whl (89kB)      |████████████████████████████████| 92kB 5.8MB/s Collecting six>=1.12.0 (from azure-identity->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/d9/5a/e7c31adbe875f2abbb91bd84cf2dc52d792b5a01506781dbcf25c91daf11/six-1.16.0-py2.py3-none-any.whl Collecting msal-extensions<2.0.0,>=0.3.0 (from azure-identity->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/52/34/a8995d6f0fa626ff6b28dbd9c90f6c2a46bd484bc7ab343d078b0c6ff1a7/msal_extensions-1.0.0-py2.py3-none-any.whl Collecting azure-core<2.0.0,>=1.11.0 (from azure-identity->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/73/c6/d938eab39385703d28555872df60b77e11779229ffb611118ac1c8725ca5/azure_core-1.26.3-py3-none-any.whl (174kB)      |████████████████████████████████| 184kB ... Collecting trio-websocket~=0.9 (from selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/ea/20/fbfa99f222b0aa298d4de6c20a65acf0ed18cab9a4392cea3f34c936a41a/trio_websocket-0.10.2-py3-none-any.whl Collecting trio~=0.17 (from selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/f1/ed/3623a910f9bb7a31b067d6baef476ed6e294e92a245f94ab992988e4a666/trio-0.22.0-py3-none-any.whl (384kB)      |████████████████████████████████| 389kB ... Collecting pysocks>=1.7.1 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/8d/59/b4572118e098ac8e46e399a1dd0f2d85403ce8bbaad9ec79373ed6badaf9/PySocks-1.7.1-py3-none-any.whl Collecting blinker>=1.4 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/17/50/cd9207254dd9ab92d300717721600e367d99b0fcb83b6338af8dc34a8fa1/blinker-1.6-py3-none-any.whl Collecting h2>=4.0; python_version >= "3.6.0" (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/2a/e5/db6d438da759efbb488c4f3fbdab7764492ff3c3f953132efa6b9f0e9e53/h2-4.1.0-py3-none-any.whl (57kB)      |████████████████████████████████| 61kB 4.1MB/s Collecting pydivert>=2.0.3; sys_platform == "win32" (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/ca/8f/86d7931c62013a5a7ebf4e1642a87d4a6050c0f570e714f61b0df1984c62/pydivert-2.1.0-py2.py3-none-any.whl (104kB)      |████████████████████████████████| 112kB ... Collecting pyasn1>=0.3.1 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/62/1e/a94a8d635fa3ce4cfc7f506003548d0a2447ae76fd5ca53932970fe3053f/pyasn1-0.4.8-py2.py3-none-any.whl (77kB)      |████████████████████████████████| 81kB ... Collecting zstandard>=0.14.1 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/9b/c9/082410f4feabd60475817dc3d0ecf99d63af598a1a17e8f2850d56ef9cff/zstandard-0.20.0-cp38-cp38-win_amd64.whl (644kB)      |████████████████████████████████| 645kB ... Collecting pyparsing>=2.4.2 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/6c/10/a7d0fa5baea8fe7b50f448ab742f26f52b80bfca85ac2be9d35cdd9a3246/pyparsing-3.0.9-py3-none-any.whl (98kB)      |████████████████████████████████| 102kB 6.8MB/s Collecting wsproto>=0.14 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/78/58/e860788190eba3bcce367f74d29c4675466ce8dddfba85f7827588416f01/wsproto-1.2.0-py3-none-any.whl Collecting hyperframe>=6.0; python_version >= "3.6.0" (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/d7/de/85a784bcc4a3779d1753a7ec2dee5de90e18c7bcf402e71b51fcf150b129/hyperframe-6.0.1-py3-none-any.whl Collecting brotli>=1.0.9 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/63/29/1b104b5915e61d9f7443889657d93937b7e0b33b331609b82693547934a0/Brotli-1.0.9-cp38-cp38-win_amd64.whl (365kB)      |████████████████████████████████| 368kB ... Collecting pyOpenSSL>=22.0.0 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/b7/6d/d7377332703ffd8821878794aca4fb54637da654bf3e467ffb32109c2147/pyOpenSSL-23.1.1-py3-none-any.whl (57kB)      |████████████████████████████████| 61kB 3.8MB/s Collecting kaitaistruct>=0.7 (from selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/4e/bf/88ad23efc08708bda9a2647169828e3553bb2093a473801db61f75356395/kaitaistruct-0.10-py2.py3-none-any.whl Collecting python-dateutil<3,>=2.1.0 (from adal>=1.2.7->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/36/7a/87837f39d0296e723bb9b62bbb257d0355c7f6128853c78955f57342a56d/python_dateutil-2.8.2-py2.py3-none-any.whl (247kB)      |████████████████████████████████| 256kB ... Collecting PyJWT<3,>=1.0.0 (from adal>=1.2.7->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/40/46/505f0dd53c14096f01922bf93a7abb4e40e29a06f858abbaa791e6954324/PyJWT-2.6.0-py3-none-any.whl Collecting psutil>=5.4.2 (from Gooey==<IP_ADDRESS>->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/3d/7d/d05864a69e452f003c0d77e728e155a89a2a26b09e64860ddd70ad64fb26/psutil-5.9.4.tar.gz (485kB)      |████████████████████████████████| 491kB ...   Installing build dependencies ... done   Getting requirements to build wheel ... done     Preparing wheel metadata ... done Collecting pygtrie>=2.3.3 (from Gooey==<IP_ADDRESS>->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/ec/cd/bd196b2cf014afb1009de8b0f05ecd54011d881944e62763f3c1b1e8ef37/pygtrie-2.5.0-py3-none-any.whl Collecting wxpython>=4.1.0 (from Gooey==<IP_ADDRESS>->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/10/1c/26ed299dbd8f81b46a76945a93223259194732796fb4979af7bd85cb7eb6/wxPython-4.2.0-cp38-cp38-win_amd64.whl (18.0MB)      |████████████████████████████████| 18.0MB 2.2MB/s Collecting Pillow>=4.3.0 (from Gooey==<IP_ADDRESS>->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/c3/ba/c4c2a1411561cd9725979115e7450f1367b44997ae1ff29e5845bce92d52/Pillow-9.5.0-cp38-cp38-win_amd64.whl (2.5MB)      |████████████████████████████████| 2.5MB ... Collecting pycparser (from cffi>=1.12->cryptography<39,>=36.0.1->goosey==1.0.0)   Using cached https://files.pythonhosted.org/packages/62/d5/5f610ebe421e85889f2e55e33b7f9a6795bd982198517d912eb1c76e1a53/pycparser-2.21-py2.py3-none-any.whl Collecting soupsieve>1.2 (from BeautifulSoup4->webdrivermanager->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/d2/70/2c92d7bc961ba43b7b21032b7622144de5f97dec14b62226533f6940798e/soupsieve-2.4-py3-none-any.whl Collecting colorama; platform_system == "Windows" (from tqdm->webdrivermanager->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/d1/d6/3965ed04c63042e047cb6a3e6ed1a63a35087b6a609aa3a15ed8ac56c221/colorama-0.4.6-py2.py3-none-any.whl Collecting requests-oauthlib>=0.5.0 (from msrest>=0.6.21->azure-mgmt-web->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/6f/bb/5deac77a9af870143c684ab46a7934038a53eb4aa975bc0687ed6ca2c610/requests_oauthlib-1.3.1-py2.py3-none-any.whl Collecting portalocker<3,>=1.6; python_version >= "3.5" and platform_system == "Windows" (from msal-extensions<2.0.0,>=0.3.0->azure-identity->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/8c/df/d4f711d168524f5aebd7fb30969eaa31e3048cf8979688cde3b08f6e5eb8/portalocker-2.7.0-py2.py3-none-any.whl Collecting exceptiongroup (from trio-websocket~=0.9->selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/61/97/17ed81b7a8d24d8f69b62c0db37abbd8c0042d4b3fc429c73dab986e7483/exceptiongroup-1.1.1-py3-none-any.whl Collecting outcome (from trio~=0.17->selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/e9/4f/2f2d3f65d851852712b4de3fd0cfdcec9c5e9a9c347430e004ba770ef4db/outcome-1.2.0-py2.py3-none-any.whl Collecting async-generator>=1.9 (from trio~=0.17->selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/71/52/39d20e03abd0ac9159c162ec24b93fbcaa111e8400308f2465432495ca2b/async_generator-1.10-py3-none-any.whl Collecting sortedcontainers (from trio~=0.17->selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/32/46/9cb0e58b2deb7f82b84065f37f3bffeb12413f947f9388e4cac22c4621ce/sortedcontainers-2.4.0-py2.py3-none-any.whl Collecting sniffio (from trio~=0.17->selenium->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/c3/a0/5dba8ed157b0136607c7f2151db695885606968d1fae123dc3391e0cfdbf/sniffio-1.3.0-py3-none-any.whl Collecting hpack<5,>=4.0 (from h2>=4.0; python_version >= "3.6.0"->selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/d5/34/e8b383f35b77c402d28563d2b8f83159319b509bc5f760b15d60b0abf165/hpack-4.0.0-py3-none-any.whl Collecting h11<1,>=0.9.0 (from wsproto>=0.14->selenium-wire->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/95/04/ff642e65ad6b90db43e668d70ffb6736436c7ce41fcc549f4e9472234127/h11-0.14.0-py3-none-any.whl (58kB)      |████████████████████████████████| 61kB ... Collecting numpy; python_version >= "3.0" (from wxpython>=4.1.0->Gooey==<IP_ADDRESS>->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/bf/8c/3d36cef521739bd481e9a5b30e5c0f9faf8b7fe7b904238368908a9d149d/numpy-1.24.2-cp38-cp38-win_amd64.whl (14.9MB)      |████████████████████████████████| 14.9MB ... Collecting oauthlib>=3.0.0 (from requests-oauthlib>=0.5.0->msrest>=0.6.21->azure-mgmt-web->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/7e/80/cab10959dc1faead58dc8384a781dfbf93cb4d33d50988f7a69f1b7c9bbe/oauthlib-3.2.2-py3-none-any.whl (151kB)      |████████████████████████████████| 153kB ... Collecting pywin32>=226; platform_system == "Windows" (from portalocker<3,>=1.6; python_version >= "3.5" and platform_system == "Windows"->msal-extensions<2.0.0,>=0.3.0->azure-identity->goosey==1.0.0)   Downloading https://files.pythonhosted.org/packages/fa/80/a6b22e031590cc5f4fcbd5bf4bcf63a9dabce9d59065f53add99a8caaec5/pywin32-306-cp38-cp38-win_amd64.whl (9.4MB)      |████████████████████████████████| 9.4MB ... Building wheels for collected packages: cryptography, webdrivermanager, psutil   Building wheel for cryptography (PEP 517) ... error   ERROR: Command errored out with exit status 1:    command: 'C:\Users\bwjohnson\.venv\Scripts\python.exe' 'C:\Users\bwjohnson\.venv\lib\site-packages\pip\_vendor\pep517\_in_process.py' build_wheel 'C:\Users\BWJOHN~1\AppData\Local\Temp\tmpzfnmc9xt'        cwd: C:\Users\bwjohnson\AppData\Local\Temp\pip-install-3i9_eo3t\cryptography   Complete output (191 lines):   running bdist_wheel   running build   running build_py   creating build   creating build\lib.win-amd64-cpython-38   creating build\lib.win-amd64-cpython-38\cryptography   copying src\cryptography\exceptions.py -> build\lib.win-amd64-cpython-38\cryptography   copying src\cryptography\fernet.py -> build\lib.win-amd64-cpython-38\cryptography   copying src\cryptography\utils.py -> build\lib.win-amd64-cpython-38\cryptography   copying src\cryptography\__about__.py -> build\lib.win-amd64-cpython-38\cryptography   copying src\cryptography\__init__.py -> build\lib.win-amd64-cpython-38\cryptography   creating build\lib.win-amd64-cpython-38\cryptography\hazmat   copying src\cryptography\hazmat\_oid.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat   copying src\cryptography\hazmat\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat   creating build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\base.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\certificate_transparency.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\extensions.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\general_name.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\name.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\ocsp.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\oid.py -> build\lib.win-amd64-cpython-38\cryptography\x509   copying src\cryptography\x509\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\x509   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\backends   copying src\cryptography\hazmat\backends\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings   copying src\cryptography\hazmat\bindings\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\cmac.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\constant_time.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\hashes.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\hmac.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\keywrap.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\padding.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\poly1305.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\_asymmetric.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\_cipheralgorithm.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\_serialization.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   copying src\cryptography\hazmat\primitives\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\aead.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\backend.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\ciphers.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\cmac.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\decode_asn1.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\dh.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\dsa.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\ec.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\ed25519.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\ed448.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\hashes.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\hmac.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\poly1305.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\rsa.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\utils.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\x25519.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\x448.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\x509.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   copying src\cryptography\hazmat\backends\openssl\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\backends\openssl   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\openssl   copying src\cryptography\hazmat\bindings\openssl\binding.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\openssl   copying src\cryptography\hazmat\bindings\openssl\_conditional.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\openssl   copying src\cryptography\hazmat\bindings\openssl\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\openssl   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\dh.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\dsa.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\ec.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\ed25519.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\ed448.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\padding.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\rsa.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\types.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\utils.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\x25519.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\x448.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   copying src\cryptography\hazmat\primitives\asymmetric\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\asymmetric   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\ciphers   copying src\cryptography\hazmat\primitives\ciphers\aead.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\ciphers   copying src\cryptography\hazmat\primitives\ciphers\algorithms.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\ciphers   copying src\cryptography\hazmat\primitives\ciphers\base.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\ciphers   copying src\cryptography\hazmat\primitives\ciphers\modes.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\ciphers   copying src\cryptography\hazmat\primitives\ciphers\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\ciphers   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\concatkdf.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\hkdf.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\kbkdf.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\pbkdf2.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\scrypt.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\x963kdf.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   copying src\cryptography\hazmat\primitives\kdf\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\kdf   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\serialization   copying src\cryptography\hazmat\primitives\serialization\base.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\serialization   copying src\cryptography\hazmat\primitives\serialization\pkcs12.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\serialization   copying src\cryptography\hazmat\primitives\serialization\pkcs7.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\serialization   copying src\cryptography\hazmat\primitives\serialization\ssh.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\serialization   copying src\cryptography\hazmat\primitives\serialization\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\serialization   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\twofactor   copying src\cryptography\hazmat\primitives\twofactor\hotp.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\twofactor   copying src\cryptography\hazmat\primitives\twofactor\totp.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\twofactor   copying src\cryptography\hazmat\primitives\twofactor\__init__.py -> build\lib.win-amd64-cpython-38\cryptography\hazmat\primitives\twofactor   running egg_info   writing src\cryptography.egg-info\PKG-INFO   writing dependency_links to src\cryptography.egg-info\dependency_links.txt   writing requirements to src\cryptography.egg-info\requires.txt   writing top-level names to src\cryptography.egg-info\top_level.txt   reading manifest file 'src\cryptography.egg-info\SOURCES.txt'   reading manifest template 'MANIFEST.in'   no previously-included directories found matching 'docs\_build'   warning: no previously-included files found matching 'vectors'   warning: no previously-included files matching '*' found under directory 'vectors'   warning: no previously-included files matching '*' found under directory '.github'   warning: no previously-included files found matching 'release.py'   warning: no previously-included files found matching '.readthedocs.yml'   warning: no previously-included files found matching 'dev-requirements.txt'   warning: no previously-included files found matching 'tox.ini'   warning: no previously-included files found matching 'mypy.ini'   warning: no previously-included files matching '*' found under directory '.circleci'   adding license file 'LICENSE'   adding license file 'LICENSE.APACHE'   adding license file 'LICENSE.BSD'   adding license file 'LICENSE.PSF'   writing manifest file 'src\cryptography.egg-info\SOURCES.txt'   copying src\cryptography\py.typed -> build\lib.win-amd64-cpython-38\cryptography   copying src\cryptography\hazmat\bindings\_openssl.pyi -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings   creating build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\_rust   copying src\cryptography\hazmat\bindings\_rust\__init__.pyi -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\_rust   copying src\cryptography\hazmat\bindings\_rust\asn1.pyi -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\_rust   copying src\cryptography\hazmat\bindings\_rust\ocsp.pyi -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\_rust   copying src\cryptography\hazmat\bindings\_rust\x509.pyi -> build\lib.win-amd64-cpython-38\cryptography\hazmat\bindings\_rust   running build_ext   running build_rust   C:\Users\user\AppData\Local\Temp\pip-build-env-vfnp0kkv\overlay\Lib\site-packages\setuptools\command\build_py.py:202: SetuptoolsDeprecationWarning:     Installing 'cryptography.hazmat.bindings._rust' as data is deprecated, please list it in packages`.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'cryptography.hazmat.bindings._rust' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'cryptography.hazmat.bindings._rust' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

  =============================DEBUG ASSISTANCE=============================
  If you are seeing a compilation error please try the following steps to
  successfully install cryptography:
  1) Upgrade to the latest pip and try again. This will fix errors for most
     users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
  2) Read https://cryptography.io/en/latest/installation/ for specific
     instructions for your platform.
  3) Check our frequently asked questions for more information:
     https://cryptography.io/en/latest/faq/
  4) Ensure you have a recent Rust toolchain installed:
     https://cryptography.io/en/latest/installation/#rust

  Python: 3.8.2
  platform: Windows-10-10.0.22621-SP0
  pip: n/a
  setuptools: 67.6.1
  setuptools_rust: 1.5.2
  rustc: n/a
  =============================DEBUG ASSISTANCE=============================

error: can't find Rust compiler
If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.
To update pip, run:
  pip install --upgrade pip

and then retry package installation.
If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
This package requires Rust >=1.48.0.
ERROR: Failed building wheel for cryptography
Running setup.py clean for cryptography
ERROR: Command errored out with exit status 1:
command: 'C:\Users\user.venv\Scripts\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\user\AppData\Local\Temp\pip-install-3i9_eo3t\cryptography\setup.py'"'"'; file='"'"'C:\Users\user\AppData\Local\Temp\pip-install-3i9_eo3t\cryptography\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' clean --all
cwd: C:\Users\user\AppData\Local\Temp\pip-install-3i9_eo3t\cryptography
Complete output (40 lines):
running clean
removing 'build\lib.win-amd64-cpython-38' (and everything under it)
'build\bdist.win-amd64' does not exist -- can't clean it
'build\scripts-3.8' does not exist -- can't clean it
removing 'build'
running clean_rust
  =============================DEBUG ASSISTANCE=============================
  If you are seeing a compilation error please try the following steps to
  successfully install cryptography:
  1) Upgrade to the latest pip and try again. This will fix errors for most
     users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
  2) Read https://cryptography.io/en/latest/installation/ for specific
     instructions for your platform.
  3) Check our frequently asked questions for more information:
     https://cryptography.io/en/latest/faq/
  4) Ensure you have a recent Rust toolchain installed:
     https://cryptography.io/en/latest/installation/#rust

  Python: 3.8.2
  platform: Windows-10-10.0.22621-SP0
  pip: n/a
  setuptools: 67.6.1
  setuptools_rust: 1.5.2
  rustc: n/a
  =============================DEBUG ASSISTANCE=============================

error: can't find Rust compiler
If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.
To update pip, run:
  pip install --upgrade pip

and then retry package installation.
If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
This package requires Rust >=1.48.0.
ERROR: Failed cleaning build dir for cryptography
Building wheel for webdrivermanager (PEP 517) ... done
Created wheel for webdrivermanager: filename=webdrivermanager-0.10.0-cp38-none-any.whl size=19550 sha256=cc84728e530455b22e2319bb1f72554a4a251a9fd739eeb0ba3b2f094b25c947
Stored in directory: C:\Users\user\AppData\Local\pip\Cache\wheels\cd\43\72\31563a16226782c70814b46d60329d741bf6889580e3b7cc46
Building wheel for psutil (PEP 517) ... done
Created wheel for psutil: filename=psutil-5.9.4-cp38-abi3-win_amd64.whl size=247973 sha256=08c6c3abcaf561bc8dcdb0a2a1a9f3604d892f27fb5302d229fc87407254091d
Stored in directory: C:\Users\user\AppData\Local\pip\Cache\wheels\21\dc\70\1181eceb230238f228ffb9df7205799790d4afcf54a4d5f814
Successfully built webdrivermanager psutil
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly
WARNING: You are using pip version 19.2.3, however version 23.0.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.`

Figured out I needed to update pip, after that I reinstalled and it works.  Now trying to figure out authenticating.


Unable to move image when zooming in and the 'crop area' goes outside of the image

Hi, I'm having issues when a user zooms into a smallish image. If when you zoom & the image lands outside of the crop area you will be unable to move the image left so it's stuck on the side of the crop area (see below for video).
http://thepilotslife.com/videos/croppie-issues.mp4
Have you come across this before? My temp fix was to remove the boundaries and allow the user to scroll anywhere but this has lead to users cropping none of their image and returning a blank image :)!
Cheers

Something weird is definitely happening at the 2 second mark in your video where your image just suddenly shifts left.
It kind of looks like you're cropping inside of a modal, just double checking, are you calling bind after your modal is shown?
Any way you can share a code sample of how you're using croppie?

Hi Dustin, thanks for the response.
I've put my code snippet on pastebin -> http://pastebin.com/1kCgzC8V
The croppie is NOT placed inside of a modal, it's simply displayed on the first page load. You can also see this page on our dev server (futureblossomapp.devdp.com, follow the sign up process to just after you upload an image).
Cheers!

It seems like you've modified some of the croppie.css - your .cr-boundary for example has a width: 100% !important.
I see you've made some padding and margin changes in there, those should be fine, but that width might be what's causing your problem.  Can you try removing that and seeing if it fixes your problem?

Hi Dustin,
Ahh yes! it looks like that's what was causing the issue. I have removed the 100% width and it is now working as it should :).
Cheers,
Hayden


Update Basic Measurement Feedback targets

Update Basic Measurement Feedback targets based on current offerings

@swernli I agree with your point.
I've moved your suggestion to a new issue (#241) so this PR can go ahead.


feat(freespace_planning_algorithms): add Astar search by python

Description

Make the following feature into the freespace_planning_algorithms package.

Astar search class with python

add setMap() function that sets "costmap" into the Astar class
add makePlan() function in the Astar class

Tests performed

Test with the data: settings, costmap, initial pose, and goalpose.
These data were successful in finding the goal in planning simulation with autoware.
evaluator_description: feat/freespace_astar_python
2024/03/13 https://evaluation.tier4.jp/evaluation/reports/3b522d1a-59f5-56a3-aaeb-de18be2c5042/?project_id=prd_jt
-- success to find goal by python, too.
https://evaluation.tier4.jp/evaluation/reports/d4a8a1ce-15b6-5301-95c6-23092a8dbe18?project_id=prd_jt
Effects on system behavior

There is no affection in autoware by this feature.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@TakumIto
thanks for your great work!!!!
please check pre-commit.ci

you also can run in local
pre-commit run -a

@kosuke55
I modified some codes and ran pre-commit. please check it up.

@kosuke55
I would be able to make this PR more useful. So I will push more commit and then contact here.

@kosuke55 I have done updates just now.

thanks!!!!!!!!!!!!!!!!!!!!!!!!!!!

@kosuke55 I modified some typos and inserted the document. Could you check them?

@TakumIto
could you please fix spellcheck?

@kosuke55 I modified it.

hmm, please check this
3: Test command: /usr/bin/python3 "-u" "/opt/ros/humble/share/ament_cmake_test/cmake/run_test.py" "/__w/autoware.universe/autoware.universe/build/freespace_planning_algorithms/test_results/freespace_planning_algorithms/copyright.xunit.xml" "--package-name" "freespace_planning_algorithms" "--output-file" "/__w/autoware.universe/autoware.universe/build/freespace_planning_algorithms/ament_copyright/copyright.txt" "--command" "/opt/ros/humble/bin/ament_copyright" "--xunit-file" "/__w/autoware.universe/autoware.universe/build/freespace_planning_algorithms/test_results/freespace_planning_algorithms/copyright.xunit.xml"
3: Test timeout computed to be: 200
3: -- run_test.py: invoking following command in '/__w/autoware.universe/autoware.universe/planning/freespace_planning_algorithms':
3:  - /opt/ros/humble/bin/ament_copyright --xunit-file /__w/autoware.universe/autoware.universe/build/freespace_planning_algorithms/test_results/freespace_planning_algorithms/copyright.xunit.xml
3: freespace_planning_algorithms/astar_search.py: copyright=TIER IV, Inc. All rights reserved. (2024), license=<unknown>
3: scripts/bind/astar_search_pybind.cpp: copyright=TIER IV, Inc. All rights reserved. (2024), license=<unknown>
3: scripts/example/example.py: copyright=TIER IV, Inc. All rights reserved. (2024), license=<unknown>
3: 3 errors, checked 18 files
3: -- run_test.py: return code 1
3: -- run_test.py: verify result file '/__w/autoware.universe/autoware.universe/build/freespace_planning_algorithms/test_results/freespace_planning_algorithms/copyright.xunit.xml'
3/6 Test #3: copyright ............................***Failed    0.69 sec
test 4
    Start 4: cppcheck

I fixed it. Could you please check?

@TakumIto
thanks! and please check pre-coomit
trim trailing whitespace.................................................Failed
- hook id: trailing-whitespace
- exit code: 1
- files were modified by this hook

@kosuke55 Thanks!!!


How to send Image as IM

hey i am using user project as base for one of my application , i was wondering how to send image as a part of IM, i was able to achieve the same with Lync SDK where i set the "InstantMessageContentType.Gif" and pass in the base 64 string for the image. I am assuming that is what we should do here as well but i was unable to find the option to do so.

Good question. Let me try to figure it out and back to you. Please wait.

yap i'll be trying it at my end too....
thanks anyway

cannot figure it out yet... I will ask my team today.

At the end, it seems we cannot send/receive attachment via UCWA 2.0. Only plain and html text.

hey @kenakamu  I am using UCWA 2.0 for one of my implementation , i am trying to send image ....i believe it can be done as Skype for Business client which enables users to send images, i was experimenting with sending base64 image using Text/html type but it was not rendered can you tell me what should be the payload in the body of the post to
"POST https://lync.contoso.com/ucwa/oauth/v1/applications/102/communication/conversations/21a1/messaging"I have attached a image which does this post request...this is your implementation only ...previously i was able to send html content by changing the content type for the Body

Do you have a code which could send images before? Or did you resolve this by setting correct content type?

no , i don't have any code which sends images, but i am trying to resolve this issue of sending images...I was hoping you would know the correct content type


Allow dynamic and non-text header content for TableColumn

📌 User Story
One of the concessions made in PR #947 was only allowing static text content for column headers. Ultimately we want to support dynamic, and non-text content for headers as described in one of the PR comments.

This might be a duplicate of #862 but I'll let @m-akinc @atmgrifter00 or @nate-ni decide that.

This might be a duplicate of #862 but I'll let @m-akinc @atmgrifter00 or @nate-ni decide that.

This is indeed a duplicate. Closing.


Aborted (core dumped) in tf.raw_ops.ResourceSparseApplyProximalAdagrad

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.16
Custom code
Yes
OS platform and distribution
Linux Ubuntu 22.04.3 LTS (x86_64)
Mobile device
No response
Python version
3.9.13
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
On specific input, tf.raw_ops.ResourceApplyCenteredRMSProp/tf.raw_ops.ResourceSparseApplyCenteredRMSProp triggers "Aborted (core dumped)". We ran the code on colab's latest TensorFlow Nightly, which also triggers the crash. The cause of the crash may be the grad parameter.
tf.raw_ops.ResourceApplyProximalAdagrad also has the same crash.
Standalone code to reproduce the issue
import tensorflow as tf

var = tf.Variable([1.0, 2.0, 3.0])
accum = tf.Variable([0.1, 0.2, 0.3], dtype=tf.complex64)
accum2 = tf.Variable([0, 1.2, -3.3], dtype=tf.complex64)
lr = 0.01
grad = tf.constant([0.1, 0.2, 0.3])
momentum = 0.9

# crash
tf.raw_ops.ResourceSparseApplyProximalAdagrad(var=var.handle, accum=accum.handle, lr=lr,
                                              l1=0.1, l2=0.2, grad=grad,
                                              indices=tf.constant([1,2,2]),
                                              use_locking=False)
# crash
# tf.raw_ops.ResourceApplyProximalAdagrad(var=var.handle, accum=accum.handle, lr=lr, l1=1,
#                                         l2=1, grad=grad,
#                                         use_locking=False)

Relevant log output
2024-06-06 01:28:02.747576: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-06-06 01:28:02.780112: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-06-06 01:28:03.819782: F tensorflow/core/framework/tensor.cc:844] Check failed: dtype() == expected_dtype (8 vs. 1) float expected, got complex64
Aborted (core dumped)

Hi @x0w3n ,

I was able to reproduce the issue on Colab using TF v2.15 and TF-nightly ,Please find the gist here for reference.

Thank you!


Update dotnet-desktop.yml: changed names to the uploader

Description

what changes did you do?
made it better names

Argumentation

why do you think these changes should be merged?
have you considered alternatives?
are there any better solutions?
it's better names in dotnet-deskotop

hope gets merges

i mean, okay

can u fix public serive and make game make page and make so i can put servers in and logi a and register page and game maker page  and mongodb
and game updater  and windows studio can update games files in serverr and make it better and faster


Add UUPS for core contracts

Original discussion
Right now we use the diamond proxy pattern for most of our contracts (implemented as diamond facets).
We also have the core contracts that can't be used with the diamond proxy because of function clashing. Hence the different upgradability pattern should be used.
What should be done:

Apply UUPS to the core contracts:

https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/CreditNft.sol
https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/ERC1155Ubiquity.sol
https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/ERC20Ubiquity.sol
https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/StakingShare.sol
https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/UbiquityCreditToken.sol
https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/UbiquityDollarToken.sol
https://github.com/ubiquity/ubiquity-dollar/blob/development/packages/contracts/src/dollar/core/UbiquityGovernanceToken.sol

Update deployment script accordingly
Refactor tests for core contracts accordingly

P.S. Although CreditClock exists in the "core" folder it is not a "core" contract. We have plans for moving it to diamond facets.

/start

chill my friend

@Keyrxng I don't know why the bot refuses to assign you to the issue, pls try with the /start command

/start

Do you have any updates @Keyrxng? If you would like to release the bounty back to the DevPool, please comment /stop Last activity time: Fri Aug 25 2023 23:15:34 GMT+0000 (Coordinated Universal Time)

There's a linked PR, why the bot isn't picking up?

Do you have any updates @Keyrxng? If you would like to release the bounty back to the DevPool, please comment /stop Last activity time: Fri Aug 25 2023 23:15:34 GMT+0000 (Coordinated Universal Time)

There's a linked PR, why the bot isn't picking up?

Hard to say, https://github.com/ubiquity/ubiquibot/issues/729

the bot is a rebel

it looks like keyring it's gonna have this one, albeit it still need more work, let's see

New review requested

@molecula451 did not receive comment incentives here. Does anybody know why? @0xcodercrane can you check the logs in Supabase?
@ubiquity/software-development  RFC

/query @molecula451

https://gnosisscan.io/tx/0xf7a1413dd82a60715a1f8bcb38b9e7e920e68d9ab5f27a093fd16b4a6a82398e
@molecula451


Allow us call ToSqlQueryText on an IQueryable

Is your feature request related to a problem? Please describe.
Right now all LINQ queries must go through a unique GetItemLinqQueryable method. This method is different than GetItemQueryIterator and GetItemQueryStreamIterator. The default response factory for LINQ queries is to deserialize into the desired type. If I want to write a LINQ query that returns a stream iterator I cant.
For debugging purposes it's also useful to see the generated SQL statement and log it if it exceeds a certain RU cost. The v2 SDK overwrote the ToString method on the DocumentQuery to facilitate this. A string is loggable, a LINQ query is not.
Describe the solution you'd like
I'd like the SDK to allow me to convert an IQueryable to a SQL string which I can then use to pass to either GetItemQueryIterator or GetItemQueryStreamIterator. From the string I can also log the request if the response exceeds a given amount of RUs (or any other metrics).
Describe alternatives you've considered
Abandoning LINQ and just using strings or forking the repository to make a custom version.
Additional context
A LINQ query is a compile-time type safe way to write queries and IMHO is a far superior approach than writing strings which are harder to refactor and verify are correct. This seems like a local transformation task separate from the query which needs to work with response data.
It also seems like it would simplify the SDK as callers choose to use LINQ or strings and all the query APIs need is to accept a string.

Thanks for creating the issue . Will get back to you in this .

I would recommend doing ToQueryDefinition() and adding a ToString to QueryDefinition so it supports parameterized quires.


feat: convertBytesToHexString

Is your feature request related to a problem? Please describe:
I'm coming from using this old NFC reading package
https://github.com/chariotsolutions/phonegap-nfc
And it had a util function called toHex which converted a byte to its equivalent character in hexadecimal
https://github.com/chariotsolutions/phonegap-nfc/blob/d325b860af64869e4b6d7996c37d61d2492310d5/www/phonegap-nfc.js#L591
I extended this to convert an array of bytes to a string of hex chars joined by ':' which is a common representation format for an NFC ID
Describe the solution you'd like:
I've rewritten this function to have a consistent API with convertBytesToString
function convertBytesToHexString(options: { bytes: number[] }): {
  text: string;
} {
  const { bytes } = options;
  const hexCharArray = bytes.map((byte) => {
    if (byte < 0) {
      byte = 256 + byte;
    }
    let hexChar: string = byte.toString(16); // convert number to hexadecimal equivalent
    if (hexChar.length === 1) {
      hexChar = '0'.concat(hexChar);
    }
    return hexChar.toUpperCase();
  });
  return {
    text: hexCharArray.join(':'),
  };
}

If you think it could be generally useful to others, feel free to include it!

Thank you for the issue!
Yes, this helper function is currently missing and i will include it in the next release.
I also already have similar code in my nfc demo app:
https://github.com/capawesome-team/capacitor-nfc-demo/blob/main/src/app/shared/pipes/bytes-to-hex/bytes-to-hex.pipe.ts

This will be part of  v0.3.1.


Prerendered root +server.js is always saved as index.html

Describe the bug
Line 146 is incorrectly assigning the index.html name to the prerendered +server.js endpoint response because we're on the root path and the statement slices off the / character leaving us with an empty string / falsy value.
https://github.com/sveltejs/kit/blob/4559e66b649516cc996a042a21739fa165388335/packages/kit/src/core/postbuild/prerender.js#L145-L153
Reproduction
n/a
Logs
No response
System Info
n/a

Severity
serious, but I can work around it
Additional Information
No response

Is the issue still open ?
If yes can I solve it ?


Add PERMIT_DOCKER=connected-networks

This will add the networks of all eth* interfaces as trusted, which is necessary if the container is in networks that are outside of the old docker default network (<IP_ADDRESS>/12), e.g. <IP_ADDRESS>/16
See https://github.com/tomav/docker-mailserver/issues/1079#issuecomment-499903541 for a more detailed description of the problem that is solved here.

Can add:

integration test
update documentation (README)

@tomav I tried but I can't seem to get the tests working locally.
I rebased onto the current master to get green tests then I used:
$ make build-no-cache
$ make generate-accounts run generate-accounts-after-run fixtures tests

Which failed in the first fixture command:
# Setup sieve & create filtering folder (INBOX/spam)
docker cp "`pwd`/test/config/sieve/dovecot.sieve" mail:/var/mail/localhost.localdomain/user1/.dovecot.sieve
Error: No such container:path: mail:/var/mail/localhost.localdomain/user1
make: *** [Makefile:294: fixtures] Error 1

Restarted build t see if it happens again. But the issue was before the tests started.

@tomav Seems we got no luck. Could you explain the issue in more detail, maybe I can debug it locally?

Okay, I debugged and my code did run at this point. There was an error in the start-mailserver.sh that prevented postfix from running.
Maybe we could add a test that makes it more explicit that start-mailserver.sh failed before "unrelated" tests trigger?

Still the same in Travis.

The code ip addr show | grep -E 'eth[0-9]+' may fail miserably as not all network interfaces use the ethx naming convention. Two of my interfaces are called enp6s0 and enp0s31f6, for example. I would rather pass in the networks as a parameter if we want to override the current behavior.

Sorry for the sluggish response, I am currently on holiday. So to answer you directly:
@tomav

Still the same in Travis.

I was a bit unclear. My previous post was just a status report that I could confirm the issue locally. I had not pushed anything new at this point.
@erik-wramner

The code ip addr show | grep -E 'eth[0-9]+' may fail miserably as not all network interfaces use the ethx naming convention. Two of my interfaces are called enp6s0 and enp0s31f6

I just copied over what was already there for PERMIT_DOCKER=host. After some research I found this:

This [enpXsY] is known as Predictable Network Interface naming and is part of systemd, [...]
Basic idea is that [...] interface name depends on physical location of hardware [...]

What I gather from this: The enp... naming scheme is only applicable to a hardware interface managed by systemd in contrast to docker's virtual network devices. So I'd assume inside containers we always have ethX.
Nevertheless, I still find it brittle to parse for ethX: docker might decide to change the naming after all and ip addr might change its output layout.
Additionally, I'd much prefer to have a manual override to allow for adding external (non docker) networks as well.
However, in the problem context if this PR, which comes from a docker-compose use case, we cannot know the subnets of the docker networks unless we force the user to define them statically. If we require the user to name the networks via their in container adapter names, we just shift the problem of unstable names onto the user. In the worst case, a container restart changes interface names.
Do you have any preferred choice here @erik-wramner? I find the existing options to be lacking:

host -> allows for only one network and suffers from the same problem
network -> only works with the default bridge network and breaks down in docker-compose settings

If I could wish I would like to have the following interface:

User sets up container with a list of connected networks
User defines which of these networks should be permitted, using their docker names, additionally can define subnets by hand
the daemon in the container automagically resolves these network names to subnets

Unfortunately, I see no way to do step 3 within the container, unless it gets access to the docker daemon for querying.

@erik-wramner
Alternatively we could use: ip -o -4 addr show type veth | egrep -o '[0-9\.]+/[0-9]+'
This would restrict the output to on line per IPv4 virtual ethernet device and parse only subnets from the output.

I don't think you can rely on the order of the networks. I haven't seen anything about a guaranteed order and if custom networks (created manually or by other components and referenced with names) are mixed with managed networks that are created with the containers the creation order may vary, which can affect the presented order. Apart from that it seems fine.
Perhaps (enabled by an option) we could permit all the connected networks using this approach, i.e. no need to use names or indexes that we can't control?

Hm reading https://github.com/docker/compose/issues/4645 I gather that the order with docker run is predefined but docker-compose orders by network name alphabetically and in some cases randomly.

Perhaps (enabled by an option) we could permit all the connected networks using this approach
Yeah, that is the initial idea of this PR. If you are fine with that approach I will update the code to the ip command mentioned above.

I'm fine with that as it is opt-in provided that we can get the tests working. You could try to rebase your branch from master, I have spent quite some time trying to get the tests stable. Perhaps that helps. I can have a look later as well.
Please note that the tests only work on Linux, I've tried to run them on Mac and Windows without luck.

I rebased as you said and still got a failing test. However, I got the impression that the make clean did not clean up everything. Even after that git status shows changes in test/config that I never did myself. Here is the last failing test:
 ✗ checking opendkim: /etc/opendkim/KeyTable should contain 2 entries
   (from function `assert_output' in file test/test_helper/bats-assert/src/assert.bash, line 239,
    in test file test/tests.bats, line 551)
     `assert_output 2' failed

   -- output differs --
   expected : 2
   actual   : 5
   --

I'll look into it when I get time, most likely by the end of the week. I don't have access to my build environment now.

@martin-schulze-vireso the tests in Travis passed, did you change something?
I wonder what happens with the cleanup step where we delete the network if we haven't created the network (i.e. that or an earlier step failed). Will it succeed or do we need to use force or handle the error?
Plus ideally I would like to avoid hard-coding the IP range for the custom network, but I can live with that to keep things simple.

@erik-wramner

the tests in Travis passed, did you change something?
I did some changes but the tests were not correct until now.

I wonder what happens with the cleanup step where we delete the network if we haven't created the network
The cleanup is aborted at this point. I hit this problem several times during development.

Plus ideally I would like to avoid hard-coding the IP range for the custom network
I could add some code to read out the subnet from docker directly but it makes the tests more complex.

I want to give some feedback for the development process with this project:

having everything in one big test suite is very ill suited to fast feedback cycles on the development of a single test. Ideally we could have some mechanism that allows to only do setup, run and teardown of a single test?
the cleanup seems to be incomplete, there are still things left in the test/config folder after make clean which seem to trigger errors in following test runs if forgotten to remove (via git checkout)
the setup steps are guarded with many sleep directives which lengthen the tests considerably and are very device specific: a slower machine might not get enough sleep and faster ones wait without benefit. If these sleeps are there solely to guarantee availability we might want to replace them with health checks and timeouts.
as mentioned above: there seems to be no test that simply checks if the server started successfully, thus giving a host of unhelpful failing tests when the root cause should be more visible.

Together these shortcomings lead to a very long feedback loop when developing new tests. I'd be willing to work on some of those, should I open up separate tickets for each of them?

One minor thing; the new docker container mounts the test folder. I've changed the others to mount the test/test-files folder read only instead. You should have that from the rebase. Can you do the same, please?
As for the cleanup, we could either do something advanced or we can simply ignore errors. Try to run:
docker network rm ... || true
Hopefully that allows the rest of the cleanup to proceed.
I fully agree with your feedback, I'm also new to this project and have also focused on the tests. In addition to your points I don't like starting all docker containers and leaving them running. Ideally there should be a test suite per container or group of containers.
I think you could just use one ticket and then use multiple PRs for that. No need for extra admin!


Additional image verification

Empty PNG images, various defects in JPG images and so on require pre-verification, else Fussel throws errors later and stops generating its gallery.
It might be better to not use the second transpose hack that is only to get pillow to validate the image better, however verify alone did not do the job and I preferred this more complete pre-verification to catching errors later. Maybe I just don't know Pillow well enough and there is another way. Or maybe all the steps themselves could catch errors and revert/delete the so far generated data as appropriate.

@Radtoo this is awesome, thanks for the contribution. I tested it locally, all seems in order.

Thank you for your kind words and fussel, it is a nice gallery.


[CMake] Rework build and installation of all swift-syntax modules

Rework the build and installation of all swift-syntax modules in a few ways:

Unify the build of all of the libraries via add_swift_host_library to eliminate a lot of copy-and-paste.
Respect BUILD_SHARED_LIBS rather than forcing static builds: this sets us up for building shared libraries instead.
Trick CMake into building proper .swiftmodule directories
Build and install the modules into lib/swift/host in the toolchain, so other clients can use them

https://github.com/apple/swift/pull/62326
@swift-ci please test

https://github.com/apple/swift/pull/62326
@swift-ci please test

https://github.com/apple/swift/pull/62326
@swift-ci please test Linux

https://github.com/apple/swift/pull/62326
@swift-ci please clean test macOS

https://github.com/apple/swift/pull/62326
@swift-ci please test

https://github.com/apple/swift/pull/62326
@swift-ci please test

I'm turning off building with library evolution for the moment, because it's triggering some surprising failures in parsing

https://github.com/apple/swift/pull/62326
@swift-ci please test

https://github.com/apple/swift/pull/62326
@swift-ci please test


ENH: Interpolate blinks in pupil channels

Reference issue
Closes #11725
What does this implement/fix?
This implements a linear interpolation function in mne.preprocessing.eyetracking, to interpolate missing values in pupil channels during blinks.
This time I wanted to get this PR up early / in a minimal working-state, so that devs have a change to review the foundation of the code, before we add more to it next week (see additional info below). I'm definitely interested in your feedback on the code design, if there are better (or more mne-like ) approaches you think I could take, I'm happy to hear your ideas🙂
Additional information
After discussing this function yesterday with @britta-wstnr , @mscheltienne , and @drammock , here are some ideas that were suggested (feel free to let me know if i missed anything):

[ ] make the interpolation channel specific. Right now, in the case of a binocular recording (2 pupil channels), if there were a "wink" in the recording, both pupil channels would be interpolated.

[ ] to do this, we should refactor read_raw_eyelink to add channel information in the blink annotations.
[ ]  There was also a discussion of whether read_raw_eyelink should prepend blink annotations with BAD_, to be consistent with other mne functions. Then, this function would only interpolate over 'BAD_blink' annotations by default. I'm not sure if there was a resolution on this matter, and I'm not sure yet how I feel about the idea.

[ ] allow the user to specify the annotation descriptions that should be considered as blinks? something like blink_annotations=['my_manual_blink'] ? we can give it a default value of None, which will use any annotation description that starts with 'blink'.

also CC @larsoner
Minimally Working example
import mne
fname = mne.datasets.testing.data_path() / "eyetrack" / "test_eyelink.asc"

raw = mne.io.read_raw_eyelink(fname, create_annotations=["blinks"],
                              find_overlaps=True, preload=True)
mne.preprocessing.eyetracking.interpolate_blinks(raw, buffer=0.05)
raw.pick(["pupil_left", "pupil_right"])
raw.plot()

Here is the updated eye-tracking tutorial

to do this, we should refactor read_raw_eyelink to add channel information in the blink annotations

This is not a necessary step in this PR (though we should do it). You can make this function channelwise-annotation-aware without changing the reader's behavior.

whether read_raw_eyelink should prepend blink annotations with BAD_, to be consistent with other mne functions

IIRC the place we left this was "don't make the reader too smart/powerful, read in what's there in the file and then the user can use annotations.rename if they want

allow the user to specify the annotation descriptions that should be considered as blinks

I think this is a necessity. I'm not sure if list of strings, regex, callable, etc is best here

This is not a necessary step in this PR (though we should do it). You can make this function channelwise-annotation-aware without changing the reader's behavior.

The other way that I can think of doing this is to rely on the eye name being in the annotation description. But if we think that relying on the 'ch_names' key of the annotation is the best way, I don't mind doing a separate PR to update read_raw_eyelink.

Relying on the ch_names key is cleaner. The field exist to create channel-wise annotations. IMO, storing this information as part of the description will be harmful in the long run.

For blink vs BAD_blink, I agree that the reader should not be too smart/powerful. The "smarter" you make it, the more likely it will break on an edge case. Reading information without transforming it is always simpler. Moreover, BAD_blink would make sense since data isn't usable during a blink, but it would create a discrepancy with the other annotations/events read from the same file.
I would however mention clearly in the tutorial that you can rename the loaded annotations, with an example code snippet.

eyegaze is np.nan and pupil is 0

This is now sparking another question, how does MNE handle a segment during which some of the channels are np.nan?
It's not a big issue for a raw containing only eyelink channels, but once merged/synchronized with a MEG recording, it opens access to many functions. Will this np.nan segment on the eyegaze channel cause issues? Should it be clearly annotated with a channel-wise annotation?

@scott-huberty I have not read all discussion but is a path forward clear? If not, want me to read through and comment and/or we chat at some point?

@scott-huberty I have not read all discussion but is a path forward clear? If not, want me to read through and comment and/or we chat at some point?

I think so:

Make this function channelwise-annotation aware
In a separate PR, update read_raw_eyelink to store channelwise info for occular annotations.. So that this function can be easily used with data loaded from read_raw_eyelink.
We require the user to pass in the description(s) of blink anntoations?

We require the user to pass in the description(s) of blink anntoations?

To me the API of this part is still not clear. Possible inputs to a annotations_to_interpolate param might be:

string
sequence of strings
callable that returns True/False
dict that maps annotation descriptions to True/False
regex

I'd like @larsoner's perspective on this, I feel like his YAGNI radar is better than mine. (also we need a better param name than annotations_to_interpolate, maybe match?)

I would start with str | list of str because usually it's just going to be BAD_blink (or whatever we read it as by default) and adding list of str is easy once you have str. And if people really have 5+ kinds they want to interpolate we can add re support but I doubt we'll get there

@larsoner and I met this afternoon and here's a summary of our plan (for anyone to confirm or object to):

In a separate PR, update read_raw_eyelink to store channelwise info for occular annotations (this should be pretty easy/quick 🤞) .
read_raw_eyelink should prepend BAD_ to blink annotations, because, upon reading them, the data within those times are not usable.
interpolate_blinks will be channelwise-annotation aware and will act on both eyegaze and pupil data.
interpolate_blinks will have a match parameter that has a default value of BAD_blink, but users can pass in another description.
If the annotation descriptions started with 'BAD_' (i.e. 'BAD_blink'), After interpolating the 'BAD_' will be removed (i.e. blink), because the data are now usable. This is akin to how channel interpolation functions will remove the interpolated channels from info['bads']

... and just to add one more point: some of this stuff (e.g., removing the BAD_ prefix, interpolating eyegaze in addition to pupil data, etc.) could in principle be made optional later. But thinking about the 95%+ of use cases we decided it shouldn't be necessary, so let's consider making this stuff optional if people ask for it.

Ok just pushed a commit, a couple notes:
I just noticed that  scipy.interpolation.interp1d, which I was using, appears to be considered legacy API and is no longer recommended.
For a simple linear interpolation, numpy.interp  seems to be the recommendation, and it has the added benefit that if you need to interpolate a value that is at the start or end of your array, numpy.interp will just use a zero order hold interpolation on that index (i.e. it handles the aforementioned issue where a blink was at the end of the recording).

Thanks @scott-huberty !


Updated idioms/examples to RC3, fixed timestamps, removed cybox references

-Adjusted idioms to work with RC3 specs
-Reformatted timestamps to be compliant with the timestamp format in the
specs
-Removed cybox instances
-Corrected kill chain phase and external-reference formats based on the
specs

👍


Add yay package manager

As an user who manages packages with yay, I want to be able to install sesh and keep it up to date.

[ ] Update goreleaser config (https://goreleaser.com/customization/aur/)
[ ] Add README.md instructions for how to install for Arch users

Hey Josh, I'd like to give this issue a try, since I've pointed to you on the stream, I would be able to test if what is done here will work correctly

Created a PR #177 for this issue, it is just a README update since goreleaser have already publish the package to the AUR using sesh-bin as the package name.
sesh aur

I'm conisdering this done, I'll work on https://github.com/joshmedeski/sesh/issues/178 to ensure it's working as expeced.


how to include .npmrc file while deploying function?

What happened?
I am trying using a few modules from the private repo in my function. I don't know how to push my .npmrc file when I deploy the function. I tried the way shown above by setting env variable like this.(Deployment command)
*function deploy vincent --runtime nodejs6 --from-file vincentKubelessCronJob.js --handler vincentKubelessCronJob.postRequest --dependencies package.json  --namespace kubeless --schedule " /1 * * "
--env NPM_REGISTRY=
--env _auth=
--env email=
--env always-auth=
What is expected?
The function should pull the package from the private repo.
Originally posted by @gsjohal in https://github.com/kubeless/kubeless/issues/694#issuecomment-433051908

@andresmgot  I tried the way you said. The function gets deployed but the status of the functions is always not ready. the pod doesn't start up. This problem is only when I use the module from a private repo. Can you tell what could be the problem?

After adding .npmrc file to the zip file, on the logs, it says "npm ERR! 404 Not Found<EMAIL_ADDRESS>where atb-exp-api-validate is my private module. I don't understand why still I am getting this error?

is your .npmrc properly formed? Is it in the default NPM registry or is it hosted in a different registry? Note that the .npmrc file should contain a valid token if you want to access a private repository.

my .npmrc is in this format:
registry=
_auth=
email=
always-auth=true
My project works fine locally. The problem I is when I  deploy it as  kubeless function. According to logs, It says node cannot find my private modules, even though I have my npmrc file in the zip folder.
I have three files one is node js, package.json and .npmrc in my zip folder. I dont understand what wrong I am doing.
this is the command I use to deploy
kubeless function deploy  --runtime nodejs6 --from-file file.zip --handler hello.world --namespace kubeless

Mm, that, in theory, should work. This is a bit advanced but what you can do to debug it further is:

Edit the deployment to make the pod hang when installing dependencies. You can do that executing kubectl edit deployment FUNC_NAME.
Look for the command that runs npm install --production --prefix=/kubeless and replace it for tail -f /dev/null to make it hang.
Now open a shell in the new pod that gets generated. kubectl exec -it POD_NAME -c install bash.

With that you can debug in that shell if the .npmrc is properly set or if the registry is reachable from within the pod.

@gsjohal you don't need to package your .npmrc file. You can pass it as an env variable in your deploy command. If you have only nodejs file, package.json and .npmrc, I would formulate something like below.
kubeless function deploy <function_name> --runtime nodejs8 \
                                --from-file <path to your hello.js file> \
                                --handler hello.world \
                                --namespace kubeless \
                                --dependencies <path to your package.json> \
                                --env http_proxy:<httpproxy> \
                                --env https_proxy:<httpsproxy> \
                                --env HTTPS_PROXY:<httpsproxy> \
                                --env HTTP_PROXY:<httpproxy> \
                                --env no_proxy:<.svc> \
                                --env NPM_REGISTRY=<your private registry URL> \
                                --env NPM_SCOPE=<@private-registry-scope>

Let me know if this helps.
@andresmgot  is this issue because of the HOME directory setting to /kubeless  and couldn't able to overwrite or read his .npmrc?

@andresmgot is this issue because of the HOME directory setting to /kubeless and couldn't able to overwrite or read his .npmrc?

That shouldn't be an issue. The running UID has permissions to write in the /kubeless folder.

Using env variables NPM_REGISTRY and NPM_SCOPE to access private repository is fine, but our private repository has disabled guest access so we need add NpmToken what can be solved by env variable NPM_CONFIG_EXTRA.
This all works fine but i see problem in fact that runtime has still these env variables available.


Working with nginx

Since the free version of trello has limitations and i really love this example, which worked
out of the box for me, i am currious if there is an easy way to run it with nginx.
I am thinking about using it for a little project, is there a simple workaround for nginx ?
Thanks a bunch !

Angello is just HTML, JavaScript  and CSS with no application server dependencies and so it should work in nginx just fine.


check, that cats resoures are mapped to scala Using.Releasable

Scala standard library define Using.Releasable
given Using.Releasable[TestResource]
Library-specific resources should be mapped to it. (i.e. should exist given Using.Releasable[cats.Resource]).  If such a given Rekeasable is not defined in the library, we can define it here.
Add tests,
(example,  https://github.com/rssh/dotty-cps-async/blob/master/shared/src/test/scala/cps/TestCBS1ShiftUsing.scala
something like this, with the difference that test Resource should be cats[monix/zio] resource and test framework is munit here)

I don't think that Using.Releasable (from standard library) is relevant for cats.Resource. They both are designed to work with resources that need to be allocated and released, but do that differently, so cats.Resource won't work with Using.Releasable`.
But integration with cats.Resource (or zio.Managed) would still be enormously useful. Both have the .use method, just as cats.Monad (well, cats.FlatMap, to be precise) has .flatMap.
So I was thinking, that since await/! is translated by cps-async-connect to .flatMap, could ~ be translated to .use?

Let's think:
We have   Resource[F,A].use[B](A =>F[B])
What we want inside async: something like CpsResourceExtension[Resource[F,A]].use[B](A=>B)
cps transformer will modify call to f:A=>B. into call to use_async[A=>F[B]], so this will be something like
extension cpsResource[F,A](r: Resource[F,A])(using m:CpsTryMonad[F]):
    def use[B](f: A => B):  B =
         r.use( a => m.pure(a) ).   //. called when cps(code_f) === pure[B], i.e. f not include awaits

   inline def  use_async[B](f: A=>F[B]): F[B] =
        r.use(f).   // callen when cps(code_f). is async

Looks like this will do all that we need, but need to recheck and write tests.

Another question:   can we change the syntax to avoid extra brackets around use arguments.  It's need investigations in terms of CpsAsync

Finally what's work:
transparent inline def using[F[_],A, B](r:Resource[F,A])(inline f: A=>B)(using m:CpsMonad[F], cm: MonadCancel[F,Throwable]): B =
     await(r.use(a => m.pure(f(a)) ))

Usage:
 using(openFile){ buffer => .
     .... do something here, can insert awaits.
 }

(should add description to readme)

What I had in mind is not
async[Task] {
    val r = makeWriterEmu()
    val ctr = await(Ref.make(0))
    using(r) { a =>
        val c0 = await(ctr.get)
        a.write(s"AAA-${c0}")
        await(ctr.update(_ + 1))
        val c1 = await(ctr.get)
        a.write(s"BBB-${c1}")
        (a, a.messages.toList, a.isClosed)
    }
}

That syntax has a significant downside: it causes nesting. Imagine, how would the code look, if you had to work with multiple resources. It doesn't provide any advantage over calling directly .use.
Could cps-async-connect do something like
async[Task] {
    val r = makeWriterEmu()
    val ctr = await(Ref.make(0))
    val a = using(r)
    val c0 = await(ctr.get)
    a.write(s"AAA-${c0}")
    await(ctr.update(_ + 1))
    val c1 = await(ctr.get)
    a.write(s"BBB-${c1}")
    (a, a.messages.toList, a.isClosed)
}

Or even more preferably
async[Task] {
    val r = makeWriterEmu()
    val ctr = ! Ref.make(0)
    val a = ~ r
    val c0 = ! ctr.get
    a.write(s"AAA-${c0}")
    ! ctr.update(_ + 1)
    val c1 = ! ctr.get
    a.write(s"BBB-${c1}")
    (a, a.messages.toList, a.isClosed)
}

?
Thank you for your effort on this! :heart:

Сan notice that there is significantly much more magic than in automatic coloring.
Hmm,  we can't embed F in Resource[F,A],  but can embedd  F[A] into Resource[F,A].  So,  await will be enough, example:
async[[X]=>>Resource[IO,X]] {
      val reader = await(openFile(input))
      val writer = await(openFile(output))
      writer.writeAll(reader)
}

The trick is that our main monad is [X]=>>Resource[IO,X],  not IO

Oh, I don't think we need to do anything like that. The point here is that .use (just like .flatMap) returns IO/Task (.use doesn't return Resource`).

btw, for now, we have the next syntax:
asyncScope[IO] {
     val reader = await(openFile(input))
      val writer = await(openFile(output))
      writer.writeAll(reader)
}

(asyncScope[IO] internally use async[[X]=>Resource[IO,X]]. but expose IO to the external world.

Does that mean, that in asyncScope I can mix IO and Resource[IO, *]? As in
asyncScope[IO] {
  val reader = await(openFileIO(input))
  val writer = await(openFileResource(output))
  writer.writeAll(reader)
}

yes


[Team 2] User tower interaction

Description
Task: Tower pop-up inplementation.
Feature: Tower feature ticket
The task involves implementing the ways the player can interact with towers once they have been placed down. This will be done in the form of a pop-up that appears when the player clicks on a turret that has been placed, and vanish when a second click is done outside the pop-up menu. The pop-up will show the tower's statistics. The statistics give the amount of health the tower has, and if it has the capability to attack aliens, its fire rate and damage per shot.
Future Features
Once basic functionality is successfully implemented, the following avenues are considered for additional features:

Aesthetic: The pop-up menu will be redesigned to fit the aesthetic appearance of the tower build menu more closely.
Repair: The menu will contain a button to spend a small amount of money to repair some missing HP from the tower.
Selling: The menu will contain a button to delete the tower, partially refunding the cost to build it.
Upgrading: The menu will contain some buttons to upgrade the tower, spending money to improve it's statistics or add a new effect.

Example

End Functionality: Once a tower has been placed, players will be able to click on it to bring up a menu. In this menu, they will be able to determine the tower's health, including how much damage it has sustained, get an option to repair damage if it has taken any, get an option to sell the tower to get a partial refund on its cost, and have a set of upgrades they can buy to make the tower better. Clicking off the menu will close the pop-up menu.

Dependencies
List any tasks on which this ticket relies. If there is already an existing ticket, reference it using #xx. If a task needs to be implemented, and the issue does not already exist, make a new ticket and leave it unassigned for someone else to take on. Ensure other team members are aware of the issue.

[ ] Tower needs to be placed before it can be selected (#06)

Dependencies for future features:

[ ] UI designs of tower placement menu, so tower selection pop-up can match the aesthetic (Team 6)
[ ] In game cash increases/decreases for selling/upgrading/repairing the tower (Team 5)

Milestones
List of steps that need to be completed for this task.

[ ] Design a basic tower menu pop-up (Aug. 20)
[ ] Implement input handling functionality, so the system can detect when the user clicks, and if they clicked a tower (Aug. 23)
[ ] Implement the system for creating a pop-up menu when a tower is clicked on (Aug. 25)
[ ] Implement the system for deleting the pop-up menu when the user clicks outside the menu (Aug. 26)
[ ] Testing and documentation of the implemented tower interaction menu and its associated mechanisms (Aug. 28)

Completion Deadline: Aug. 29
Documentation

Main description of feature
JavaDoc
...

Member

Alasdair Sinclair (@AlasdairS4698737) (Alasdair Sinclair)

@AlasdairS4698737 This task looks great! Don't forget to assign yourself (and any other team members) and add projects and milestones.

This task has been taken up by (#34), as their feature scope covers the creation of a tower interactive menu.

Majority of this task taken up by other teams.


Update iced 0.10.0

I'll do some more testing of this today

It seems to be working pretty well with some testing and updates to libcosmic :)


Enigma M3: middle rotor II + rigtmost rotors V..VIII produces wrong results

It seems there is an issue with the roror II in Enigma tool.
Steps to reproduce:

Open Practical Cryptography's Enigma tool
Set the following values:

Plaintext: SOMESECRETMESSAGE
key settings: VEZ
ring settings: ABD
Rotors: 324
Plug board settings: GT YC EJ UA RX PN IS WB MH ZV

Press Encrypt/Decrypt
Copy cipertext value to Dencode Enigma tool
Configure Dencode Enigma tool with the above mentioned settings. (Reflector UKW-B)

Result: message is decrypted correctly.

In the Practical Cryptography's Enigma tool set rightmost rotor to 5 (to be 325)
Repeat steps 3-4

Result: message is decrypted incorrectly.

In the Practical Cryptography's Enigma tool set middle rotor to 3 (to be 335)
Repeat steps 3-4

Result: message is decrypted correctly.
So it seems that combinations of the middle rotor II + rightmost rotors V..VIII produce incorrect results.
I've also tested CacheSleuth tool, and it behaves like Practical Cryptography's one, i.e. it has no such issue.
P.S. Thanks to @the-lambda-way

This also has to do with the position / key settings. If you set the rotors to 325 with positions / key VDZ instead of VEZ, then DenCode agrees with Practical Cryptography. Note that rotor II has a turnover notch at E and rotor V has a notch at Z, so this might be related to this comment on Practical Cryptography. I've noticed issues with many Enigma tools when it comes to double stepping, and I'm not sure what the correct behavior actually is in this special case.

The behavior is certainly different.
I implemented Enigma as a separate project. The implementation for double stepping is below.
https://github.com/mozq/enigma4j/blob/d716e97a0cdff6b0fe7544746ccd44836dd6abc6/src/main/java/net/mozq/enigma4j/scrambler/ScramblerChain.java#L131-150
This implementation is based on cryptomuseum.com.
I'll look into it, but if you find anything please let me know.

According to this comment pointed out by @the-lambda-way, the behavior of DenCode seems to be fine. I also checked on Universal Enigma and cryptii, but they are the same as DenCode.
Practical Cryptography's Enigma tool and CacheSleuth use almost the same JavaScript code. Based on the behavior, they may be stepping the middle rotor twice at once.