Exception : Invalid status

~/scripts/kaspa-ledger/app-kaspa ~/scripts/kaspa-ledger/app-kaspa
ledger virtualenv already exists
Looking in indexes: https://pypi.org/simple, https://test.pypi.org/simple/
Collecting pytest (from -r tests/requirements.txt (line 1))
  Using cached pytest-7.4.4-py3-none-any.whl.metadata (7.9 kB)
Collecting ragger>=1.6.0 (from ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached https://test-files.pythonhosted.org/packages/cf/8e/287bc16d0b27c769c50a7aa30aaa5d1515bdc65dc304fa20f2509fd142e0/ragger-1.13.1-py3-none-any.whl.metadata (10 kB)
Collecting Jinja2==3.1.2 (from -r tests/requirements.txt (line 4))
  Using cached https://test-files.pythonhosted.org/packages/bc/c3/f068337a370801f372f2f8f6bad74a5c140f6fda3d9de154052708dd3c65/Jinja2-3.1.2-py3-none-any.whl (133 kB)
Collecting Flask==2.1.2 (from -r tests/requirements.txt (line 5))
  Using cached https://test-files.pythonhosted.org/packages/ba/76/e9580e494eaf6f09710b0f3b9000c9c0363e44af5390be32bb0394165853/Flask-2.1.2-py3-none-any.whl (95 kB)
Collecting safe-pysha3<2.0.0,>=1.0.0 (from -r tests/requirements.txt (line 6))
  Using cached safe_pysha3-1.0.4-cp311-cp311-linux_x86_64.whl
Collecting secp256k1>=0.14.0 (from -r tests/requirements.txt (line 7))
  Using cached secp256k1-0.14.0-cp311-cp311-linux_x86_64.whl
Collecting Werkzeug==2.2.2 (from -r tests/requirements.txt (line 8))
  Using cached https://test-files.pythonhosted.org/packages/c8/27/be6ddbcf60115305205de79c29004a0c6bc53cec814f733467b1bb89386d/Werkzeug-2.2.2-py3-none-any.whl (232 kB)
Collecting MarkupSafe>=2.0 (from Jinja2==3.1.2->-r tests/requirements.txt (line 4))
  Using cached https://test-files.pythonhosted.org/packages/fe/21/2eff1de472ca6c99ec3993eab11308787b9879af9ca8bbceb4868cf4f2ca/MarkupSafe-2.1.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.0 kB)
Collecting itsdangerous>=2.0 (from Flask==2.1.2->-r tests/requirements.txt (line 5))
  Using cached https://test-files.pythonhosted.org/packages/68/5f/447e04e828f47465eeab35b5d408b7ebaaaee207f48b7136c5a7267a30ae/itsdangerous-2.1.2-py3-none-any.whl (15 kB)
Collecting click>=8.0 (from Flask==2.1.2->-r tests/requirements.txt (line 5))
  Using cached https://test-files.pythonhosted.org/packages/00/2e/d53fa4befbf2cfa713304affc7ca780ce4fc1fd8710527771b58311a3229/click-8.1.7-py3-none-any.whl.metadata (3.0 kB)
Collecting iniconfig (from pytest->-r tests/requirements.txt (line 1))
  Using cached https://test-files.pythonhosted.org/packages/ef/a6/62565a6e1cf69e10f5727360368e451d4b7f58beeac6173dc9db836a5b46/iniconfig-2.0.0-py3-none-any.whl (5.9 kB)
Collecting packaging (from pytest->-r tests/requirements.txt (line 1))
  Using cached packaging-23.2-py3-none-any.whl.metadata (3.2 kB)
Collecting pluggy<2.0,>=0.12 (from pytest->-r tests/requirements.txt (line 1))
  Using cached pluggy-1.3.0-py3-none-any.whl.metadata (4.3 kB)
Collecting bip-utils>=2.4.0 (from ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached bip_utils-2.9.0-py3-none-any.whl.metadata (12 kB)
Collecting py-sr25519-bindings<0.3.0,>=0.2.0 (from ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached py_sr25519_bindings-0.2.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.1 MB)
Collecting cffi>=1.3.0 (from secp256k1>=0.14.0->-r tests/requirements.txt (line 7))
  Using cached cffi-1.16.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting ledgerwallet>=0.2.3 (from ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached https://test-files.pythonhosted.org/packages/f5/57/6ca5bdf650d28231ae91c463476b34d82dbcb01ce758788cd3bd626b12b2/ledgerwallet-0.4.0-py3-none-any.whl.metadata (7.7 kB)
Collecting pyqt5 (from ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached PyQt5-5.15.10-cp37-abi3-manylinux_2_17_x86_64.whl.metadata (2.1 kB)
Collecting pytesseract (from ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached pytesseract-0.3.10-py3-none-any.whl (14 kB)
Collecting speculos>=0.2.8 (from ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached https://test-files.pythonhosted.org/packages/59/c9/719addf2554b84f6228095b56e39c28ac2999bd076e845ca6ffcbce473b9/speculos-0.4.1-py3-none-any.whl.metadata (4.2 kB)
Collecting cbor2~=5.1 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached cbor2-5.5.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.0 kB)
Collecting coincurve<19.0.0,>=15.0.1 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached coincurve-18.0.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.4 MB)
Collecting crcmod~=1.7 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached crcmod-1.7-cp311-cp311-linux_x86_64.whl
Collecting ecdsa~=0.15 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached ecdsa-0.18.0-py2.py3-none-any.whl (142 kB)
Collecting ed25519-blake2b~=1.4 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached ed25519_blake2b-1.4-cp311-cp311-linux_x86_64.whl
Collecting pycryptodome~=3.6 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached pycryptodome-3.19.1-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.4 kB)
Collecting pynacl~=1.4 (from bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached PyNaCl-1.5.0-cp36-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (856 kB)
Collecting pycparser (from cffi>=1.3.0->secp256k1>=0.14.0->-r tests/requirements.txt (line 7))
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting construct>=2.10 (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached construct-2.10.70-py3-none-any.whl.metadata (4.2 kB)
Collecting cryptography>=2.5 (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached cryptography-41.0.7-cp37-abi3-manylinux_2_28_x86_64.whl.metadata (5.2 kB)
Collecting hidapi (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached hidapi-0.14.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.3 kB)
Collecting intelhex (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached intelhex-2.3.0-py2.py3-none-any.whl (50 kB)
Collecting Pillow (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached pillow-10.2.0-cp311-cp311-manylinux_2_28_x86_64.whl.metadata (9.7 kB)
Collecting protobuf<4,>=3.20 (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached https://test-files.pythonhosted.org/packages/8d/14/619e24a4c70df2901e1f4dbc50a6291eb63a759172558df326347dce1f0d/protobuf-3.20.3-py2.py3-none-any.whl (162 kB)
Collecting requests (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting tabulate (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached https://test-files.pythonhosted.org/packages/40/44/4a5f08c96eb108af5cb50b41f76142f0afa346dfa99d5296fe7202a11854/tabulate-0.9.0-py3-none-any.whl (35 kB)
Collecting toml (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Collecting flask-restful<1.0,>=0.3.9 (from speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached Flask_RESTful-0.3.10-py2.py3-none-any.whl.metadata (1.0 kB)
Collecting jsonschema<4.18.0,>=3.2.0 (from speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached jsonschema-4.17.3-py3-none-any.whl (90 kB)
Collecting mnemonic<1.0,>=0.19 (from speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached https://test-files.pythonhosted.org/packages/57/48/5abb16ce7f9d97b728e6b97c704ceaa614362e0847651f379ed0511942a0/mnemonic-0.21-py3-none-any.whl.metadata (3.4 kB)
Collecting Pillow (from ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached Pillow-9.5.0-cp311-cp311-manylinux_2_28_x86_64.whl (3.4 MB)
Collecting pyelftools<1.0,>=0.27 (from speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached pyelftools-0.30-py2.py3-none-any.whl.metadata (381 bytes)
Collecting PyQt5-sip<13,>=12.13 (from pyqt5->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached PyQt5_sip-12.13.0-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.whl.metadata (504 bytes)
Collecting PyQt5-Qt5>=5.15.2 (from pyqt5->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached PyQt5_Qt5-5.15.2-py3-none-manylinux2014_x86_64.whl (59.9 MB)
Collecting asn1crypto (from coincurve<19.0.0,>=15.0.1->bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached asn1crypto-1.5.1-py2.py3-none-any.whl (105 kB)
Collecting six>=1.9.0 (from ecdsa~=0.15->bip-utils>=2.4.0->ragger>=1.6.0->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting aniso8601>=0.82 (from flask-restful<1.0,>=0.3.9->speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached aniso8601-9.0.1-py2.py3-none-any.whl (52 kB)
Collecting pytz (from flask-restful<1.0,>=0.3.9->speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached pytz-2023.3.post1-py2.py3-none-any.whl.metadata (22 kB)
Collecting attrs>=17.4.0 (from jsonschema<4.18.0,>=3.2.0->speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached https://test-files.pythonhosted.org/packages/e0/44/827b2a91a5816512fcaf3cc4ebc465ccd5d598c45cefa6703fcf4a79018f/attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)
Collecting pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0 (from jsonschema<4.18.0,>=3.2.0->speculos>=0.2.8->ragger[speculos]>=1.6.0->-r tests/requirements.txt (line 2))
  Using cached https://test-files.pythonhosted.org/packages/3d/fc/ebf798e52db8052fc64979950272cb352066700b1918d0360341a3952814/pyrsistent-0.20.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (27 kB)
Collecting charset-normalizer<4,>=2 (from requests->ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting idna<4,>=2.5 (from requests->ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached idna-3.6-py3-none-any.whl.metadata (9.9 kB)
Collecting urllib3<3,>=1.21.1 (from requests->ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached urllib3-2.1.0-py3-none-any.whl.metadata (6.4 kB)
Collecting certifi>=2017.4.17 (from requests->ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3))
  Using cached certifi-2023.11.17-py3-none-any.whl.metadata (2.2 kB)
Requirement already satisfied: setuptools>=19.0 in ./ledger/lib/python3.11/site-packages (from hidapi->ledgerwallet>=0.2.3->ragger[ledgerwallet]>=1.6.0->-r tests/requirements.txt (line 3)) (69.0.2)
Using cached pytest-7.4.4-py3-none-any.whl (325 kB)
Using cached https://test-files.pythonhosted.org/packages/cf/8e/287bc16d0b27c769c50a7aa30aaa5d1515bdc65dc304fa20f2509fd142e0/ragger-1.13.1-py3-none-any.whl (141 kB)
Using cached bip_utils-2.9.0-py3-none-any.whl (588 kB)
Using cached cffi-1.16.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (464 kB)
Using cached https://test-files.pythonhosted.org/packages/00/2e/d53fa4befbf2cfa713304affc7ca780ce4fc1fd8710527771b58311a3229/click-8.1.7-py3-none-any.whl (97 kB)
Using cached https://test-files.pythonhosted.org/packages/f5/57/6ca5bdf650d28231ae91c463476b34d82dbcb01ce758788cd3bd626b12b2/ledgerwallet-0.4.0-py3-none-any.whl (33 kB)
Using cached https://test-files.pythonhosted.org/packages/fe/21/2eff1de472ca6c99ec3993eab11308787b9879af9ca8bbceb4868cf4f2ca/MarkupSafe-2.1.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (28 kB)
Using cached pluggy-1.3.0-py3-none-any.whl (18 kB)
Using cached https://test-files.pythonhosted.org/packages/59/c9/719addf2554b84f6228095b56e39c28ac2999bd076e845ca6ffcbce473b9/speculos-0.4.1-py3-none-any.whl (12.0 MB)
Using cached PyQt5-5.15.10-cp37-abi3-manylinux_2_17_x86_64.whl (8.2 MB)
Using cached packaging-23.2-py3-none-any.whl (53 kB)
Using cached cbor2-5.5.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (235 kB)
Using cached construct-2.10.70-py3-none-any.whl (63 kB)
Using cached cryptography-41.0.7-cp37-abi3-manylinux_2_28_x86_64.whl (4.4 MB)
Using cached Flask_RESTful-0.3.10-py2.py3-none-any.whl (26 kB)
Using cached https://test-files.pythonhosted.org/packages/57/48/5abb16ce7f9d97b728e6b97c704ceaa614362e0847651f379ed0511942a0/mnemonic-0.21-py3-none-any.whl (92 kB)
Using cached pycryptodome-3.19.1-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.1 MB)
Using cached pyelftools-0.30-py2.py3-none-any.whl (177 kB)
Using cached PyQt5_sip-12.13.0-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.whl (346 kB)
Using cached requests-2.31.0-py3-none-any.whl (62 kB)
Using cached hidapi-0.14.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (923 kB)
Using cached https://test-files.pythonhosted.org/packages/e0/44/827b2a91a5816512fcaf3cc4ebc465ccd5d598c45cefa6703fcf4a79018f/attrs-23.2.0-py3-none-any.whl (60 kB)
Using cached certifi-2023.11.17-py3-none-any.whl (162 kB)
Using cached charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (140 kB)
Using cached idna-3.6-py3-none-any.whl (61 kB)
Using cached https://test-files.pythonhosted.org/packages/3d/fc/ebf798e52db8052fc64979950272cb352066700b1918d0360341a3952814/pyrsistent-0.20.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (120 kB)
Using cached urllib3-2.1.0-py3-none-any.whl (104 kB)
Using cached pytz-2023.3.post1-py2.py3-none-any.whl (502 kB)
Installing collected packages: safe-pysha3, pytz, PyQt5-Qt5, pyelftools, py-sr25519-bindings, intelhex, ed25519-blake2b, crcmod, asn1crypto, aniso8601, urllib3, toml, tabulate, six, pyrsistent, PyQt5-sip, pycryptodome, pycparser, protobuf, pluggy, Pillow, packaging, mnemonic, MarkupSafe, itsdangerous, iniconfig, idna, hidapi, construct, click, charset-normalizer, certifi, cbor2, attrs, Werkzeug, requests, pytest, pytesseract, pyqt5, jsonschema, Jinja2, ecdsa, cffi, secp256k1, pynacl, Flask, cryptography, coincurve, ledgerwallet, flask-restful, bip-utils, speculos, ragger
Successfully installed Flask-2.1.2 Jinja2-3.1.2 MarkupSafe-2.1.3 Pillow-9.5.0 PyQt5-Qt5-5.15.2 PyQt5-sip-12.13.0 Werkzeug-2.2.2 aniso8601-9.0.1 asn1crypto-1.5.1 attrs-23.2.0 bip-utils-2.9.0 cbor2-5.5.1 certifi-2023.11.17 cffi-1.16.0 charset-normalizer-3.3.2 click-8.1.7 coincurve-18.0.0 construct-2.10.70 crcmod-1.7 cryptography-41.0.7 ecdsa-0.18.0 ed25519-blake2b-1.4 flask-restful-0.3.10 hidapi-0.14.0 idna-3.6 iniconfig-2.0.0 intelhex-2.3.0 itsdangerous-2.1.2 jsonschema-4.17.3 ledgerwallet-0.4.0 mnemonic-0.21 packaging-23.2 pluggy-1.3.0 protobuf-3.20.3 py-sr25519-bindings-0.2.0 pycparser-2.21 pycryptodome-3.19.1 pyelftools-0.30 pynacl-1.5.0 pyqt5-5.15.10 pyrsistent-0.20.0 pytesseract-0.3.10 pytest-7.4.4 pytz-2023.3.post1 ragger-1.13.1 requests-2.31.0 safe-pysha3-1.0.4 secp256k1-0.14.0 six-1.16.0 speculos-0.4.1 tabulate-0.9.0 toml-0.10.2 urllib3-2.1.0

[notice] A new release of pip is available: 23.3.1 -> 23.3.2
[notice] To update, run: pip install --upgrade pip
Collecting ledgerblue
  Using cached ledgerblue-0.1.48-py3-none-any.whl
Requirement already satisfied: pyelftools<1.0,>=0.29 in ./ledger/lib/python3.11/site-packages (from ledgerblue) (0.30)
Requirement already satisfied: hidapi>=0.7.99 in ./ledger/lib/python3.11/site-packages (from ledgerblue) (0.14.0)
Requirement already satisfied: protobuf>=2.6.1 in ./ledger/lib/python3.11/site-packages (from ledgerblue) (3.20.3)
Collecting pycryptodomex>=3.6.1 (from ledgerblue)
  Using cached pycryptodomex-3.19.1-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.4 kB)
Collecting future (from ledgerblue)
  Using cached future-0.18.3-py3-none-any.whl
Collecting ecpy>=0.9.0 (from ledgerblue)
  Using cached ECPy-1.2.5-py3-none-any.whl (43 kB)
Requirement already satisfied: pillow>=3.4.0 in ./ledger/lib/python3.11/site-packages (from ledgerblue) (9.5.0)
Collecting python-u2flib-host>=3.0.2 (from ledgerblue)
  Using cached python_u2flib_host-3.0.3-py3-none-any.whl
Collecting websocket-client>=0.56.0 (from ledgerblue)
  Using cached websocket_client-1.7.0-py3-none-any.whl.metadata (7.9 kB)
Collecting nfcpy>=1.0.4 (from ledgerblue)
  Using cached nfcpy-1.0.4-py3-none-any.whl (186 kB)
Collecting bleak>=0.20.1 (from ledgerblue)
  Using cached bleak-0.21.1-py3-none-any.whl.metadata (5.3 kB)
Requirement already satisfied: pycryptodome>=3.18.0 in ./ledger/lib/python3.11/site-packages (from ledgerblue) (3.19.1)
Collecting python-gnupg>=0.5.0 (from ledgerblue)
  Using cached python_gnupg-0.5.2-py2.py3-none-any.whl.metadata (1.9 kB)
Collecting dbus-fast<3,>=1.83.0 (from bleak>=0.20.1->ledgerblue)
  Using cached dbus_fast-2.21.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (10 kB)
Collecting typing-extensions>=4.7.0 (from bleak>=0.20.1->ledgerblue)
  Using cached typing_extensions-4.9.0-py3-none-any.whl.metadata (3.0 kB)
Requirement already satisfied: setuptools>=19.0 in ./ledger/lib/python3.11/site-packages (from hidapi>=0.7.99->ledgerblue) (69.0.2)
Collecting libusb1 (from nfcpy>=1.0.4->ledgerblue)
  Using cached libusb1-3.1.0-py3-none-any.whl.metadata (15 kB)
Collecting pyserial (from nfcpy>=1.0.4->ledgerblue)
  Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
Collecting ndeflib (from nfcpy>=1.0.4->ledgerblue)
  Using cached ndeflib-0.3.3-py2.py3-none-any.whl (56 kB)
Collecting pydes (from nfcpy>=1.0.4->ledgerblue)
  Using cached pyDes-2.0.1-py2.py3-none-any.whl
Requirement already satisfied: requests in ./ledger/lib/python3.11/site-packages (from python-u2flib-host>=3.0.2->ledgerblue) (2.31.0)
Requirement already satisfied: charset-normalizer<4,>=2 in ./ledger/lib/python3.11/site-packages (from requests->python-u2flib-host>=3.0.2->ledgerblue) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in ./ledger/lib/python3.11/site-packages (from requests->python-u2flib-host>=3.0.2->ledgerblue) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./ledger/lib/python3.11/site-packages (from requests->python-u2flib-host>=3.0.2->ledgerblue) (2.1.0)
Requirement already satisfied: certifi>=2017.4.17 in ./ledger/lib/python3.11/site-packages (from requests->python-u2flib-host>=3.0.2->ledgerblue) (2023.11.17)
Using cached bleak-0.21.1-py3-none-any.whl (137 kB)
Using cached pycryptodomex-3.19.1-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.1 MB)
Using cached python_gnupg-0.5.2-py2.py3-none-any.whl (20 kB)
Using cached websocket_client-1.7.0-py3-none-any.whl (58 kB)
Using cached dbus_fast-2.21.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.4 MB)
Using cached typing_extensions-4.9.0-py3-none-any.whl (32 kB)
Using cached libusb1-3.1.0-py3-none-any.whl (62 kB)
Installing collected packages: python-gnupg, pyserial, pydes, ndeflib, libusb1, ecpy, websocket-client, typing-extensions, pycryptodomex, nfcpy, future, dbus-fast, python-u2flib-host, bleak, ledgerblue
Successfully installed bleak-0.21.1 dbus-fast-2.21.0 ecpy-1.2.5 future-0.18.3 ledgerblue-0.1.48 libusb1-3.1.0 ndeflib-0.3.3 nfcpy-1.0.4 pycryptodomex-3.19.1 pydes-2.0.1 pyserial-3.5 python-gnupg-0.5.2 python-u2flib-host-3.0.3 typing-extensions-4.9.0 websocket-client-1.7.0

[notice] A new release of pip is available: 23.3.1 -> 23.3.2
[notice] To update, run: pip install --upgrade pip
cat: debug/app.map: Nie ma takiego pliku ani katalogu
cat: debug/app.map: Nie ma takiego pliku ani katalogu
nanosp
Prepare directories
[GLYPH] Compiling...
[CC]   build/nanos2/obj/address.o
[CC]   build/nanos2/obj/app_main.o
[CC]   build/nanos2/obj/app_metadata.o
[CC]   build/nanos2/obj/bagl.o
[CC]   build/nanos2/obj/bagl_display.o
[CC]   build/nanos2/obj/bagl_fonts.o
[CC]   build/nanos2/obj/bagl_glyphs.o
[CC]   build/nanos2/obj/base58.o
[CC]   build/nanos2/obj/bip32.o
[CC]   build/nanos2/obj/blake2b.o
[CC]   build/nanos2/obj/buffer.o
[CC]   build/nanos2/obj/cashaddr.o
[CC]   build/nanos2/obj/checks.o
[CC]   build/nanos2/obj/crypto.o
[CC]   build/nanos2/obj/crypto_helpers.o
[AS]   build/nanos2/obj/cx_stubs.o
[CC]   build/nanos2/obj/cx_wrappers.o
[CC]   build/nanos2/obj/debug.o
[CC]   build/nanos2/obj/deserialize.o
[CC]   build/nanos2/obj/dispatcher.o
[CC]   build/nanos2/obj/format.o
[CC]   build/nanos2/obj/format_local.o
[CC]   build/nanos2/obj/get_app_name.o
[CC]   build/nanos2/obj/get_public_key.o
[CC]   build/nanos2/obj/get_version.o
[CC]   build/nanos2/obj/glyphs.o
[CC]   build/nanos2/obj/io.o
[CC]   build/nanos2/obj/ledger_assert.o
[CC]   build/nanos2/obj/ledger_protocol.o
[CC]   build/nanos2/obj/main.o
[CC]   build/nanos2/obj/menu_bagl.o
[CC]   build/nanos2/obj/menu_nbgl.o
[CC]   build/nanos2/obj/nbgl_display_address.o
[CC]   build/nanos2/obj/nbgl_display_message.o
[CC]   build/nanos2/obj/nbgl_display_transaction.o
[CC]   build/nanos2/obj/os.o
[CC]   build/nanos2/obj/os_io_seproxyhal.o
[CC]   build/nanos2/obj/os_io_task.o
[CC]   build/nanos2/obj/os_io_usb.o
[CC]   build/nanos2/obj/os_printf.o
[CC]   build/nanos2/obj/parser.o
[CC]   build/nanos2/obj/personal_message.o
[CC]   build/nanos2/obj/pic.o
[CC]   build/nanos2/obj/read.o
[CC]   build/nanos2/obj/send_reponse.o
[CC]   build/nanos2/obj/serialize.o
[CC]   build/nanos2/obj/sighash.o
[CC]   build/nanos2/obj/sign_msg.o
[CC]   build/nanos2/obj/sign_tx.o
[CC]   build/nanos2/obj/stack_protector.o
[AS]   build/nanos2/obj/stack_protector_init.o
[AS]   build/nanos2/obj/svc_call.o
[AS]   build/nanos2/obj/svc_cx_call.o
[CC]   build/nanos2/obj/swap_utils.o
[CC]   build/nanos2/obj/syscalls.o
[CC]   build/nanos2/obj/tx_validate.o
[CC]   build/nanos2/obj/u2f_impl.o
[CC]   build/nanos2/obj/u2f_io.o
[CC]   build/nanos2/obj/usbd_ccid_cmd.o
[CC]   build/nanos2/obj/usbd_ccid_core.o
[CC]   build/nanos2/obj/usbd_ccid_if.o
[CC]   build/nanos2/obj/usbd_conf.o
[CC]   build/nanos2/obj/usbd_core.o
[CC]   build/nanos2/obj/usbd_ctlreq.o
[CC]   build/nanos2/obj/usbd_hid.o
[CC]   build/nanos2/obj/usbd_impl.o
[CC]   build/nanos2/obj/usbd_ioreq.o
[CC]   build/nanos2/obj/utils.o
[CC]   build/nanos2/obj/ux_flow_engine.o
[CC]   build/nanos2/obj/ux_layout_bb.o
[CC]   build/nanos2/obj/ux_layout_bn.o
[CC]   build/nanos2/obj/ux_layout_bnn.o
[CC]   build/nanos2/obj/ux_layout_bnnn.o
[CC]   build/nanos2/obj/ux_layout_nn.o
[CC]   build/nanos2/obj/ux_layout_nnbnn.o
[CC]   build/nanos2/obj/ux_layout_nnn.o
[CC]   build/nanos2/obj/ux_layout_nnnn.o
[CC]   build/nanos2/obj/ux_layout_pages.o
[CC]   build/nanos2/obj/ux_layout_paging.o
[CC]   build/nanos2/obj/ux_layout_paging_compute.o
[CC]   build/nanos2/obj/ux_layout_pb.o
[CC]   build/nanos2/obj/ux_layout_pbb.o
[CC]   build/nanos2/obj/ux_layout_pbn.o
[CC]   build/nanos2/obj/ux_layout_pn.o
[CC]   build/nanos2/obj/ux_layout_pnn.o
[CC]   build/nanos2/obj/ux_layout_utils.o
[CC]   build/nanos2/obj/ux_legacy.o
[CC]   build/nanos2/obj/ux_menulist.o
[CC]   build/nanos2/obj/ux_stack.o
[CC]   build/nanos2/obj/validate.o
[CC]   build/nanos2/obj/varint.o
[CC]   build/nanos2/obj/write.o
[LINK] build/nanos2/bin/app.elf
[CP] build/nanos2/bin/app.elf => bin/app.elf
[CP] build/nanos2/bin/app.hex => bin/app.hex
[CP] build/nanos2/dbg/app.map => debug/app.map
[CP] build/nanos2/bin/app.apdu => bin/app.apdu
[CP] build/nanos2/bin/app.sha256 => bin/app.sha256
[CP] build/nanos2/dbg/app.asm => debug/app.asm
Generated random root public key : b'0452f677d4f20234a61d2f57df9be70a6d932d2ae6c17de4ed68907ca4d494a1577af4bfaba98cffe3e74bf2423c936ef07fd4cfd2aeb12fa33d6f04e91f3e9890'
Using test master key b'0452f677d4f20234a61d2f57df9be70a6d932d2ae6c17de4ed68907ca4d494a1577af4bfaba98cffe3e74bf2423c936ef07fd4cfd2aeb12fa33d6f04e91f3e9890'
Using ephemeral key b'040aef479f0705a0482e319ec0bb71d08205c98321d0dfa03f524534bfd189c776e6b214f89575920f6a942f680bf5d94062d4b50ef7fb48abb10b10a044cbfc8f'
Broken certificate chain - loading from user key
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/patryk/scripts/kaspa-ledger/app-kaspa/ledger/lib/python3.11/site-packages/ledgerblue/loadApp.py", line 253, in <module>
    loader.createApp(code_length, args.apiLevel, args.dataSize, paramsSize, args.appFlags, args.bootAddr|1)
  File "/home/patryk/scripts/kaspa-ledger/app-kaspa/ledger/lib/python3.11/site-packages/ledgerblue/hexLoader.py", line 374, in createApp
    self.exchange(self.cla, 0x00, 0x00, 0x00, data)
  File "/home/patryk/scripts/kaspa-ledger/app-kaspa/ledger/lib/python3.11/site-packages/ledgerblue/hexLoader.py", line 207, in exchange
    return self.scpUnwrap(bytes(self.card.exchange(apdu)))
                                ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/patryk/scripts/kaspa-ledger/app-kaspa/ledger/lib/python3.11/site-packages/ledgerblue/comm.py", line 157, in exchange
    raise CommException("Invalid status %04x (%s)" % (sw, possibleCause), sw, response)
ledgerblue.commException.CommException: Exception : Invalid status 511f (Unknown reason)

Can someone tell me why after I allow install from unsafe manager the installation crashes with Exception?

What firmware version are you using?
This is a Nano S+ correct?

What firmware version are you using?
This is a Nano S+ correct?

1.1.1
Yes it is S+
Only change I made is replacing pysha3 to safe-pysha3 in tests/requirements.txt because of error during compiling wheels for pysha3

Same thing on my laptop, even without changing pysha3 to safe-pysha3

@coderofstuff So will be any patch for this?


Is it possible to replace model or add new img、fearture and use them while server.py running?

Technically it would be possible.


Cert-manager don't renew certs created by ingress

Describe the bug:
We use cert-manager 1.4 into k8s. The certificates are issued by ingress networking.k8s.io/v1beta1. Problem is only renew certificates when restart the cert-manager pod, after this the cert-manager pod never update any cert.
Logs after renew certificates (only when the pod is new) and then no try to renew more certs (kubectl logs cert-manager-pod):
W0117 14:27:32.944386       1 warnings.go:70] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
I0117 14:29:05.966728       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.ClusterIssuer total 0 items received
I0117 14:30:07.969401       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Certificate total 10 items received
I0117 14:30:11.108469       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 0 items received
I0117 14:30:56.918702       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Service total 4 items received
I0117 14:31:56.198912       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.CertificateRequest total 7 items received
I0117 14:32:00.989103       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Issuer total 0 items received
I0117 14:32:04.091060       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Pod total 5 items received
I0117 14:32:46.930719       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Challenge total 4 items received
I0117 14:33:26.246308       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Order total 0 items received
I0117 14:33:26.945281       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1beta1.Ingress total 0 items received
W0117 14:33:26.946672       1 warnings.go:70] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
...
and again and again

Code:
   $ kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.4.0/cert-manager.yaml

Expected behaviour:
Should be renew certificates. We have 3 environments and only renew certificates in "renewal time" when the pod is recreated. After a minutes, only recieve the logs showed (verbose v=4).
Steps to reproduce the bug:
Generate a new certificate by the secret into ingress. When the renewal time is in range of time to renew it, cert-manager not renew this certificate. In cert-manager pod logs only showed the info and warning of the resources.
Environment details::

Kubernetes version: 1.21
Cloud-provider/provisioner: EKS
cert-manager version:  1.4.0
Install method: e.g. helm/static manifests - statis manifest (publish by ArgoCD deploy)

/kind bug

Could you please upgrade to the latest cert-manager version and see if that fixes the issue?
It sounds like you may have hit this bug https://github.com/jetstack/cert-manager/pull/4399

This week we try to upgrade version to 1.5.2 and seem like the problem persist, never renew certificates:
I0126 08:36:26.997548       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Certificate total 9 items received
I0126 08:36:41.932036       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Ingress total 3 items received
I0126 08:36:56.073209       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 9 items received
I0126 08:37:00.931054       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Service total 7 items received
I0126 08:37:34.179477       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Order total 10 items received
I0126 08:37:35.834585       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 10 items received
I0126 08:37:57.087251       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Pod total 13 items received
I0126 08:39:40.994942       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Issuer total 5 items received
I0126 08:41:56.001256       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.ClusterIssuer total 3 items received
I0126 08:42:13.184268       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.CertificateRequest total 0 items received
I0126 08:42:14.001151       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Certificate total 0 items received
I0126 08:42:19.926242       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Challenge total 0 items received
I0126 08:43:20.076740       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 0 items received
I0126 08:43:45.933100       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Service total 3 items received
I0126 08:44:47.181753       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Order total 3 items received
I0126 08:45:49.935473       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Ingress total 3 items received
I0126 08:46:36.091382       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Pod total 3 items received
I0126 08:47:08.837611       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 3 items received
I0126 08:48:57.999352       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Issuer total 4 items received
I0126 08:50:41.003599       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Certificate total 6 items received
I0126 08:50:49.184165       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Order total 0 items received
I0126 08:50:50.013797       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.ClusterIssuer total 3 items received
I0126 08:51:22.188195       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.CertificateRequest total 5 items received
I0126 08:51:35.945760       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Challenge total 4 items received
I0126 08:52:19.935341       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Service total 1 items received
I0126 08:52:32.840637       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 0 items received
I0126 08:53:13.078771       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Secret total 9 items received
I0126 08:53:32.937946       1 reflector.go:530] external/io_k8s_client_go/tools/cache/reflector.go:167: Watch close - *v1.Ingress total 0 items received

Again and again and no more logs in verbose -v=4
And the certificates only renew when kill cert-manager pod and new pod is started. Also, every time that restart pod and renew some cert with renewal time, a new certificaterequest is created...
CertificateRequest example:
certificate1         True                True    letsencrypt       system:serviceaccount:cert-manager:cert-manager   15d
certificate1        True                True    letsencrypt       system:serviceaccount:cert-manager:cert-manager   92d
certificate2          True                True    letsencrypt-dev   system:serviceaccount:cert-manager:cert-manager   15d
certificate2           True                True    letsencrypt-dev   system:serviceaccount:cert-manager:cert-manager   92d

install:
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.2/cert-manager.yaml

Only changing the cert-manager role from AWS in the ServiceAccount (to DNS validating) and the deployment args (to resolve DNS and validate certs).
Some idea?

a new certificaterequest is created

this is the expected behaviour, there should be a new CertificateRequest for each issuance

Generate a new certificate by the secret into ingress

To clarify- the renewal works in a way that for the same Certificate custom resource, a new CertificateRequest is created which results in issuance of a new TLS cert which gets written to the same Kubernetes Secret.
So what you see is that the cert written to Secret does not get updated and also that there is no CertificateRequest created at the renewal time (i.e the time recorded on Certificate.status.renewalTime)?
Perhaps you could provide the specs and statuses (showing also renewalTime of any of those Certificates that aren't getting renewed? Would you also be able to provide a full log from the controller pod from the moment you restart the pod?

We don't have any cert renewal time near, because the certs deployed by our ingress are issued by clusterissuer, and when try to change renewal time or expriration, the configuration no change and put default 90 days. But now checking the logs, we can see this:
Certificate status:
Status:
  Conditions:
    Last Transition Time:  2021-11-02T15:19:45Z
    Message:               Certificate is up to date and has not expired
    Observed Generation:   1
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2022-04-11T10:20:32Z
  Not Before:              2022-01-11T10:20:33Z
  Renewal Time:            2022-03-12T10:20:32Z
  Revision:                2
Events:                    <none>

Two certificaterequests of this cert:
acme-crt-first-service-2bcs6                 True                True    letsencrypt-dev   system:serviceaccount:cert-manager:cert-manager   85d
acme-crt-first-service-mflf6                 True                True    letsencrypt-dev   system:serviceaccount:cert-manager:cert-manager   15d

The second renewal was after day 60, see the days, forced by my kill cert-manager pod (v1.4.0). And the new cert-manager (1.5.2) say this:
E0127 07:45:19.587921       1 util.go:80] cert-manager/controller/certificaterequests/handleOwnedResource "msg"="error getting referenced owning resource" "error"="certificaterequest.cert-manager.io \"acme-crt-first-service-2bcs6\" not found" "related_resource_kind"="CertificateRequest" "related_resource_name"="acme-crt-first-service-2bcs6" "related_resource_namespace"="default" "resource_kind"="Order" "resource_name"="acme-crt-first-service-2bcs6-2467856329" "resource_namespace"="default" "resource_version"="v1"
E0127 07:45:19.582132       1 util.go:80] cert-manager/controller/certificaterequests/handleOwnedResource "msg"="error getting referenced owning resource" "error"="certificaterequest.cert-manager.io \"acme-crt-first-service-mflf6\" not found" "related_resource_kind"="CertificateRequest" "related_resource_name"="acme-crt-first-service-mflf6" "related_resource_namespace"="default" "resource_kind"="Order" "resource_name"="acme-crt-first-service-mflf6-2467856329" "resource_namespace"="default" "resource_version"="v1"

All certificate request are showed into error logs. Seem like the new cert-manager can't manage older certificaterequests?
Also, more ingress showed as info, because we have 2 ingress using the same cert, and 1 of these say:
I0127 07:45:19.184493       1 sync.go:374] cert-manager/controller/ingress-shim "msg"="certificate resource is not owned by this object. refusing to update non-owned certificate resource for object" "related_resource_kind"="Certificate" "related_resource_name"="acme-crt-first-service" "related_resource_namespace"="default" "related_resource_version"="v1" "resource_kind"="Ingress" "resource_name"="application-fisrt-service-ingress" "resource_namespace"="default" "resource_version"="v1"

No more errors or warnings of a cert showed, before the logs of the  first post.
Thanks,

Trying to change renewal time in selfsigned cert:
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: test-selfsigned
spec:
  selfSigned: {}
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: selfsigned-cert
spec:
  dnsNames:
    - example.com
  duration: 1h # 90d
  renewBefore: 30m # 15d
  secretName: selfsigned-cert-tls
  issuerRef:
    name: test-selfsigned

Status and renewal time in cert after an hour:
Status:
  Conditions:
    Last Transition Time:  2022-01-27T08:37:52Z
    Message:               Certificate is up to date and has not expired
    Observed Generation:   1
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2022-04-27T08:36:52Z
  Not Before:              2022-01-27T08:36:52Z
  Renewal Time:            2022-04-27T08:06:52Z
Events:                    <none>

logs pod cert-manager about selfsigned cert:
I0127 07:45:02.258926       1 controller.go:85] cert-manager/controller "msg"="enabled controllers: [certificaterequests-approver certificaterequests-issuer-acme certificaterequests-issuer-ca certificaterequests-issuer-selfsigned certificaterequests-issuer-vault certificaterequests-issuer-venafi certificates-issuing certificates-key-manager certificates-metrics certificates-readiness certificates-request-manager certificates-revision-manager certificates-trigger challenges clusterissuers ingress-shim issuers orders]"
I0127 07:45:18.957795       1 controller.go:163] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-selfsigned"
I0127 07:45:18.958493       1 controller.go:186] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-selfsigned"
I0127 08:36:51.629506       1 conditions.go:95] Setting lastTransitionTime for Issuer "test-selfsigned" condition "Ready" to 2022-01-27 08:36:51.629481187 +0000 UTC m=+3109.449034176
I0127 08:36:51.829265       1 trigger_controller.go:181] cert-manager/controller/certificates-trigger "msg"="Certificate must be re-issued" "key"="default/selfsigned-cert" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I0127 08:36:51.829340       1 conditions.go:201] Setting lastTransitionTime for Certificate "selfsigned-cert" condition "Issuing" to 2022-01-27 08:36:51.829337194 +0000 UTC m=+3109.648890184
I0127 08:36:51.829250       1 conditions.go:201] Setting lastTransitionTime for Certificate "selfsigned-cert" condition "Ready" to 2022-01-27 08:36:51.829241754 +0000 UTC m=+3109.648794747
I0127 08:36:51.885359       1 controller.go:161] cert-manager/controller/certificates-trigger "msg"="re-queuing item due to optimistic locking on resource" "key"="default/selfsigned-cert" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"selfsigned-cert\": the object has been modified; please apply your changes to the latest version and try again"
I0127 08:36:51.885521       1 trigger_controller.go:181] cert-manager/controller/certificates-trigger "msg"="Certificate must be re-issued" "key"="default/selfsigned-cert" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I0127 08:36:51.885622       1 conditions.go:201] Setting lastTransitionTime for Certificate "selfsigned-cert" condition "Issuing" to 2022-01-27 08:36:51.885615306 +0000 UTC m=+3109.705168292
I0127 08:36:52.190139       1 controller.go:161] cert-manager/controller/certificates-key-manager "msg"="re-queuing item due to optimistic locking on resource" "key"="default/selfsigned-cert" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"selfsigned-cert\": the object has been modified; please apply your changes to the latest version and try again"
I0127 08:36:52.215405       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "selfsigned-cert-qpklf" condition "Approved" to 2022-01-27 08:36:52.215396241 +0000 UTC m=+3110.034949235
I0127 08:36:52.248814       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "selfsigned-cert-qpklf" condition "Ready" to 2022-01-27 08:36:52.248804348 +0000 UTC m=+3110.068357328
I0127 08:36:52.281166       1 conditions.go:190] Found status change for Certificate "selfsigned-cert" condition "Ready": "False" -> "True"; setting lastTransitionTime to 2022-01-27 08:36:52.281155863 +0000 UTC m=+3110.100708857
I0127 08:36:52.301785       1 controller.go:161] cert-manager/controller/certificates-readiness "msg"="re-queuing item due to optimistic locking on resource" "key"="default/selfsigned-cert" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"selfsigned-cert\": the object has been modified; please apply your changes to the latest version and try again"
I0127 08:36:52.302268       1 conditions.go:190] Found status change for Certificate "selfsigned-cert" condition "Ready": "False" -> "True"; setting lastTransitionTime to 2022-01-27 08:36:52.302259959 +0000 UTC m=+3110.121813054
I0127 08:36:52.320729       1 controller.go:161] cert-manager/controller/certificates-issuing "msg"="re-queuing item due to optimistic locking on resource" "key"="default/selfsigned-cert" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"selfsigned-cert\": the object has been modified; please apply your changes to the latest version and try again"
I0127 08:36:52.321434       1 controller.go:161] cert-manager/controller/certificates-key-manager "msg"="re-queuing item due to optimistic locking on resource" "key"="default/selfsigned-cert" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"selfsigned-cert\": the object has been modified; please apply your changes to the latest version and try again"
E0127 08:37:47.016803       1 controller.go:133] cert-manager/controller/issuers "msg"="issuer in work queue no longer exists" "error"="issuer.cert-manager.io \"test-selfsigned\" not found"
E0127 08:37:47.089772       1 readiness_controller.go:142] cert-manager/controller/certificates-readiness "msg"="certificate not found for key" "error"="certificate.cert-manager.io \"selfsigned-cert\" not found" "key"="default/selfsigned-cert"
E0127 08:37:47.089822       1 revisionmanager_controller.go:106] cert-manager/controller/certificates-revision-manager "msg"="certificate not found for key" "error"="certificate.cert-manager.io \"selfsigned-cert\" not found" "key"="default/selfsigned-cert"
E0127 08:37:47.089863       1 requestmanager_controller.go:136] cert-manager/controller/certificates-request-manager "msg"="certificate not found for key" "error"="certificate.cert-manager.io \"selfsigned-cert\" not found" "key"="default/selfsigned-cert"
E0127 08:37:47.089880       1 keymanager_controller.go:139] cert-manager/controller/certificates-key-manager "msg"="certificate not found for key" "error"="certificate.cert-manager.io \"selfsigned-cert\" not found" "key"="default/selfsigned-cert"
E0127 08:37:47.089917       1 trigger_controller.go:137] cert-manager/controller/certificates-trigger "msg"="certificate not found for key" "error"="certificate.cert-manager.io \"selfsigned-cert\" not found" "key"="default/selfsigned-cert"
E0127 08:37:47.089934       1 issuing_controller.go:152] cert-manager/controller/certificates-issuing "msg"="certificate not found for key" "error"="certificate.cert-manager.io \"selfsigned-cert\" not found" "key"="default/selfsigned-cert"
I0127 08:37:52.808720       1 conditions.go:95] Setting lastTransitionTime for Issuer "test-selfsigned" condition "Ready" to 2022-01-27 08:37:52.808708036 +0000 UTC m=+3170.628261013
I0127 08:37:52.961401       1 conditions.go:201] Setting lastTransitionTime for Certificate "selfsigned-cert" condition "Ready" to 2022-01-27 08:37:52.961390819 +0000 UTC m=+3170.780943805

I didn't realize that you are still on v1.5.2.
The fix for https://github.com/jetstack/cert-manager/pull/4399 is not included in v1.5.2, so that explains why you still had the issue after upgrading.
Can you please upgrade to the latest cert-manager version (this is now v1.7)? I believe that should fix the issue as it looks to be the same as #4399
Generally, we always recommend to have the latest release installed and if upgrading to a minor release, it should be the latest patch release of the minor release.

Ok, but the most near renewal time in a cert is 2022-02-12.... We install 1.7.0 and wait, because can't change renewal time into selfsigned or ingress deploy certificate. Thanks!

Hi all,
After upgrade version to 1.7.0, the older and new certificates are being renewal at certificate "renewat time". All seem working fine.
Thanks!


Diags: Use the declared type for diagnosing inheritance from final class

Otherwise we do not reflect the lexical scope of nested superclass declarations.

@swift-ci please smoke test


[Snyk] Upgrade showdown from 1.5.1 to 1.9.1

Snyk has created this PR to upgrade showdown from 1.5.1 to 1.9.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 26 versions ahead of your current version.

The recommended version was released on 5 years ago.

Issues fixed by the recommended upgrade:

Issue
Score
Exploit Maturity

Reverse TabnabbingSNYK-JS-SHOWDOWN-469487
380
No Known Exploit

Release notes

Package name: showdown

1.9.1 - 2019-11-02Bug Fixes

openLinksInNewWindow: add rel="noopener noreferrer" to links (1cd281f), closes #670

Dependecy update

yargs: update yargs to latest version ^14.2 (dae65c6)

1.9.0 - 2018-11-10Version 1.9.0 introduces a new feature, the HTML to Markdown converter. This feature is still experimental and is a partial backport of the new Reverse Converter planned for version 2.0.
Bug Fixes

italicsAndBold: fix issue with consecutive spans (#608) (5c0d67e), closes #544
underline: fix issue with consecutive spans (81edc70)

Features

converter.makeMarkdown: [EXPERIMENTAL] add an HTML to MD converter (e4b0e69), closes #388 #233

1.8.7 - 2018-10-16Bug Fixes

emojis: fix emoji excessive size (4aca41c)
gfm-codeblocks:

add support for spaces before language declaration (24bf7b1), closes #569
leading space no longer breaks gfm codeblocks (828c32f), closes #523

images: fix js error when using image references (980e702), closes #585
literalMidWordAsterisks: now parses single characters enclosed by * correctly (fe70e45), closes #478
mentions: allow for usernames with dot, underscore and dash (dfeb1e2), closes #574
nbsp: fix replacing of nbsp with regular spaces (8bc1f42)

1.8.6 - 2017-12-22

1.8.5 - 2017-12-10

1.8.4 - 2017-12-05

1.8.3 - 2017-11-28

1.8.2 - 2017-11-11

1.8.1 - 2017-11-01

1.8.0 - 2017-10-24

1.7.6 - 2017-10-06

1.7.5 - 2017-10-02

1.7.4 - 2017-09-08

1.7.3 - 2017-08-23

1.7.2 - 2017-08-05

1.7.1 - 2017-06-02

1.7.0 - 2017-06-01

1.6.4 - 2017-02-06

1.6.3 - 2017-01-30

1.6.2 - 2017-01-29

1.6.1 - 2017-01-28

1.6.0 - 2017-01-09

1.5.5 - 2016-12-30

1.5.4 - 2016-12-23

1.5.3 - 2016-12-19

1.5.2 - 2016-12-17

1.5.1 - 2016-12-01

    from showdown GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.
Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Archipelo Digest
The branch digest for this pull request is being generated will be available at: https://app.archipelo.com/project/org_IbH0cHymyk0evY6l/834966279/branch/snyk-upgrade-94e69a9193a18e9b2eedb96d97201d2e/3


Typo "eqiality" in CaseEx.ard

In Line 33 of PartI/src/Exercises/CaseEx.ard, "equality" is misspelled as "eqiality".

You can pull request


Search Death records by Date of Birth/Age at death

Backend task for Search Death records by Date of Birth/Age at death.

@Vino-S how are things going on this one?

Search Ralph Alcock, min death age 70 in top box, 100 in bottom gives error: that min age should not exceed max, so put 100 in to and 70 in bottom and got this odd result:

i

Tried dob search for a death.
Errror:
**Extracted source (around line #1227):
1225
1226
1227
1228
1229
1230
def date_array date
date.split('-')
end
def dob_exact_match**

Hi @PatReynolds , I have a screenshot for Ralph Alcock  Age Range search below. Are these the expected results? The results are ordered by Date

Thanks Vino, that's the expected result. Also tried a search myself and the search page now works as expected, too.


Remove task_list_id and task_list_type from project

Changes
These two Project attributes are now redundant:
task_list_id
task_list_type
Remove the two columns from projects. Update the documentation to reflect that we've now moved to the TasksData model.
Checklist

[ ] Attach this pull request to the appropriate card in Trello.
[ ] Update the CHANGELOG.md if needed.

 Remove task_list_id and task_list_type from Project


There is a problem with the document

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception
Identify the driver
If a driver that is responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. You can use dx (display debugger object model expression), a debugger command, to display this: dx KiBugCheckDriver.
The dx KiBugCheckDriver command is no longer available
Error details:
9: kd> dx KiBugCheckDriver
Type information missing error for KiBugCheckDriver
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: KiBugCheckDriver                              ***
***                                                                   ***
*************************************************************************
Error: Unable to bind name 'KiBugCheckDriver'

@skrandy - In my testing, the dx KiBugCheckDriver is functional, so I don't believe there is an error in the docs. Typically, the error output shown, indicates that the symbols are missing for that build of Windows on the symbol server that you are accessing. For more information about troubleshooting symbols, see Symbol Problems While Debugging. The use of !sym noisy can be helpful in watching symbol loading.  Even with symbols being available for that version of Windows, it is very possible that the specific crash was not able to identify a faulting driver, so that information may not be present, or even corrupted.  For further assistance with troubleshooting 0x3B, you may have success posting your question in the following debugging forum.
OSR's windbg List


Reformat README.md

Sorry for I remember the wrong python version.
The async def syntax start at python 3.6

Lets keep it at Python 3.7+.

I don't want to go out of my way to support lower versions


Few improvements for OO part

Fix a few typos, reword a few sentences
Tweak layout and alignments on a few slides
Use float literals instead of int to show how it's done
Please check this: Add an override on a c++98 slide to give a good example of modern style. Should I update the c++98 label in the top corner?

@sponce

Ok, the things that were discussed above are done. Ready to merge.


map not updating

up until 2 days ago was working fine and now it updates on the first room i open. Freezes and does not update any new rooms unlocked and boss rooms aren't highlighted either. have reset/uninstalled multiple times.

It's working now 5/25 thanks i was hoping i wasn't going to have to take a break from cg.


Add RTL Support

This is an enhancement or feature.
Summary
As you might know, some writing systems are written and read from right to left (mainly Persian, Arabic & Hebrew).  These types of writings need extra formatting for web.
In this PR I added the support for RTL direction with the minimum changes in the code by only adding an extra css file, & not changing the html structures and leaving zero side effect for the original left to right view.
These changes are just meant to be proof of concept and are not final changes. I was not sure if RTL support is a concern for the project or not, but if it is, then I'll be more than happy to make them ready for a final review.
Context
RTL support was previously mentioned in #3903 but the suggested changes where affecting the original LTR direction.
Live Demo
Here's a live demo of the RTL support.

@ha36d I noticed you have submitted a related PR (#4884), 15 minutes before me. 😅
I'll be glad if we can work on it together.

@ha36d I noticed you have submitted a related PR (#4884), 15 minutes before me. 😅 I'll be glad if we can work on it together.

Yes, Sure. I was moving from blogger to jekyll. So I needed RTL support on this theme.

Awesome! The changes I suggested are activated by adding a
direction: ltr

to the site settings sections in _config.yml.
Here's the config for the demo link mentioned in the PR description.

For me, it is the same. But I am not introducing css changes. It only makes the body page "RTL". I guess still we need the body direction in "rtl".

Correct. I added the body direction to CSS, but I think adding the dir attribute is more appropriate.
But the rest of the CSS extensions were needed to keep to meaning of the template.

Correct. I added the body direction to CSS, but I think adding the dir attribute is more appropriate. But the rest of the CSS extensions were needed to keep to meaning of the template.

Agreed. you can copy the documentation part from mine. I will close my PR.

Thanks! Cherry picked your doc change! 🙌🏻

Looks decent. I have one minor concern: For the configuration key, why did you choose direction: rtl instead of a boolean key like rtl: true? To me it seems easier to maintain and you don't have to mention the default value (which is actually null).

Thanks for the feedback @iBug, that totally makes sense!
I also noticed the toc does not expand in mobile view which is not the as original version. I'll fix both soon and ask for your review.
Also I thought maybe it's better to inject a rtl value into body's attributes, instead of loading a whole new file and then have the rtl condition styles next to the parts their original style is defined. I think that would be easier to maintain and if someone decided to change the style, they would also notice there's a rtl counterpart. What do you think?

Aaaaah, there's actually an exact example in the scss docs:
  // It can also be used to style the outer selector in a certain context, such
  // as a body set to use a right-to-left language.
  [dir=rtl] & {
    margin-left: 0;
    margin-right: 10px;
  }

@iBug I pushed the change you mentioned + fix for the bug I saw on small screen view.
Also made the removing separate rtl file suggestion in the 3rd commit (50bd4eaff924ec49b551dffeaa0b10bb9f67ced3).
If you think it's OK, I'll fixup it to the first commit, but if you don't like that, I can drop it.
Thanks! 🙌🏻

Seems sufficiently good for now so I've merged it. If you have any further improvements feel free to open another PR.
One potential improvement I can think of is replacing all affected margins and paddings with padding-block-start and similar, so that you don't have to, for example, set *-left: 0 while *-right: (original value). Browser support for these direction-agnostic CSS properties are not to be worried.

I've pushed ded2d87b2bddecabbd1f4c9d6b7558ec450a9dc9 and I wonder if you'd like to help test it (e.g. remote_theme: "mmistakes/minimal-mistakes@ded2d87b2bddecabbd1f4c9d6b7558ec450a9dc9").

Sorry for late reply.
All my test cases look valid on the changes! They look great! 🙌🏻

Hi, thanks for your work. It would be great to dynamically adjust the direction of the paragraph based on the used language.
Just like the way that GitHub handles RTL languages in rendered markdown views:
همانطور که مشاهده می‌کنید، جهت این پاراگراف از راست به چپ است.

@srezasm If you use Kramdown's syntax for adding HTML attributes, you'll automatically have RTL for only specified paragraphs:
This is some text.

This is some more text.
{: dir="rtl" }

@iBug Can it be automated by the language that paragraph is started with?

@iBug It works with dir="auto" as well, but still, I will need to add this at the end of each paragraph manually.

@srezasm You can probably just add one dir="auto" to the <body> element as this attribute can be inherited.

@iBug Didn't work, do you know how to add it to all individual text placeholder tags?


[Master] Some refactoring and fail if bp binary is not found adjacent to bluepill binary

TL;DR Rebasing changes from https://github.com/linkedin/bluepill/pull/378 to be merged into master
Major change: Do not look for bp binary on PATH and simply fail if it is not found adjacent to the bluepill binary.
Also did some refactoring, cleanup and improvements like...

Moved a helper method to utils
Enhancing error messages and better error handling
Fixing asserts in tests
Renaming variables

P.S: Works best if pushed after https://github.com/linkedin/bluepill/pull/379
\cc @ob @jmkk Please review.

@ob Thank you Oscar, for your review. Please merge it as soon as the checks are done.
I wish the checks do not take 1+ hours, on each and every commit!


Is the geometry of high quality?

Firstly, thank you very much for your excellent work! When I tried your code, I found that the quality of the rendering in some scenes of the hypernerf dataset by 4d-gs was not good. In these monocular scenes, is there a need to add some additional supervision to improve the geometry? Also, could it be possible that the final trained deformation field is overfitting to rgb? This is just my guess. Have you conducted any related experiments? Thanks for your reply!

Hi, thanks for your nice problem!
I encountered the same problem, I've tried to supervise the training process with depth and it seems to improve rendering quality. However, overfitting to training images is an existing problem. Maybe adding the disturbance in time  mentioned in deformable 3DGS will ease the issue (I guess).
Besides, I'm also working hard to train a better 4DGS to fit any other dataset. If you have any ideas to improve 4DGS, please feel free to contact to me.
Best,
Guanjun

Thank you for your information!
Yes, I also believe that adding depth or optical flow supervision can enhance geometry. However, I recently tried to use optical flow supervision, and without adding this additional loss, I supervised the rendering of flow only with the existing loss. I found a significant discrepancy between the flow map rendered from the Gaussian deformed through the deformation field and the flow map estimated by some excellent estimators. I have previously added optical flow supervision in static GS work, which can significantly improve the quality of geometry. Therefore, I think the deformation block of 4dgs is not robust enough.

There's other 4D GS models that use deformation and it's not a great solution (honestly this 4D-GS seems like a better approach then most), plus introduces new issues that hex planes methods avoids. For example with the banana scene, a deformable model might find it challenging to model the appearance and geometry of the banana slices after they have been cut as they might not be present in the canonical field (as part of a canonical+deformable model). Also for sparse scenes (where geometry is going to suffer the most), I have seen some methods periodically use D-SSIM loss to improve the multi-view aspect ( for 6DoF). They use it every 1000 epochs or so as D-SSIM can be a bottle neck. Methods like Sparse-Controlled GS (for 4-D) also use "control" points, essentially the same way hierarchical voxel geometry works, just with point clouds. Seems there are some regularizers for these that can deal with rigid motions better compared to unconstrained solutions


Add skill relationships to user

Closes #120.
This adds missing skill relationships to the user and tests they are present in the view.

This is ready for review.

Looks good and straightforward to me. :+1: Not sure why build is failing, though.

@begedin failing for timeout, just rebuilt.


producer.send function options

Thank you for the awesome module supporting so many neat features!
I'm struggling with its API though. It's not clear from the README what are the producer.send() function options.

The first argument is a message. Although, the message can have property message. So it's unclear what "message" is. Either the first argument, or the property of the first argument.
Sometimes it says that it's not message but messages. I assume, but not sure, that the first argument can be an array.
And the most important! The second options argument possible properties are not listed anywhere. All I see is the Producer options. Could you update the README with the .send function options please?

Thank you so much

Слава Україні :)

Can you please point me at the place where the first argument to .send is called message?

First argument to send is either a:

single data structure containing topic, partition, key and message value
or the array of the above structures

Its codec, retries, batch options in the same structure as in Producer constructor.

Its quite easy to get all the answers by looking at the send code and its head doc: https://github.com/oleksiyk/kafka/blob/master/lib/producer.js#L129

@oleksiyk but @koresar is right, there is no description of particular producer.send() method unless you want users look into the code. 😉

I believe a simple PR would solve the issue for Olexiy. I'll see what I can
do.
On Sun, 8 May 2016, 18:02 Alexander Makarenko<EMAIL_ADDRESS>wrote:

@oleksiyk https://github.com/oleksiyk but @koresar
https://github.com/koresar is right, there is no description of
particular producer.send() method unless you want users look into the
code. 😉
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/oleksiyk/kafka/issues/54#issuecomment-217702437

@olexiyk answering your question. Here it is:

While doing the #56 I realized that the value property must be string.

I guess you mean the value property of the message structure? It can be either a String or a Buffer. It is up to the user to transform arbitrary object into the Buffer.


PPC64 Link problems on AIX

Link issue on GCC119. Too much output to paste on GitHub and Pastebin.
failed-link.zip

Output from make -jN is not exactly helpful as it's impossible to navigate among multi-line outputs from different programs. Submit output from make without -j argument. You claim an error, but the only error message there is is "interrupted system call", as if ^C was pressed. And if it was something else, then it still sounds rather as external problem that we can't be held responsible for. If you are alarmed by duplicate symbol warnings, you have to keep in mind that those are warnings. And since vendor or any of AIX users didn't claim that this poses a problem, it's assumed benign. After all, make test does pass. If you claim it's a problem, then present a test case. [On related note it's not unlike that majority of AIX users prefer vendor compiler, and there are no warnings if you use xlc.]


STEP-6: Add repository layer

Add repository layer
Acceptance Criteria:

Spring Data added
Entities added

Implements in https://github.com/EllsaG/power-supply-design/pull/37 pull request.


Fix all remaining field partials in preview mode

One thing this is going to have a big impact on is how the forms look in preview mode now - effectively, it's just going to look like a form in which all fields are not editable, whereas before, it tried to simplify the view to only show text or simplified widget, like an actual "view screen" for a record.
I'm not saying it needs to be done in this PR, but I would propose that we'll need to follow up perhaps with some CSS that tries to go back to that look, because I personally liked that look.

Yeah, I'll need to see a before / after screenshot, preferably with the "Records" update / preview views from the test plugin

@LukeTowers Any idea why we're getting this error in Code Quality check?

@mjauvin the issue is that whole PHP block at the top of the field-range partial is indented, when it should not be - it should be inline with the <?php tag.

@mjauvin the issue is that whole PHP block at the top of the field-range partial is indented, when it should not be - it should be aligned to the same column as the <?php tag.

@LukeTowers please don't fix things that aren't broken... :stuck_out_tongue_winking_eye:

@mjauvin I disagree with that coding style rule :P

@mjauvin I disagree with that coding style rule :P

Ok, feel free to change it! :)

@LukeTowers technically it's not a rule specific to the templates but to PHP in general.
ie. You can't do this.
<?php
    namespace My\Plugin;

    class MyClass
    {
        // ...
    }

@mjauvin is there still any interest in getting this merged?

Personally, nope!


chore: bumped intl package version

Can you elaborate more on why that is needed?
^ allows 0.17 and 0.18 and 0.19 and any non major version update so having a bigger version pool is easier for users don't you think?

As I'm aware the package is not compatible with the project using ^0.19 intl dependency.
Because my_package depends on ftp_server from path which depends on intl ^0.17.0, intl ^0.17.0 is required.
So, because my_package depends on intl ^0.19.0, version solving failed.

0.0.7 released, thank you for your contribution.


bower main should not be min file

as per bower.json specification.  main file should not be minimized.  could you fix that?
main": "lib/jsonp.min.js",

Done!


Utilising the currently blank space on the right-hand side

We currently leave a lot of unused space on the right-hand side of the screen:

What are the current plans for this space? My understanding is that we condensed the document text to the middle so that line-lengths wouldn't be too long (this is known to cause fatigue when reading). However, some users have reported that they preferred the longer line length.
Docsy uses the right space for a second sidebar that includes helpful links, some of which would equally apply to us:

Perhaps a similar sidebar that's optionally collapsible? Equally though those links could be implemented as icons in the top-right of the header and we use this space for something else.

I mostly use the spec at half width (so 1280 or 960 pixels) on my monitor, because I usually have an editor open on the other side. On my bigger monitor this looks like this (side by side, both at my preferred width):

There is significantly less content visible in the new spec at this size. Especially on smaller screen, that makes it much easier to get lost. The lines are also so short, that most blocks are about 10 lines high. At that line count, it can become easy to get lost vertically in a paragraph and a longer line length actually helps. At full screen the line length is pretty good, so I'd say it is mostly the margin on the right, that causes issues here.
Related to that. the old spec uses a font size of 0.9, with a paragraph spacing of 1 and line spacing 1.5. This makes it much easier to distinguish different paragraphs and as such get less easily lost inside a paragraph. The new spec using line spacing 1.5, font size 1 and paragraph spacing of 1, so paragraphs are visually close to each other and take more lines to fit the same content.


debug: debugged algorithm error is not reported

HKube micro-service
node-wrapper
Describe the bug
my code fails on error the Algorunner catches it and sends the error via WebSocket but for some reason, it does not fail the job.
Expected behavior
fail the job
To Reproduce
Steps to reproduce the behavior:

run code with debugging on node.js with something that fails on runtime
run debug from the dashboard
the job is still active

Additional context
node wrapper version 2.0.50

There is no handling of errorMessage message in the debug worker.

tested on
systemVersion: "v2.3.18",
fullSystemVersion: "v2.3.18-1648462268639",


Add initial types for fgraphql

Summary
Add initial version of types for fgraphql. This was erroring (for some reason, not quite sure why though) in my project, which was generated by feathers+ cli. So I thought I'd get these started.

[x] Tell us about the problem your pull request is solving.
[x] Are there any open issues that are related to this?
#467
[ ] Is this PR dependent on PRs in other repos?

Other Information
There are a few enhancements that we could do still, to query, runtime, parse function return and possibly resolvers (a generic type for ResolverMap)
Docs issue #466
question: Why is there an async version and a non-async version. As far as I can tell they are actually the same implementation, with different keywords

Thanks for the effort. We do need typings for fgraphql. https://medium.com/@eddyystop/fgraphql-feathers-graphql-hook-38faee75dd1
Unfortunately the tests are not passing.
Setting APT mirror in /etc/apt/sources.list: http://us-east-1.ec2.archive.ubuntu.com/ubuntu/
git.checkout
1.57s$ git clone --depth=50 https://github.com/feathers-plus/feathers-hooks-common.git feathers-plus/feathers-hooks-common
Cloning into 'feathers-plus/feathers-hooks-common'...
remote: Enumerating objects: 795, done.
remote: Counting objects: 100% (795/795), done.
remote: Compressing objects: 100% (443/443), done.
remote: Total 795 (delta 415), reused 629 (delta 350), pack-reused 0
Receiving objects: 100% (795/795), 326.04 KiB | 14.82 MiB/s, done.
Resolving deltas: 100% (415/415), done.
$ cd feathers-plus/feathers-hooks-common
1.03s$ git fetch origin +refs/pull/469/merge:
remote: Enumerating objects: 50, done.
remote: Counting objects: 100% (42/42), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 10 (delta 5), reused 8 (delta 4), pack-reused 0
Unpacking objects: 100% (10/10), done.
From https://github.com/feathers-plus/feathers-hooks-common

branch            refs/pull/469/merge -> FETCH_HEAD
$ git checkout -qf FETCH_HEAD
nvm.install
4.31s$ nvm install node
Downloading and installing node v11.2.0...
Downloading https://nodejs.org/dist/v11.2.0/node-v11.2.0-linux-x64.tar.xz...
Computing checksum with sha256sum
Checksums matched!
Now using node v11.2.0 (npm v6.4.1)
$ node --version
v11.2.0
$ npm --version
6.4.1
$ nvm --version
0.33.11
4.97s$ npm ci
npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm ERR!
npm ERR!
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR!
npm ERR!  Retrying, 2 of 3.
npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm ERR!
npm ERR!
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR!
npm ERR!  Retrying, 3 of 3.
npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm ERR!
npm ERR!
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR!
npm ERR!
The command "npm ci " failed and exited with 1 during .
Your build has been stopped.

@eddystop I've gotta update the package lock.json. I'll do that in a few hours.

@eddyystop Should be fixed now. Took a few tries though lol. I don't know why vscode wasn't catching these things. Is it because there isn't a tslint.json?

@j2L4e please confirm this follows the standards the rest of typings follow.

@NickBolles thanks for adding the tests and fixing the linting errors. dtslint is pretty strict and can be a pain sometimes.

@jsl4e do we want to do anything about "Parent, args, content, ast will always be objects. I guess its possible some custom code may make context,ast undefined or perhaps null."? Or should I merge?

Sounds like any is the right thing here if it's possible to change the type with custom code. I guess args could at least be type any[].

Should I merge?

I missed this conversation before. I think we should make the two changes that j2l4e suggested. I can do those quick later tonight I think.
I haven't used fgraphql at all since doing this PR, so this hasn't really been in my mind. Sorry about the delay!

That'd be great, go ahead: )

@NickBolles sync/async version of what? I'll be back tomorrow morning

@j2L4e of the fgraphql hook
https://github.com/feathers-plus/feathers-hooks-common/blob/master/lib/services/fgraphql.js
vs
https://github.com/feathers-plus/feathers-hooks-common/blob/master/lib/services/fgraphql-async.js

We will remove fgraphql-async because batchloader can only work with promises. I had to rewrite the original async back into promises. 🤥

Gotcha, that makes sense!

I'm losing track of outstanding TS issues. Is this one resolved?
I'm asking because I have to write the next article on populate hooks but don't want to do that if there issues with it in TS.

Looks done to me


Stabilize slirp outside connectivity test

What this PR does / why we need it:
Use PingFromVMConsole to verify Slirp connectivity: The orignal code using curl was problematic due to its lack of retry - temporary connection drop would fail the test. With this patch, curl is replaced by ping with a retry. This is following the format of the same scenario in vmi_networking.go.
This PR also removes unused HTTP server from a Slirp test.
Special notes for your reviewer:
This should resolve flakes like https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-1.22-sig-network/1587200279651028992#1:build-log.txt%3A3067.
Release note:

NONE

/test pull-kubevirt-e2e-k8s-1.22-sig-network

/test pull-kubevirt-e2e-k8s-1.24-sig-network-nonroot

/test pull-kubevirt-e2e-k8s-1.24-sig-network-nonroot

/test pull-kubevirt-e2e-k8s-1.24-sig-network-nonroot

/retest

@phoracek , the failures seem to originate from this test.

@EdDev seems that the original line that started the HTTP server implicitly logged into the VM. Now without the HTTP server, it is necessary to add LoginToVM call, which is not a part of WaitForSuccessfulVMIStartIgnoreWarnings.

/retest
Not related to the test changed in this PR.

/approve


[Question] What are the current limitations of this platform?

Hey guys,
I'm trying to better understand the limitations of Viro, how one would go about making a first-person shooter with Viro and if this platform would be appropriate / scale for an experience as described below.
I'd like to build a VR-based fps game consisting of obj's and animated fbx's for character models all produced within Blender. The main character node would basically be an fbx model w/ several animations for reloading. walking, shooting, etc and I'm assuming that a ViroCamera would be fixed to that particular node in order to produce that FPS perspective. I see raycasting / collision detection is supported so I assume basic shooting mechanics would work.
The majority of the game would take place in a colosseum/arena where robots and drone progressively spawn in waves, approach and surround the user until they are close enough to attack at which point the user begins to lose health points.
The main objective of this game would be to destroy all enemy robots/drones using various weapons that you unlock, craft, or pick up throughout the game such as swords, pistols, rifles, etc.
Does this sound like something Viro could help me produce? Or this something best handled by a game engine like Unity?

Hi @tedjames, everything you mention is technically possible in our platform. That being said, Viro is an application framework, so FPS was not a use case we optimized for. If you are a React Native/Javascript developer, then it’s worth trying Viro as you will be able to build a lot faster. But if you are already familiar with Unity/Unreal, then you should consider those platforms as they are tailored for games like first person shooters.

Thanks for clearing that up @VikAdvani! I'm going to give Viro a try then since I've never touched Unity or Unreal. I plan on upping my Blender skills and making some smaller games with Viro before progressing to a first person shooter.

Hi @tedjames, just an fyi here is a good sample code that may be helpful for "shooting and applying a force from your controller".


Switch from sass gem

The sass gem is officially being deprecated and will stop being supported in 2019.  There are several options; for our purposes, sassc-rails is probably the best fit.

Here is the current post-install message from sass:
Ruby Sass is deprecated and will be unmaintained as of 26 March 2019.

If you use Sass as a command-line tool, we recommend using Dart Sass, the new
primary implementation: https://sass-lang.com/install

If you use Sass as a plug-in for a Ruby web framework, we recommend using the
sassc gem: https://github.com/sass/sassc-ruby#readme

For more details, please refer to the Sass blog:
http://sass.logdown.com/posts/7081811

#1675


Dependency problem in 2.0.12 (broken shade plugin update)

There is a critical issue with 2.0.12 Maven release - it does not declare any transitive dependencies. See:
https://mvnrepository.com/artifact/xyz.rogfam/littleproxy/2.0.12 (0 compile dependencies)
vs.
https://mvnrepository.com/artifact/xyz.rogfam/littleproxy/2.0.11 (10 compile dependencies)
This seems to be caused by shade plugin configuration - obviously not fully compatible with updated plugin version.

Oh, again! :(
We already had this problem: https://github.com/LittleProxy/LittleProxy/issues/115, and now it happened again.
Will fix it tomorrow in 2.0.13.

Instead of reverting, like the last time, force the plugin to package the original pom.xml (instead of the reduced one). My understanding is that the shaded, executable artifact is not in fact being deployed anywhere, so it should not create a problem.

fixed by PR https://github.com/LittleProxy/LittleProxy/pull/171


Add new company: [Tandy]

Company Name?
Radioshack/Tandy
What's the company main business today?
Leather goods (but for a while, electronics)
What did the company do in the early days?
Leather goods
What caused the company to pivot?
Tandy originally made leather goods for the hobby market. As electronics grew as a hobby in the 70s and 80s, Tandy acquired a small, failing electronics store in Boston called Radioshack. The Tandy TRS-80 was one of the first microcomputers and Radioshack was synonymous with hobby electronics until it went defunct. Tandy Leathergoods still exists today.
Source?
https://en.wikipedia.org/wiki/Tandy_Corporation

Added! Thanks a lot for contributing!


Column header hover

When hover over a column, have the header show it as well. Fixes #156

Not exactly what I had in mind. I was thinking the column header would change colour when the header is hovered. As simple as that.

Oh! I thought you mean Excel-like, where it shows row and column.
Well, any objection to keeping this the way it is? I like it, even if I misunderstood. Then we can add in header hover easily.

OK, added both. Check it out.

I only like the header hover. Also could it have an active state when clicked?

Oh great. I misunderstood, put all the work, and you only like the first part? Any reason not to keep it?

could it have an active state when clicked?

What do you mean?

Because it doesn't look good.
When column header is clicked (sorted), it could have an active class.
I don't mind making these changes, I only raised it as an issue to remind myself and let others know what I was thinking about doing.

Because it doesn't look good.
When column header is clicked (sorted), it could have an active class.

OK, can you show me an example?

see: https://github.com/adamjimenez/jstree-grid/tree/column-header-hover

That link you sent is just to a branch of your copy of the repo. Do you have a fiddle or similar example of it not working?

check again, it has an extra commit.

It looks like you removed the hoverInHandler and hoverOutHandler changes, which is what allowed the header to highlight when you hover a cell in the column, at https://github.com/adamjimenez/jstree-grid/commit/d45a0ca7e7274f79a81977fa41115c493e03b67e
And then what does this do? https://github.com/adamjimenez/jstree-grid/commit/e73b0f20a4843f4093653f975ad1f69f28b928fe


Change the repo description

The description for this repo needs to be changed
Currently:
Web AppBuilder widgets for Military Analyst +
Change to :
Web AppBuilder widgets for Military Tools for ArcGIS

@topowright done.


Avoid data copy in parquet reader.

Describe This Problem
After parquet is upgraded by #269, some api changes and in order to adapt them some performance issues are introduced:
https://github.com/CeresDB/ceresdb/blob/a8fb2c92edb979051fbfbd339d72f65f94628f2c/components/parquet_ext/src/serialized_reader.rs#L195-L202
Proposal
(TODO)
Additional Context
No response

I guess this has been fixed already.


save in file by base64, for copy visibility

Description
What is the purpose of the change?
The key can be saved in file by base64, for visibility.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

Brief of your solution
Before write to file, encode content use base64.
After read from file,decode content use base64.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.gaowei16 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Don't use "version" in "OpenSSL Version 1.1.0" etc

Seems a little conflicting with your suggested here: https://github.com/openssl/openssl/pull/3895#discussion_r127577670
I guess I need to fix that to follow this PR : )

you are right, but we had a bit of discussion and 'majority rules' :)

Thanks, merged.  We don't have a manpage style guide (yet).  I'm looking for one to use as a starting point.  For now, the style rules are "must pass find-doc-nits" :)


Consider empty buffered input in appBufferStatus to close the SSLIOSession.

Update the logic back to consider empty buffered input in appBufferStatus before closing the SSLIOSession.
This was the condition considered before this commit https://github.com/apache/httpcomponents-core/commit/211c21f86f27c8cc786a621fef2e1fdf3dc6b126#diff-b31898263b1708b34dde2568e52e870fa623a6d4be99ce247a7f6dc61f03ed7fR395

@sajinieKavindya Yes, I made a mistake. The correct condition should likely be
&& (this.terminated || (!this.inPlain.hasData() && (this.appBufferStatus == null || !this.appBufferStatus.hasBufferedInput())))) {

Please test and update your PR if you agree.

@sajinieKavindya Yes, I made a mistake. The correct condition should likely be
&& (this.terminated || (!this.inPlain.hasData() && (this.appBufferStatus == null || !this.appBufferStatus.hasBufferedInput())))) {

Please test and update your PR if you agree.

@ok2c Updated the commit.


Mussum Ipsum replaces lorem ipsum for brazilian provider

This is a known random text generator for brazilian developers based on:
http://mussumipsum.com/

Since it is about random "text like content" i don't really see a benefit of adding this in the core at this point compared to the Lorum provider there already is.
@fzaninotto what is your view?

The Lorem formatter is never translated. Check the realText formatter for localized random text.