2.4 Upgrade Failing on alter_user_last_name_max_length

Environment

Python version:  3.6.5
NetBox version: 2.3.4 --> 2.4

With last names length being mentioned, I've got the longest last name of 11 chars, but for some reason now my last name is showing up with a space, if the space is getting in the way.

Steps to Reproduce

Pull the latest release via Github
Execute ./upgrade.sh file

Expected Behavior
Successful Upgrade

Observed Behavior
# ./upgrade.sh
Running NetBox upgrade as root, press any key to continue or ^C to cancel
Cleaning up stale Python bytecode (find . -name "*.pyc" -delete)...
Removing old Python packages (pip3 uninstall -r old_requirements.txt -y)...
Cannot uninstall requirement django-rest-swagger, not installed
You are using pip version 9.0.3, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Updating required Python packages (pip3 install -r requirements.txt --upgrade)...
Collecting Django<2.1,>=1.11 (from -r requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/2b/85/337bfa37c4b82f59ee9b8deca55a8daa7ef16c8cdfa86d273625bc6ed887/Django-2.0.8-py3-none-any.whl (7.1MB)
    100% |████████████████████████████████| 7.1MB 139kB/s
Collecting django-cors-headers==2.4.0 (from -r requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/cc/7e/83ba784ad2b95317bbbed915f0888d7d1cd8dc3d2e4b8ddec8fbc4c3e800/django_cors_headers-2.4.0-py2.py3-none-any.whl
Requirement already up-to-date: django-debug-toolbar==1.9.1 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 3))
Requirement already up-to-date: django-filter==1.1.0 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 4))
Collecting django-mptt==0.9.1 (from -r requirements.txt (line 5))
  Downloading https://files.pythonhosted.org/packages/46/ec/415a72ff8c41be0e00900941fad48b3c696fd1da7f8e8ac1e6abc59d8981/django_mptt-0.9.1-py2.py3-none-any.whl (105kB)
    100% |████████████████████████████████| 112kB 7.0MB/s
Requirement already up-to-date: django-tables2==1.21.2 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 6))
Collecting django-taggit==0.22.2 (from -r requirements.txt (line 7))
  Downloading https://files.pythonhosted.org/packages/83/63/0d5fb906e2f88952d86ba4ec472cdeab4425e430bfe9e0fd631e5bbb1e7d/django_taggit-0.22.2-py2.py3-none-any.whl (45kB)
    100% |████████████████████████████████| 51kB 7.2MB/s
Collecting django-taggit-serializer==0.1.7 (from -r requirements.txt (line 8))
  Downloading https://files.pythonhosted.org/packages/68/c4/9737e1df18ca8af0f40f46a54af08a15d75eb7afd7805ba94c87fc042ae3/django-taggit-serializer-0.1.7.tar.gz
Requirement already up-to-date: django-timezone-field==2.1 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 9))
Collecting djangorestframework==3.8.1 (from -r requirements.txt (line 10))
  Downloading https://files.pythonhosted.org/packages/d9/ea/eb9855829e2c22b6c610c02302d2979f9c53b797e2064b3304eff3b57c0c/djangorestframework-3.8.1-py2.py3-none-any.whl (923kB)
    100% |████████████████████████████████| 931kB 1.1MB/s
Collecting drf-yasg[validation]==1.9.2 (from -r requirements.txt (line 11))
  Downloading https://files.pythonhosted.org/packages/a3/67/22c2b5f7e5538b394a2527ffe47c1a2861600a74e462a27a5a77423b683a/drf_yasg-1.9.2-py2.py3-none-any.whl (841kB)
    100% |████████████████████████████████| 849kB 1.2MB/s
Collecting graphviz==0.8.4 (from -r requirements.txt (line 12))
  Downloading https://files.pythonhosted.org/packages/53/39/4ab213673844e0c004bed8a0781a0721a3f6bb23eb8854ee75c236428892/graphviz-0.8.4-py2.py3-none-any.whl
Requirement already up-to-date: Markdown==2.6.11 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 13))
Collecting natsort==5.3.3 (from -r requirements.txt (line 14))
  Downloading https://files.pythonhosted.org/packages/d6/8d/3bca1e1415299dae9d469b04a4ced7267f62249a9902e823fd7d6b085683/natsort-5.3.3-py2.py3-none-any.whl
Collecting ncclient==0.6.0 (from -r requirements.txt (line 15))
  Downloading https://files.pythonhosted.org/packages/d7/5a/def9ce89fd9bbc57fd9b0a7202b371bfad16c0e738d3a3a672ea436d022e/ncclient-0.6.0.tar.gz (69kB)
    100% |████████████████████████████████| 71kB 6.9MB/s
Collecting netaddr==0.7.19 (from -r requirements.txt (line 16))
  Downloading https://files.pythonhosted.org/packages/ba/97/ce14451a9fd7bdb5a397abf99b24a1a6bb7a1a440b019bebd2e9a0dbec74/netaddr-0.7.19-py2.py3-none-any.whl (1.6MB)
    100% |████████████████████████████████| 1.6MB 632kB/s
Requirement already up-to-date: paramiko==2.4.1 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 17))
Collecting Pillow==5.2.0 (from -r requirements.txt (line 18))
  Downloading https://files.pythonhosted.org/packages/d1/24/f53ff6b61b3d728b90934bddb4f03f8ab584a7f49299bf3bde56e2952612/Pillow-5.2.0-cp36-cp36m-manylinux1_x86_64.whl (2.0MB)
    100% |████████████████████████████████| 2.0MB 484kB/s
Requirement already up-to-date: psycopg2-binary==2.7.5 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 19))
Requirement already up-to-date: py-gfm==0.1.3 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 20))
Collecting pycryptodome==3.6.4 (from -r requirements.txt (line 21))
  Downloading https://files.pythonhosted.org/packages/f3/37/ee6b25ef78a5c4399ef2a23d60404be897e13568d9c8999c282b61e3d14e/pycryptodome-3.6.4-cp36-cp36m-manylinux1_x86_64.whl (7.4MB)
    100% |████████████████████████████████| 7.4MB 133kB/s
Requirement already up-to-date: xmltodict==0.11.0 in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 22))
Collecting pytz (from Django<2.1,>=1.11->-r requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/30/4e/27c34b62430286c6d59177a0842ed90dc789ce5d1ed740887653b898779a/pytz-2018.5-py2.py3-none-any.whl (510kB)
    100% |████████████████████████████████| 512kB 2.1MB/s
Requirement already up-to-date: sqlparse>=0.2.0 in /usr/local/lib/python3.6/site-packages (from django-debug-toolbar==1.9.1->-r requirements.txt (line 3))
Requirement already up-to-date: django-js-asset in /usr/local/lib/python3.6/site-packages (from django-mptt==0.9.1->-r requirements.txt (line 5))
Requirement already up-to-date: six in /usr/local/lib/python3.6/site-packages (from django-taggit-serializer==0.1.7->-r requirements.txt (line 8))
Requirement already up-to-date: future>=0.16.0 in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: inflection>=0.3.1 in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Collecting ruamel.yaml>=0.15.34 (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
  Downloading https://files.pythonhosted.org/packages/6c/15/32111dee7455acf71a7f99fcc3ce2de689d56cbce03c6b105455351f1894/ruamel.yaml-0.15.50-cp36-cp36m-manylinux1_x86_64.whl (639kB)
    100% |████████████████████████████████| 645kB 1.5MB/s
Requirement already up-to-date: coreapi>=2.3.3 in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: uritemplate>=3.0.0 in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: coreschema>=0.0.4 in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: openapi-codec>=1.3.2 in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: swagger-spec-validator>=2.1.0; extra == "validation" in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: flex>=6.11.1; extra == "validation" in /usr/local/lib/python3.6/site-packages (from drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Collecting setuptools>0.6 (from ncclient==0.6.0->-r requirements.txt (line 15))
  Downloading https://files.pythonhosted.org/packages/ff/f4/385715ccc461885f3cedf57a41ae3c12b5fec3f35cce4c8706b1a112a133/setuptools-40.0.0-py2.py3-none-any.whl (567kB)
    100% |████████████████████████████████| 573kB 1.6MB/s
Collecting lxml>=3.3.0 (from ncclient==0.6.0->-r requirements.txt (line 15))
  Downloading https://files.pythonhosted.org/packages/eb/59/1db3c9c27049e4f832691c6d642df1f5b64763f73942172c44fee22de397/lxml-4.2.4-cp36-cp36m-manylinux1_x86_64.whl (5.8MB)
    100% |████████████████████████████████| 5.8MB 151kB/s
Requirement already up-to-date: bcrypt>=3.1.3 in /usr/local/lib/python3.6/site-packages (from paramiko==2.4.1->-r requirements.txt (line 17))
Requirement already up-to-date: pynacl>=1.0.1 in /usr/local/lib/python3.6/site-packages (from paramiko==2.4.1->-r requirements.txt (line 17))
Collecting cryptography>=1.5 (from paramiko==2.4.1->-r requirements.txt (line 17))
  Downloading https://files.pythonhosted.org/packages/c2/fa/fa9a8933c285895935d1392922fe721e9cb1b2c1881d14f149213a227ee3/cryptography-2.3-cp34-abi3-manylinux1_x86_64.whl (2.1MB)
    100% |████████████████████████████████| 2.1MB 477kB/s
Collecting pyasn1>=0.1.7 (from paramiko==2.4.1->-r requirements.txt (line 17))
  Downloading https://files.pythonhosted.org/packages/d1/a1/7790cc85db38daa874f6a2e6308131b9953feb1367f2ae2d1123bb93a9f5/pyasn1-0.4.4-py2.py3-none-any.whl (72kB)
    100% |████████████████████████████████| 81kB 6.9MB/s
Requirement already up-to-date: itypes in /usr/local/lib/python3.6/site-packages (from coreapi>=2.3.3->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: requests in /usr/local/lib/python3.6/site-packages (from coreapi>=2.3.3->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: jinja2 in /usr/local/lib/python3.6/site-packages (from coreschema>=0.0.4->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Collecting pyyaml (from swagger-spec-validator>=2.1.0; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
  Downloading https://files.pythonhosted.org/packages/9e/a3/1d13970c3f36777c583f136c136f804d70f500168edc1edea6daa7200769/PyYAML-3.13.tar.gz (270kB)
    100% |████████████████████████████████| 276kB 3.4MB/s
Requirement already up-to-date: jsonschema in /usr/local/lib/python3.6/site-packages (from swagger-spec-validator>=2.1.0; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Collecting rfc3987<2,>=1.3.4 (from flex>=6.11.1; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
  Downloading https://files.pythonhosted.org/packages/65/d4/f7407c3d15d5ac779c3dd34fbbc6ea2090f77bd7dd12f207ccf881551208/rfc3987-1.3.8-py2.py3-none-any.whl
Requirement already up-to-date: strict-rfc3339<1,>=0.7 in /usr/local/lib/python3.6/site-packages (from flex>=6.11.1; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: validate-email<2,>=1.2 in /usr/local/lib/python3.6/site-packages (from flex>=6.11.1; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: click<7,>=3.3 in /usr/local/lib/python3.6/site-packages (from flex>=6.11.1; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: jsonpointer<2,>=1.7 in /usr/local/lib/python3.6/site-packages (from flex>=6.11.1; extra == "validation"->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: cffi>=1.1 in /usr/local/lib/python3.6/site-packages (from bcrypt>=3.1.3->paramiko==2.4.1->-r requirements.txt (line 17))
Requirement already up-to-date: asn1crypto>=0.21.0 in /usr/local/lib/python3.6/site-packages (from cryptography>=1.5->paramiko==2.4.1->-r requirements.txt (line 17))
Requirement already up-to-date: idna>=2.1 in /usr/local/lib/python3.6/site-packages (from cryptography>=1.5->paramiko==2.4.1->-r requirements.txt (line 17))
Requirement already up-to-date: certifi>=2017.4.17 in /usr/local/lib/python3.6/site-packages (from requests->coreapi>=2.3.3->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.6/site-packages (from requests->coreapi>=2.3.3->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: urllib3<1.24,>=1.21.1 in /usr/local/lib/python3.6/site-packages (from requests->coreapi>=2.3.3->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: MarkupSafe>=0.23 in /usr/local/lib/python3.6/site-packages (from jinja2->coreschema>=0.0.4->drf-yasg[validation]==1.9.2->-r requirements.txt (line 11))
Requirement already up-to-date: pycparser in /usr/local/lib/python3.6/site-packages (from cffi>=1.1->bcrypt>=3.1.3->paramiko==2.4.1->-r requirements.txt (line 17))
Installing collected packages: pytz, Django, django-cors-headers, django-mptt, django-taggit, django-taggit-serializer, djangorestframework, ruamel.yaml, drf-yasg, graphviz, natsort, setuptools, lxml, ncclient, netaddr, Pillow, pycryptodome, cryptography, pyasn1, pyyaml, rfc3987
  Found existing installation: pytz 2018.4
    Uninstalling pytz-2018.4:
      Successfully uninstalled pytz-2018.4
  Found existing installation: Django 1.11.13
    Uninstalling Django-1.11.13:
      Successfully uninstalled Django-1.11.13
  Found existing installation: django-cors-headers 2.2.0
    Uninstalling django-cors-headers-2.2.0:
      Successfully uninstalled django-cors-headers-2.2.0
  Found existing installation: django-mptt 0.9.0
    Uninstalling django-mptt-0.9.0:
      Successfully uninstalled django-mptt-0.9.0
  Running setup.py install for django-taggit-serializer ... done
  Found existing installation: djangorestframework 3.8.2
    Uninstalling djangorestframework-3.8.2:
      Successfully uninstalled djangorestframework-3.8.2
  Found existing installation: ruamel.yaml 0.15.40
    Uninstalling ruamel.yaml-0.15.40:
      Successfully uninstalled ruamel.yaml-0.15.40
  Found existing installation: drf-yasg 1.9.0
    Uninstalling drf-yasg-1.9.0:
      Successfully uninstalled drf-yasg-1.9.0
  Found existing installation: graphviz 0.8.3
    Uninstalling graphviz-0.8.3:
      Successfully uninstalled graphviz-0.8.3
  Found existing installation: natsort 5.3.2
    Uninstalling natsort-5.3.2:
      Successfully uninstalled natsort-5.3.2
  Found existing installation: setuptools 39.2.0
    Uninstalling setuptools-39.2.0:
      Successfully uninstalled setuptools-39.2.0
  Found existing installation: lxml 4.2.2
    Uninstalling lxml-4.2.2:
      Successfully uninstalled lxml-4.2.2
  Found existing installation: ncclient 0.5.3
    Uninstalling ncclient-0.5.3:
      Successfully uninstalled ncclient-0.5.3
  Running setup.py install for ncclient ... done
  Found existing installation: netaddr 0.7.18
    Uninstalling netaddr-0.7.18:
      Successfully uninstalled netaddr-0.7.18
  Found existing installation: Pillow 5.1.0
    Uninstalling Pillow-5.1.0:
      Successfully uninstalled Pillow-5.1.0
  Found existing installation: pycryptodome 3.6.3
    Uninstalling pycryptodome-3.6.3:
      Successfully uninstalled pycryptodome-3.6.3
  Found existing installation: cryptography 2.2.2
    Uninstalling cryptography-2.2.2:
      Successfully uninstalled cryptography-2.2.2
  Found existing installation: pyasn1 0.4.3
    Uninstalling pyasn1-0.4.3:
      Successfully uninstalled pyasn1-0.4.3
  Found existing installation: PyYAML 3.12
    Uninstalling PyYAML-3.12:
      Successfully uninstalled PyYAML-3.12
  Running setup.py install for pyyaml ... done
  Found existing installation: rfc3987 1.3.7
    Uninstalling rfc3987-1.3.7:
      Successfully uninstalled rfc3987-1.3.7
Successfully installed Django-2.0.8 Pillow-5.2.0 cryptography-2.3 django-cors-headers-2.4.0 django-mptt-0.9.1 django-taggit-0.22.2 django-taggit-serializer-0.1.7 djangorestframework-3.8.1 drf-yasg-1.9.2 graphviz-0.8.4 lxml-4.2.4 natsort-5.3.3 ncclient-0.6.0 netaddr-0.7.19 pyasn1-0.4.4 pycryptodome-3.6.4 pytz-2018.5 pyyaml-3.13 rfc3987-1.3.8 ruamel.yaml-0.15.50 setuptools-40.0.0
You are using pip version 9.0.3, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Applying database migrations (python3 netbox/manage.py migrate)...
Operations to perform:
  Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, taggit, tenancy, users, virtualization
Running migrations:
  Applying auth.0009_alter_user_last_name_max_length...Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
psycopg2.IntegrityError: duplicate key value violates unique constraint "django_migrations_pkey"
DETAIL:  Key (id)=(111) already exists.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.6/site-packages/django/core/management/__init__.py", line 371, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.6/site-packages/django/core/management/__init__.py", line 365, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 335, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 200, in handle
    fake_initial=fake_initial,
  File "/usr/local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/usr/local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/usr/local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 250, in apply_migration
    self.recorder.record_applied(migration.app_label, migration.name)
  File "/usr/local/lib/python3.6/site-packages/django/db/migrations/recorder.py", line 71, in record_applied
    self.migration_qs.create(app=app, name=name)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 417, in create
    obj.save(force_insert=True, using=self.db)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 729, in save
    force_update=force_update, update_fields=update_fields)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 759, in save_base
    updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 842, in _save_table
    result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 880, in _do_insert
    using=using, raw=raw)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 1125, in _insert
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/local/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1285, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 68, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: duplicate key value violates unique constraint "django_migrations_pkey"
DETAIL:  Key (id)=(111) already exists.

Collecting static files (python3 netbox/manage.py collectstatic --no-input)...
 As discussed on NetworkToCode, this seems related to some corruption in your particular database.


[pixel4] Cannot load Android system. Your data may be corrupt

issue
Android phone only showed and not operatable normally. Screen reads as following, same as https://support.google.com/pixelphone/thread/17930356/is-there-a-way-to-bypass-the-cannot-load-android-system-error-without-losing-personal-data?hl=en:

Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device

What happened before seeing the issue
In the morning after it's fully charged, I unplugged, did some normal daily browsing, then put it in my pocket. A few minutes after that I saw this. Note I did NOT trigger a reboot/shutdown.
Workaround worked
Press "Try again" rebooted Android and it seems to have rebooted normally.
Additional info

Replaced battery and frontpanel 5 days before #557. I have yet to reported how it's been though, there are a new behavior, which seems minor for now, that I had never seen.

Not seen again so far.


Transforming types of loop condition in 'for' crashes ironpython

Using int(), str(), to transform the type of loop condition causes crashes in ironpython. See the following test.py.
test.py
for int(i) in range(10):
	print(i)

Error message:
>>'ironpython/ironpython3/bin/Debug/net6.0/ipy' test.py
.....
ting/Shell/CommandLine.cs:line 100
   at Microsoft.Scripting.Hosting.Shell.ConsoleHost.RunCommandLine() in /home/xxm/Desktop/IFuzzer/experiment_on_different_interpreter/ironpython/ironpython3/Src/DLR/Src/Microsoft.Dynamic/Hosting/Shell/ConsoleHost.cs:line 386
   at Microsoft.Scripting.Hosting.Shell.ConsoleHost.ExecuteInternal() in /home/xxm/Desktop/IFuzzer/experiment_on_different_interpreter/ironpython/ironpython3/Src/DLR/Src/Microsoft.Dynamic/Hosting/Shell/ConsoleHost.cs:line 321
   at PythonConsoleHost.ExecuteInternal() in /home/xxm/Desktop/IFuzzer/experiment_on_different_interpreter/ironpython/ironpython3/Src/IronPythonConsole/Console.cs:line 165
   at Microsoft.Scripting.Hosting.Shell.ConsoleHost.Execute() in /home/xxm/Desktop/IFuzzer/experiment_on_different_interpreter/ironpython/ironpython3/Src/DLR/Src/Microsoft.Dynamic/Hosting/Shell/ConsoleHost.cs:line 299
   at Microsoft.Scripting.Hosting.Shell.ConsoleHost.Run(String[] args) in /home/xxm/Desktop/IFuzzer/experiment_on_different_interpreter/ironpython/ironpython3/Src/DLR/Src/Microsoft.Dynamic/Hosting/Shell/ConsoleHost.cs:line 197
   at PythonConsoleHost.Main(String[] args) in /home/xxm/Desktop/IFuzzer/experiment_on_different_interpreter/ironpython/ironpython3/Src/IronPythonConsole/Console.cs:line 199
Aborted (core dumped)

System info:
ironpython3-debug(main branch):IronPython 3.4.0b1 DEBUG (<IP_ADDRESS>0)[.NETCoreApp,Version=v6.0 on .NET 6.0.11 (64-bit)] on linux
operating system: Ubuntu 18.04.6 LTS

Thanks! Crashes in debug mode due to an assertion error. In release mode we get a SystemError:

SystemError: Operation is not valid due to the current state of the object.

instead of the expected SyntaxError:

SyntaxError: can't assign to function call

Not just transforming types, the following raises an assertion error as well:
for 1 in range(10):
    pass


feat: Add Upcoming Events for July

Is your feature request related to a problem? Please describe.
We have 4+ upcoming events on Meetup: https://www.meetup.com/women-coding-community/events/. It'd be good to highlight the upcoming ones for July on the website.
Describe the solution you'd like
July events added to the website, events details can be found here.
Note: An event for July 17 will still be added
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hey - I'd like to take a look at this!

@swetha-charles thank you! I have assigned the issue to you


do.sh: Improve host OS distro detection.

Don't use lsb_release anymore and correctly detect Fedora/RHEL-like distro versions.

@igsilya, wdyt?


fix: microdnf update

Microdnf was missing -y and was not updating correctly.
Closes #714

is there a test we can add for microdnf?

@MiahaCybersec we can add registry.access.redhat.com/ubi9/ubi-minimal:9.4-949 so from the issue to the integration tests

It looks like the failing test is due to a custom network configuration integration test

@MiahaCybersec sometimes the connection is flakey. I re-ran and the test passed.


[FLINK-36046] Change the existing org.apache.flink.streaming.api.functions.sink#DiscardingSink and org.apache.flink.streaming.api.functions.sink#PrintSinkFunction to use the new interfaces

What is the purpose of the change
Change the existing org.apache.flink.streaming.api.functions.sink#DiscardingSink and org.apache.flink.streaming.api.functions.sink#PrintSinkFunction to use the new interfaces
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no )
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@flinkbot run azure


[Lab Notes] Not all captions are marked as emphasised

Example:
https://franklin.moleculardevices.com/lab-notes/clone-screening/accelerated-production-of-monoclonal-antibodies-for-treatment-of-sars-cov-2-covid-19
Text or lists marked with either:

caption or text-caption classes

should be emphasised.

@mhaack I think I contributed the code for this in the importer, but we haven't reimported the blogs since. We might need to do it, because there is a lot of them.
We anyway need to do it for https://github.com/hlxsites/moleculardevices/issues/489.

@andreituicu this should be fixed I think.

It looks fixed, closing.


LUTECE-1933 : Experimental jade templating support

Requires the library-jade library.
This library is available at https://github.com/rzara/lutece-tech-library-jade
*.jade template files are routed to the JadeTemplateService.
Jade templates can be embedded in freemarker templates by using the
@jade directive :
<@jade>
	p.jade
	span variable's value is ${r"#{variable}"}
</@jade>

The body of the directive is first evaluated by freemarker before being
processed by jade.

won't be merged as is


Prevent starting a VM in destroyed state (or any state but Stopped)

Description
A destroyed VM when attempted to be started (using the bulk action support in the UI), results in a successful operation, however, the VM doesn't actually start. This PR fixes the false positive result shown in the above mentioned condition

VM continues to remain in destroyed state - but a success response is returned

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[X] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Tried starting an instance in destroyed state:
2021-06-29 12:57:51,609 WARN  [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-5:ctx-da4601fa job-52/job-54 ctx-cc08e96e) (logid:08e57fcb) VM VM instance {"id": "3", "name": "i-2-3-VM", "uuid": "4213c3d9-72a8-4201-96c4-003e2c2f845b", "type"="User"} is not in a state to be started: Destroyed
2021-06-29 12:57:51,610 INFO  [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-5:ctx-da4601fa job-52/job-54 ctx-cc08e96e) (logid:08e57fcb) Caught CloudRuntimeException, returning job failed com.cloud.utils.exception.CloudRuntimeException: Cannot start VM: VM instance {"id": "3", "name": "i-2-3-VM", "uuid": "4213c3d9-72a8-4201-96c4-003e2c2f845b", "type"="User"} in Destroyed state
2021-06-29 12:57:51,613 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-5:ctx-da4601fa job-52/job-54 ctx-cc08e96e) (logid:08e57fcb) Done executing VM work job: com.cloud.vm.VmWorkStart{"dcId":0,"rawParams":{"VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":3,"handlerName":"VirtualMachineManagerImpl"}

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 422

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 424

@blueorangutan test

@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian.  I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian.  I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian. SL-JID 475

@blueorangutan test

@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-1205)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33120 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5165-t1205-kvm-centos7.zip
Smoke tests completed. 88 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Merging this based on LGTMs, manual and smoke tests.


Train of Thought Review

Thanks for getting this going @jesstelford!
Brace yourself, I'm about to get nit-picky. Nothing personal of course, and I'm willing to admit I may be off the mark or flat out wrong! Don't be discouraged because this is a great workshop already, even if you disregard all of my comments I'm very proud to be able to present this to attendees at CampJS V.
From here on out I'm just logging my thoughts as I think them:

esnext-generation is a long one to type, maybe could include a shorter alias to binary.
node/iojs prerequisite could/should be enforced

1. Traditional Looping

Not sure the purpose of this exercise, I guess it's to ensure people understand basic iteration before diving into the more advanced iteration. Perhaps is a bit too basic for all but the most green JS developers.

"Looping" vs "Iterating" vs "Enumerating" vs "Sequences". Is a .forEach really a "loop"? IMO loops are specifically while/for/do..while language constructs, while .forEach is not a loop, but all of these enable iteration/enumeration, which I haven't found a useful distinction for yet and are synonyms. This is just how I categorise these features in my head and is by no means canonical definition.

Over time the language has expanded to contain further looping constructs to cover Objects and Arrays:

vs

JavaScript has evolved to include more convenient features for iterating over its built-in collection datatypes:

The ## Object & ## Array headings could be more explicit, something like:
 ## Looping over Object values using for...in
## Looping over Array values using forEach

The Array section could be more meaty. Maybe you could explicitly point out that "you shouldn't use for...in to enumerate arrays" as this is a common stumbling block rather than just

"requiring a special function Array.prototype.forEach(function(){})"
If someone needs to be taught about forEach vs for there's a good chance they won't understand the Array.prototype.* notation.

"Complete the following boilerplate"
Maybe be more explicit: "copy this boilerplate to a new file and complete with your solution:"

From a functional programming perspective, an example exercise of "find a single value from a set of values" isn't the best usage for .forEach – since this operation would be better described by a reduce… IMO. I usually reserve .forEach for things with external side effects for each item, and for for cases where I don't know the number of iterations up-front (e.g. constructing a new Array) or for performance.

Your solution won't handle negative numbers because of var largest = 0;. Use var largest = -Infinity; instead.

My Solution:
module.exports = function max(arr) {
  return arr.reduce(function(max, cur) { return Math.max(max, cur) })
}

2. Introduction To Iterators

"es6 (aka ESNext)" AFAIK it's not called either of these things any more. It's ES2015. Also consider always capitalizing.

What do you mean by "finally"

Consider a line break after ""Iterators are nothing more than objects with a certain interface."[1]

This syntax is likely unfamiliar to many next() -> {value: <mixed>, done: <boolean>}, perhaps include an "in english" translation: "That interface consists of a single method: "next", which takes no arguments (not true???) and returns an object containing a value property of any type, and done flag:"

"While Iterators may appear overly verbose" might be best to not assume what the reader is thinking as it can shape their attitude towards using the interface.

"Create a function, count(), which returns an Iterator that returns the numbers 1, 2, 3, ... etc, up to 10."  Starting at zero? Maybe s/numbers/positive integers.

Maybe get people to write out the full iterator interface, just give them an object hash, since it's trivial and maybe drives home the point that "Iterators" are just POJOs with a particular flavour of next.

Note that real-world iterators often throw away the value when done is true, so this might be setting people up for surprises later, though perhaps you're going to cover this in a future exercise.

I ignored the bonus points, don't want to be known as "teacher's pet"

My Solution
module.exports = function count() {
  var i = 0
  return {
    next: function() {
      i++
      return {
        value: i,
        done: !(i <= 10)
      }
    }
  }
}

3. Built In Iterators

I believe "Built In" should be hyphenated when used as an adjective.
"Es6" at the start of a sentence looks weird against "es6" in the middle of a sentence. Again, I suggest capitalisation.
"have an iterator" and "provide built in iterators" isn't really right, more correct would be "implements Iterable interface".
I suggest flipping the order that you explain things i.e. explain what we've been creating are "iterators" then explain what the "iterable interface" is and that this makes these collection instances "iterables", thus usable with for...of
Might be worth introducing well-known Symbols
"Arrays, Objects, and the new es6 Map & Set collections all provide built in iterators" Objects don't: Object.prototype[Symbol.iterator] === undefined but TypedArray does (and so does Buffer in iojs).
"not to be confused with looping over objects" -> "not to be confused with looping over objects values with for...in"
for(... in ...){}: I suggest standardising on MDN syntax of for...in
"Rewrite your function, max(), from Traditional Looping" Oops I wrote over it.
I suggest the exercise does something like pass the user both a Set and an Array objects and have them use the for...of interface to iterate over them. i.e. demonstrate "universality" of the interface, so long as thing is iterable you can treat them the same.
perhaps change collection in boilerplate to iterable to be explicit
Perhaps detect global pollution as people often forget they need to use var/let in for...in/for...of

My Solution
module.exports = function max(collection) {
  var currentMax = -Infinity
  for (var num of collection) {
    currentMax = Math.max(currentMax, num)
  }
  return currentMax
}

4. Advanced Iterables

"Iteratabls specificatoin:"
"ie;" i.e.
"Both the function which creates the Iterable (max() in Introduction To Iterators)" Introduction to Iterators was count not max and it created Iterator instances, but it wasn't Iterable itself: "In order to be iterable, an object must implement the @@iterator method" source
Perhaps also try to encourage understanding that the Iterator interface can and should be used to represent any type of sequence, even infinite sequences. Gives us a unified interface for to defining both abstract sequences and abstract operations which work with sequences.
Your verification insists that done:false exists, but the done key is optional and considered false if non-existent.
Not sure this exercise is any more advanced than the "Introduction To Iterators" exercise since we're just passing in regular function arguments to a regular function. You mention passing values to next, but we don't do that. Suggest maybe force people to set the start & end values in "Introduction To Iterators", then maybe have this one only require "start". These may be way too easy though. Consumption of an infinite iterator might be more interesting, perhaps you could do something like have them implement "pluck" or "take" i.e. pass them an infinite iterator and a number "total", then have them produce a new iterator that consumes the first iterator until "total" number of items have been iterated or the iterator is exhausted. That's not at all hard but gets them thinking about infinite sequences and how to write utilities that produce and consume iterators rather than arrays.
var num, done = false; IMO manually hoisting variables is an unnecessary anachronism, I avoid this as it runs high risk of creating unused variables.  IMO.

My Solution
module.exports = function generate(isEven) {
  var start = isEven ? 0 : -1
  return {
    next: function() {
      return {
        value: start += 2,
        done: false // should not be required
      }
    }
  }
}

Sorry, I don't have time now to do the last two exercises right now, I'll try to get to them this week.
Overall
I may have lots of comments but I do this is a great-looking workshop! I can see where you're going with these exercises and I like it. It's nice and gentle. You explain the concepts well, in a good sequence + link to all the appropriate information. Great job!

Thanks so much for your awesome feedback @timoxley! I'm going to split my responses up into two sections: First where I have outstanding questions, then second where I go through and fix a lot of the bits and pieces you pointed out.
Outstanding Questions

node/iojs prerequisite could/should be enforced

I've added an engineStrict directive to package.json, but it looks like it'll be deprecated in the near future. 83b5aa4
I was thinking: Is it possible to maybe use babel-node to transpile the code before execution when we detect node < 0.11.4?
3. Built in iterators

I suggest flipping the order that you explain [iterators & for...of]

Since I merged the "traditional looping" lesson into this one, I think it flows better as "forEach -> for...in -> for...of -> example". What do you think?

I suggest the exercise does something like [...] demonstrate "universality" of the interface. [...] perhaps change collection in boilerplate to iterable to be explicit

Good point. I've extended it a bit further to be:
Write a function `filterForNumbers(iterable)` which extracts only the numeric
values from `iterable`, returning those values as an Array. `iterable` could be
any built-in Iterable, or a custom Iterable exposing an Iterator via the key
`Symbol.iterator`.

Copy this boilerplate to a new file and complete with your solution, then
execute `$ADVENTURE_COMMAND verify <your-file.js>` to verify it.

module.exports = function filterForNumbers(iterable) {
  // loop over iterable, adding numeric valus to a new array
  // then return the new array of numbers
}

I think this drives home the point that any Iterable can be iterated via for...of. Let me know if you think it can be enhanced further.

Perhaps detect global pollution as people often forget they need to use var/let in for...in/for...of

Hmm, I just checked using Object.keys on global, and it appears there are other globals which get added (_ being one):
$ node
> Object.keys(global);
[ 'global',
  'process',
  'GLOBAL',
  'root',
  'Buffer',
  'setTimeout',
  'setInterval',
  'clearTimeout',
  'clearInterval',
  'setImmediate',
  'clearImmediate',
  'console',
  'module',
  'require' ]
> for(foo in [1, 2, 3]){ console.log(foo); }
0
1
2
undefined
> Object.keys(global);
[ 'global',
  'process',
  'GLOBAL',
  'root',
  'Buffer',
  'setTimeout',
  'setInterval',
  'clearTimeout',
  'clearInterval',
  'setImmediate',
  'clearImmediate',
  'console',
  'module',
  'require',
  '_',
  'foo' ]

Do you know of any other ways to detect global leakage? Or, maybe I need to warm the globals by using for...of once before testing? That seems like it might be brittle, though :(
4. Advanced Iterables

Not sure this exercise is any more advanced than the "Introduction To Iterators" exercise

Yep, agreed. My main goal was to act as the bridge to generators in the next lesson. Essentially introducing the idea that we can generate() Iterators that do particular things.
Later on, there is an entire lesson dedicated to passing values to .next() via yield in generators. I also point this out in the Extra Credit section of the Advanced Iterators lesson.
... Actually, I've gone ahead and enforced accepting a value to .next(), and made the Extra Credit section about plucking from an infinite Iterable: c7c1eec. Thoughts?
Bits & Pieces Fixes

esnext-generation is a long one to type, maybe could include a shorter alias to binary.

Good call! I added esng as an alias. It doesn't seem to be a command in use on Linux or OSX. 26d9d57

"Looping" vs "Iterating" vs "Enumerating" vs "Sequences"...

Great point; I've kept consistency with "Iterating". 83b5aa4..91052a9

"es6 (aka ESNext)" AFAIK it's not called either of these things any more. It's ES2015.

I went with "ES6" as the standardization - it's much more well known than ES2015: ba91a17

"Complete the following boilerplate" Maybe be more explicit: "copy this boilerplate to a new file and complete with your solution:"

Much nicer, thanks! 9d29ec6
1. Traditional Looping

Not sure the purpose of [the Traditional Looping] exercise. [...] The Array section could be more meaty. [...] If someone needs to be taught about forEach vs for [...]

Overall, I agree: this lesson is too simplistic, and may drive away more users than it attracts to the workshop. I've nuked it, and distributed the useful bits between other lessons: e3b82cd
2. Introduction To Iterators

What do you mean by "finally" [...] Consider a line break after [...] syntax is likely unfamiliar to many [...] best to not assume what the reader is thinking [...] Note that real-world iterators often throw away the value when done is true.

Thanks for pointing these out. Fixed in 14eac10

[...] just give them an object hash, since it's trivial and maybe drives home the point that "Iterators" are just POJOs with a particular flavour of next.

Agreed: simplification is always the best option: 81ec4e0

I ignored the bonus points, don't want to be known as "teacher's pet"

Haha, your call :)
3. Built In Iterators

I believe "Built In" should be hyphenated when used as an adjective.

Awesome, never knew about compound adjectives before now. Thanks for pointing it out. 3a23eda

"have an iterator" and "provide built in iterators" isn't really right, more correct would be "implements Iterable interface".

Yep, consistency is key: c786b18

Might be worth introducing well-known Symbols

Added in 182c504

Objects don't [provide iterators], but TypedArray does.

Thanks! 7833c2a

"not to be confused with looping over objects" -> "not to be confused with looping over objects values with for...in"
for(... in ...){}: I suggest standardising on MDN syntax of for...in

Yep, I caught these in a couple earlier fixes, thanks for pointing them out.
4. Advanced Iterables

"Iteratabls specificatoin:"
"ie;" i.e.

Spelling fixes in 82b9a4e

[...] it wasn't Iterable itself
Perhaps also try to encourage understanding that the Iterator interface can and should be used to represent any type of sequence

Great clarification, I've added it in f162a93

the done key is optional and considered false if non-existent.

Thanks for pointing that out. 0b7147a

var num, done = false; IMO manually hoisting variables is an unnecessary anachronism

Fair call. I've fallen into this pattern due to working with devs who are less familiar with how hoisting works. This is the only way to ensure subtle hoisting bugs are avoided. I'm still on the fence about its usefulness, but I figure it can't hurt, and unused variables can optimised away during compile time.

I may have lots of comments but I do this is a great-looking workshop! I can see where you're going with these exercises and I like it. It's nice and gentle. You explain the concepts well, in a good sequence + link to all the appropriate information. Great job!

Thanks mate - really really appreciate your feedback and help! :)


Provide default config for Mac OS

At the moment default config is only setup for Windows and Linux. It will nice to also have it setup for Mac.
You can check these merged PRs to look at the implementations for guidance.
https://github.com/starfixdev/starfix/pull/102 and https://github.com/starfixdev/starfix/pull/99

@fahad-israr can you make this a good first issue?

@fahad-israr can you make this a good first issue?

sure

@fahad-israr I'll submit a pr by tomorrow.


clone/checkout command (update_code) has not finished but next tasks start

I'm using deployer from master branch.
My repo has around 4000 files.
This is my deploy task:
task('deploy', [
    'deploy:prepare',
    'deploy:release',
    'deploy:update_code',
    'deploy:shared',
    'deploy:writable',
    'deploy:symlink',
    'cleanup',
    'backend:restart',
])->desc('Deploy your project');

This is part of log when I deploy with -vvv:
➤ Executing task deploy:update_code
...
⤶ done on [dev]
✔ Ok
➤ Executing task deploy:shared
Run: cd deploy_path && if [ -d $(echo deploy_path/releases/20150421105716/app/tmp) ]; then rm -rf deploy_path/releases/20150421105716/app/tmp; fi
Run: cd deploy_path && mkdir -p deploy_path/shared/app/tmp
Run: cd deploy_path && mkdir -p `dirname deploy_path/releases/20150421105716/app/tmp`
PHP Notice:  Unable to open channel in ***/phpseclib/Net/SSH2.php on line 3032
PHP Notice:  Connection closed prematurely in ***/phpseclib/Net/SSH2.php on line 3173
...
⤶ done on [dev]
✔ Ok
➤ Executing task deploy:writable
...
⤶ done on [dev]
✔ Ok
...
➤ Executing task success
Successfully deployed!
✔ Ok

Though it seems to be successful. I can tell all run commands after
PHP Notice:  Unable to open channel in ***/phpseclib/Net/SSH2.php on line 3032
PHP Notice:  Connection closed prematurely in ***/phpseclib/Net/SSH2.php on line 3173

were unsuccessful.
How can I tell that "clone/checkout command (update_code) has not finished but next tasks start"?
At the time of deploy:shared task running, I logged in the deploy server and saw my release folder had less than 4000 files.
Some of my friends have also faced kind of this problem since yesterday.

Hmm, never seen problems like this. Need to test it myself with big reps.

@elfet : For more information, I had not installed ssh2.

After installing ssh2, there were few successful deployments along with unsuccessful ones.

Is this problem related to these issues?
https://github.com/phpseclib/phpseclib/issues/134
https://github.com/phpseclib/phpseclib/issues/506

@elfet This problem happens after "composer update".
I've cloned master branch again to test and deployment was successful.
Then, I ran "composer update" and this problem occured again.
This was the update log:
composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Removing symfony/finder (v2.6.4)
  - Installing symfony/finder (v2.6.6)
    Loading from cache

  - Removing symfony/console (v2.6.4)
  - Installing symfony/console (v2.6.6)
    Loading from cache

  - Removing symfony/process (v2.6.4)
  - Installing symfony/process (v2.6.6)
    Loading from cache

  - Removing sebastian/version (1.0.4)
  - Installing sebastian/version (1.0.5)
    Downloading: 100%

  - Removing sebastian/environment (1.2.1)
  - Installing sebastian/environment (1.2.2)
    Downloading: 100%

  - Removing sebastian/diff (1.2.0)
  - Installing sebastian/diff (1.3.0)
    Downloading: 100%

  - Removing symfony/yaml (v2.6.4)
  - Installing symfony/yaml (v2.6.6)
    Downloading: 100%

  - Removing phpspec/prophecy (v1.3.1)
  - Installing phpspec/prophecy (1.4.0)
    Downloading: 100%

  - Removing phpunit/phpunit-mock-objects (2.3.0)
  - Installing phpunit/phpunit-mock-objects (2.3.1)
    Downloading: 100%

  - Removing phpunit/php-token-stream (1.4.0)
  - Installing phpunit/php-token-stream (1.4.1)
    Downloading: 100%

  - Removing phpunit/php-file-iterator (1.3.4)
  - Installing phpunit/php-file-iterator (1.4.0)
    Downloading: 100%

  - Removing phpunit/php-code-coverage (2.0.15)
  - Installing phpunit/php-code-coverage (2.0.16)
    Downloading: 100%

  - Removing phpunit/phpunit (4.5.0)
  - Installing phpunit/phpunit (4.6.4)
    Downloading: 100%

  - Removing herzult/php-ssh (v1.1.0)
  - Installing herzult/php-ssh (v1.1.1)
    Downloading: 100%

  - Removing symfony/debug (v2.6.4)
  - Installing symfony/debug (v2.6.6)
    Loading from cache

  - Removing symfony/expression-language (v2.6.4)
  - Installing symfony/expression-language (v2.6.6)
    Loading from cache

  - Removing react/socket-client (v0.4.2)
  - Installing react/socket-client (v0.4.3)
    Loading from cache

  - Removing justinrainbow/json-schema (1.3.7)
  - Installing justinrainbow/json-schema (1.4.1)
    Loading from cache

  - Updating phpseclib/phpseclib dev-master (2c96af2 => 1b22d52)
    Checking out 1b22d523dce3a3134ef671f7189a8ce3a8e42044

Maybe there was problem with some package update. Can you have a check?
Thank you.

This problem is resolved when i fixed version of phpseclib
    "require": {
        "php": ">=5.4.0",
        "phpseclib/phpseclib": "dev-master#2c96af214bf1b5e29b707249108504b4e0041a21",
        "deployer/deployer": "dev-master"
    },

Thanks! Updated composer.json.
Really waiting for release of phpseclib/phpseclib lib. A lot of problems will gone. Also working on different ssh implementation for Deployer.


Make auto-resize match video aspect ratio

Fixes #565

Possibly we could only use setContentSize on non-OS X environments. Though I’m not sure how animations for other environments are affected.

Yes, that's what I was thinking. Other environments shouldn't pose problems, because the animate argument concerns only OS X.
We could test it on Linux just to be sure, however. I'll do that a bit later.

LGTM

I believe this is closed by #772. Thanks for your work @Goldob!


Fixes with key pressing, colors. More info in messages

Some improvements with key pressing (no needs in Enter key). Service messages were colorized. Added header to analyze boot message. Disclosed info about started, stopped, enabled and disabled services.

Hm...Font size checking in appearance-menu. :) I will try to implement it this evening.

Next target will be diclosing info about current active themes. Now I work on excluding unpredictable situations and messages.

And return command should be added to all functions. Like return STATUSVAR it makes code more clear for understanding.

Looks promising. I'll need to merge these manually because of the conflicts.

Hm, maybe. I'm not well in github.

Font size checking done

Okay, I implemented your changes manually and added font sorting.

Hm, some problems with pull request. New fixed files: appearance-menu, bmenu, initmenu, system-settings. How to pull them in good way?


Help text, grammar, spelling & style updates

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Pester test is included
[X] Spelling, grammar & other cleanup in Help and other text content

Purpose
To clean up grammar, style, spelling and other issues related to comment-based help and other text in functions.

Thanks so much andy 🙇


still not able to see/catch pokemons

I am still not able to catch pokemons; only walking going on. I see that the requirements.txt has the unknown 6 fix.
I did a pip install -r requirements.txt to download the fix; but still facing the issue?
Help much appreciated!
[2016-08-07 08:54:38] [x] Starting PokemonGo Bot....
[2016-08-07 08:54:38] [#] Scanning area for objects (1 / 2500)
[2016-08-07 08:54:38] [#] Walking from (40.744222, -74.042822) to (40.744222, -74.042822) for approx. 0.00 seconds
[#] (40.744222, -74.042822, 0)
[2016-08-07 08:54:52] [#] Scanning area for objects (2 / 2500)
[2016-08-07 08:54:52] [#] Walking from (40.744222, -74.042822) to (40.746722, -74.042822) for approx. 1.12 minutes
[2016-08-07 08:56:15] [#] Finished walking
[#] (40.746722, -74.042822, 0)
[2016-08-07 08:56:27] [#] Scanning area for objects (3 / 2500)
[2016-08-07 08:56:27] [#] Walking from (40.746722, -74.042822) to (40.746722, -74.040322) for approx. 51.00 seconds

You use an old version of the bot

Looks like you haven't updated the bot itself, did you git pull ?

Aha.. i guess i didnt; did a git pull ; pip install -r requirements.txt
am on dev branch
on doing a ./run.sh i get this:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x9c in position 1: ordinal not in range(128)
2016-08-07 09:07:23,051 [sentry.errors.uncaught] [ERROR] [u'OSError: encrypt.so: cannot open shared object file: No such file or directory', u'  File "pokecli.py", line 501, in ', u'  File "pokecli.py", line 130, in main', u'  File "pokecli.py", line 139, in report_summary', u'  File "pokemongo_bot/metrics.py", line 76, in capture_stats', u'  File "pokemongo_bot/api_wrapper.py", line 106, in call', u'  File "pokemongo_bot/api_wrapper.py", line 63, in _call', u'  File "pgoapi/pgoapi.py", line 210, in call', u'  File "pgoapi/rpc_api.py", line 85, in activate_signature', u'  File "ctypes/init.py", line 443, in LoadLibrary', u'  File "ctypes/init.py", line 365, in init']

Remove the pgoapi folder and reinstall the pgoapi.

also, have a look at #2769

This fixed it. Happy Farming!


equivalent to \d of PostgreSQL ?

Hi,
with PostgreSQL, we can see the description of a table, is it possible in the REPL?

There's no such shortcut in the repl yet, but you can run introspection queries.
To list object types:
SELECT schema::ObjectType { name };
To list properties an links of an object type:
    WITH Object := (SELECT schema::ObjectType
                    FILTER .name = '<fully-qualified object type name>`)
    SELECT Object.pointers {name};

For example:
    WITH Object := (SELECT schema::ObjectType
                    FILTER .name = 'std::Object')
    SELECT Object.pointers {name};

It makes sense for us to implement a similar set of commands to PostgreSQL \d. In principle, we now have one more mechanism in addition to introspection queries that can help us - DESCRIBE. Let's consider some of the features, first.
Many PostgreSQL commands allow to specify a pattern to be matched. The pattern rules are a mix of shell file name patterns, regexp, and identifier quoting. Which incidentally means that *, ., and ? don't have their regexp meaning and require extra care if they are needed in regexp. For example, instead of the regexp .+ one should use ?+, etc. I would argue that this is one of the areas where EdgeDB should try to clean up the confusion:

There's not a lot of value in forcing identifiers to lower-case (unless quoted) for EdgeDB simply because we have case-sensitive identifiers often of mixed case. However, we may want to make the matches case-insensitive by default.
Rather than rely on identifier quoting mechanism to force exact case match I would suggest adding a flag to the command to toggle case-sensitivity. This will reduce the overall complexity of rules and feature interaction for patterns.
There's no real incentive to use glob-like syntax, since we use :: as a module/name separator instead of . for an equivalent concept in PostgreSQL. So we would end up with *::* where PostgreSQL has *.*, which is neither here nor there in terms of similarity to something familiar. So it would make sense then to only use regexp patterns to provide flexibility in matches. The upside of this is that the users won't have to learn 2 flavors of regexp - one for \d commands and another for actual queries.
We can retain the overall rule that patterns without an explicit :: in them refer to short names in the currently selected module (e.g. default). Whereas to view all modules something like .*::Foo.* should be used. It's possible to scan the pattern for presence of explicit :: and match full names or short names based on that. In theory it would be possible to write patterns that match everything by kind of abusing this (e.g. ::|.*), but this digs into fairly advanced usage of regexp and there's no real harm.

To summarize, I would propose to use patterns that are case-insensitive regexps where the presence of a literal :: is interpreted that fully-qualified name must be matched, while its absence indicates that only short names in the current module will be matched. Case-sensitivity should be a command-level flag. I'm tempted to suggest C, but that may clash with something like \dC for displaying casts. So maybe M (for "match") or P (for "pattern") could work.

However, we may want to make the matches case-insensitive by default.

+1.
But how to make it case-sensitive? Upper-case I as in \dI foo|bar?

So it would make sense then to only use regexp patterns to provide flexibility in matches.

+1.

We can retain the overall rule that patterns without an explicit :: in them refer to short names in the currently selected module (e.g. default).

-1.
I wouldn't do any of that (implicit :: and current module scope) that -- seems overly complex UX. I'd simply match the pattern on fullnames in all modules.

. I'm tempted to suggest C, but that may clash with something like \dC for displaying casts. So maybe M (for "match") or P (for "pattern") could work.

The classic flag for case-insensitive regexp is i. I propose to do the reverse of that flag -- I.

We can retain the overall rule that patterns without an explicit :: in them refer to short names in the currently selected module (e.g. default).

-1.
I wouldn't do any of that (implicit :: and current module scope) that -- seems overly complex UX. I'd simply match the pattern on fullnames in all modules.

I think I see your point. I didn't take into account that in PostgreSQL the tendency is to have flat structure where everything is basically in the same "module". Whereas in EdgeDB we expect potentially a fair bit of module fragmentation (depending on coding style, of course). So treating :: as special makes less sense. With clear naming it won't matter and with multiple similar names across modules it's a benefit if the pattern picks them all up.

. I'm tempted to suggest C, but that may clash with something like \dC for displaying casts. So maybe M (for "match") or P (for "pattern") could work.

The classic flag for case-insensitive regexp is i. I propose to do the reverse of that flag -- I.

I like I just fine. +1

I think we should support the following commands:
  \d      NAME           describe type / function / view / etc
  \df     [PATTERN]      list functions
  \dA     [PATTERN]      list access methods
  \dC     [PATTERN]      list casts
  \dg     [PATTERN]      list roles
  \di     [PATTERN]      list indexes
  \do     [PATTERN]      list operators
  \dt     [PATTERN]      list object types
  \dT     [PATTERN]      list scalar types
  \du     [PATTERN]      list roles
  \dv     [PATTERN]      list views
  \l      [PATTERN]      list databases

Open question:

Should \dt and \dT show all types including the ones defined in modules std::,sys::, and cfg::? Or should we have an S modifier as in \dtS, \dTS, \dfS, etc to show system/standard types?

Another common feature of \d commands is that they often have an S variant that includes system/built-in items, whereas by default the results include only user-created items. We currently don't have a natural divide like that, or rather, it's inconsistent.
For example, SELECT Object{__type__:{name}} will ignore schema objects (ostensibly every TYPE is implicitly extending Object, though), and will include primarily user-created objects, but will also include arguably system objects like stdgraphql::Query and stdgraphql::Mutation singletons.
On the other hand, SELECT schema::ObjectType{name} or SELECT schema::Function{name} will dutifully list all such items present in the schema regardless of provenance.
So overall it appears that we tend to ignore the divide between system entities and user-created entities and simply rely on module names to filter them as needed. So we can use this in a form of an S flag for some commands (like listing types, scalars, or functions), where we would introduce an additional filter that omits all things that have names starting with any of the "system" modules by default and remove that restriction when the S flag is used.

To the commands I'd add:
\dm [PATTERN]      list modules

Otherwise I agree with the list.
One question, though: what are "access methods"?

Oh, and we want a \dc [PATTERN]    list constraints, too.

Additionaly, for functions and scalar types it may be useful to add extra flags (similar to function flags in PostgreSQL):
  \df[an]     [PATTERN]      list functions [only aggregate/normal]

Where aggregate functions are any functions with at least one SET OF arg.
  \dT[sen]     [PATTERN]      list scalar types [only sequences/enums/normal]

Oh, and we want a \dc [PATTERN] list constraints, too.

I'm not sure if it's going to be useful. Not sure we should have a command to list all indexes either. I'd skip them for now. @elprans?

Additionaly, for functions and scalar types it may be useful to add extra flags (similar to function flags in PostgreSQL):

I don't like the idea of separating functions and aggregates. We don't really separate them in our documentation; aggregate is a function with a SET OF parameter.  So I'd just stick to \df listing both.

Listing what constraints are available is useful when you know you need one, but forgot the exact name.
It's also useful to know which custom constraints have already been created so you don't blindly duplicate them.
Regarding indexes, knowing which things are indexed could be useful when trying to get a sense of what may be impacting a large complex query. Like trying to narrow down where to look first for optimizations. This bit is coming from ORM experience where a priory I don't always know which indexes will be created automatically and which I need to specify manually, so this kind of overview is useful.
Regarding aggregates, I can see why now it's not terribly relevant distinction, but it may be useful when we finally have GROUP working because that's where you may specifically want to only consider SET OF functions when constructing a query. So we can have a plain \df for now and maybe revisit this later in context of having GROUP.

OK on indexes & constraints; just need to tweak the output to make sure it's clear if a constraint is abstract or not. Need to also display clear type names / link/property names for non-abstract constraints and indexes.

Do we really have to follow the \dX command for listing things?  It seems like using \lX makes a bit more sense.  The X in \dX can then denote the schema class, which is directly related to DESCRIBE <SCHEMACLASS> syntax.

@elprans

Do we really have to follow the \dX command for listing things?

The only point of using \dX is to make Postgres users feel at home. I feel it's important. Although since you're a heavy Postgres user yourself I think you should make the call here.  So \lX or \dX?

I use psql quite often and I have to look them up most of the time, so I don’t think there’s much muscle memory there other than \dt. We can always put a hint into an error message about unrecognized command. I’m for \l

Then \l it is :) I like that it's consistent now.

This seems to be done. Feel free to open more specific issues in CLI repository.


ALPR

Describe the feature
An in-game ALPR that can pickup plates and get information such as DUIs, BOLOs, etc. Support for these scripts would be cool (https://forum.cfx.re/t/release-wraith-ars-2x-police-radar-and-plate-reader-v1-3-1/1058277 | https://forum.cfx.re/t/prefech-alpr/2653668)
Additional Context
No response

How would this connect to SnailyCAD? It sends a request to the CAD from those scripts?

Yes it would send a request to see if the plate is wanted or has a BOLO on it like (https://www.youtube.com/watch?v=5oL7Mg6LQgg&ab_channel=SonoranSoftwareSystems)

And where would the returned data show up?

@marshular progress can be tracked here: https://github.com/SnailyCAD/fivem-integrations, some screenshots
Note: this is a work-in-progress


us/windows/security/hardware-security/tpm/switch-pcr-banks-on-tpm-2-0-devices)

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 55b3bd7a-b069-ae6c-7ea3-257b8c78e2e0
Version Independent ID: 55b3bd7a-b069-ae6c-7ea3-257b8c78e2e0
Content: UnderstandPCR banks on TPM 2.0 devices - Windows Security
Content Source: windows/security/hardware-security/tpm/switch-pcr-banks-on-tpm-2-0-devices.md
Product: windows-client
Technology: itpro-security
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

Assuming a misfire, closing


az storage blob generate-sas Permission Errors

This is autogenerated. Please review and update as needed.
Describe the bug
I keep receiving permissions errors when I have contributor rights at the sub level.
Command Name
az storage blob generate-sas
Errors:

You do not have the required permissions needed to perform this operation.
Depending on your operation, you may need to be assigned one of the following roles:
    "Storage Blob Data Contributor"
    "Storage Blob Data Reader"
    "Storage Queue Data Contributor"
    "Storage Queue Data Reader"

If you want to use the old authentication method and allow querying for the right account key, please use the "--auth-mode" parameter and "key" value.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az storage blob generate-sas --account-name {} --container-name {} --name {} --permissions {} --expiry {} --auth-mode {} --as-user --https-only --full-uri

Expected Behavior
There should not be perms errors.
Environment Summary
macOS-10.14.6-x86_64-i386-64bit
Python 3.8.10
Installer: HOMEBREW

azure-cli 2.23.0

Extensions:
dev-spaces 1.0.6
k8s-configuration 1.0.0
connectedk8s 1.1.3
k8s-extension 0.2.1
deploy-to-azure 0.2.0
resource-graph 1.1.0
customlocation 0.1.2
vm-repair 0.3.5
image-copy-extension 0.2.8

Additional Context

resolved with guidance in https://docs.microsoft.com/en-us/rest/api/storageservices/create-user-delegation-sas#assign-permissions-with-rbac.

This was resolved by granting the explicit permissions in that article to me, although I have contributor at a sub level, this should be referenced in the CLI and PS docs.


Add support for RequireJS

I know this repo is called node-oauth, but its probably not hard to make it compatible with RequireJS and then you could change the name to oauth and take over the world. How hard can it be?
I've started this at https://github.com/cblair/node-oauth, I'll finish and start a PR or give up if I find an easier RequireJS oauth solution.
Thanks!

Things went swimmingly until hitting require('crypto'). At this point, I'm not converting and using the best alternative to that node.js library (crypto-js I think).
Running away for now.


Not the same file structure in the original github repo for Time 22b-27b?

Hi.
I cloned the Time repo from the following URL:
https://github.com/JodaOrg/joda-time.git
I checked out the revision IDs from the following file:
defects4j/framework/projects/Time/commit-db
But the file structure for checked out versions according to rows 22-27
do not correspond as is to 22b-27b in defects4j version.
For e.g. in the version for 22b from original github repo I have these files:
JodaTime/
JodaTimeContrib/

and for the version in defects4j I have these files:
checkstyle.xml
LICENSE.txt
NOTICE.txt
release.bat
defects4j.build.properties
pom.xml
RELEASE-NOTES.txt
build.xml
JodaTimeContrib/
src/

Do you have any rules on how you restructured it?
Or any scripts?
Thanks in advance.
-Ismail

Hi @shaikhismail,
The only rule that Defects4J applies is:

if, after checking out a buggy or a fixed project version, the top-level directory JodaTime exists in the working directory, move its content to the working directory (mv <working_dir>/JodaTime/* <working_dir>/).

In your example, all files that Defects4J provides in the working directory are exactly the same files that exist under the directory JodaTime in the original repository.
The rationale for this restructuring of older JodaTime versions is that each project version should be uniformly compilable and testable from within the working directory.
Let me know if you have further questions.
Thanks,
René

Hi @rjust ,
Got your point.
Many thanks for the response.
-Ismail


Unhandled Exception: type '_Type' is not a subtype of type 'IBaseModel' in type cast

abstract class IBaseModel {
  String get table => throw UnimplementedError();
}

class BotModel extends IBaseModel {
  @override
  String get table => "bots";
}

abstract class IBaseMigration<T extends IBaseModel> {

  const IBaseMigration();

  String get table => (T as IBaseModel).table;

  Future<void> up(Database db) {
    throw UnimplementedError();
  }

}

class BotMigration extends IBaseMigration<BotModel> {

  const BotMigration();

  @override
  Future<void> up(Database db) async {
    print("table $table");  //  Unhandled Exception: type '_Type' is not a subtype of type 'IBaseModel' in type cast
  }

}

// But if i'am print table getter like this
abstract class IBaseMigration<T extends IBaseModel> {
  const IBaseMigration();

  // here
  Type get table => T;

  Future<void> up(Database db) {
    throw UnimplementedError();
  }

}

class BotMigration extends IBaseMigration<BotModel> {

  const BotMigration();

  @override
  Future<void> up(Database db) async {

    print("model $table"); // output: model BotModel
    print("is IBaseModel ${table is IBaseModel}"); // output // is IBaseModel false

}

This tracker is for issues related to:

Dart VM

If you aren't sure, file the issue here, and we'll find the right home for it.
In your issue, please include:

Dart 3.4.0 (stable) (Mon May 6 07:59:58 2024 -0700) on "windows_x64"
on windows / "Windows 10 Pro" 10.0 (Build 22621)

and the second question is, when inheriting in generic, methods or properties are not visible

Expected these methods:

Dart does not allow access to static methods through type variables. That's why the only members you can see for T. are the ones on Type objects.
That's also why (T as IBaseModel) fails, the type variable T is evaluated as an expression which gives you a Type object, an instance of the class Type, which cannot be cast to IBaseModel, so the cast throws.

@lrhn I understand you, thanks so much🔥


KMS: encrypt private keys

KeyManagementSystem should take an encryption key as a constructor param, and then use it to encrypt/decrypt private keys that are stored by the KeyStore

It makes more sense to do this encryption in KeyStore, and not in the KMS

It makes more sense to do this encryption in KeyStore, and not in the KMS

:) I was about to comment this when you first posted the issue but see that you already did it in the implementation


Replace SPv1 with SPv2

Rework the pipeline, after PDF download, so that text gets extracted with a containerized SPv2 server.

https://github.com/allenai/spv2

PDF text extraction by SPv1 may not provide sufficient support for feature engineering needed in the competition:

That version works differently, and does generally worse, but it's faster, and has more features than this one.

Best to start with the pre-built Docker container from @allenai that's at https://hub.docker.com/r/allenai/spv2

Whoever works on this issue, please talk with @philipskokoh to compare notes

Then update instructions for launch and use in Downloading-Resource-Files

Hi @ceteri, I think spv2 is not a good option since it's no longer being maintained (deprecated). The current spv2 only parses title, authors, and bibliographies (see this issue). It also skews toward medical documents (see https://github.com/allenai/spv2/issues/42#issuecomment-444665509).
Another option that might be better is grobid.

Many thanks @philipskokoh !


[SYMFONY53] replace getCollectionKeyType and getCollectionValueType with getCollectionKeyTypes and getCollectionValueTypes

Make sure to write a custom rule for this as return type has changed more information can be found on the symfony pull request
Some more info https://github.com/rectorphp/rector-symfony/pull/283

Finally getting to these issues, thanks for you patience!
These might require quite a refactoring, as single value to multiple values is not A → B refactoring.
Closing as we can't handle this. Manual work is needed here :)


Community Meeting February 7, 2024

Overview
At 10am Eastern, 7am Pacific, 2pm UTC; find your time
Video call link: https://meet.google.com/ved-ivnv-aen
dial-in: (US) +1<PHONE_NUMBER>
PIN: 873 550 579#
More phone numbers: tel.meet/ved-ivnv-aen?pin=7872592963542&hs=1
Add topics you'd like to discuss below!

How to handle time based data as input in Enterprise Contract.

Meeting recording: https://drive.google.com/file/d/12hjgblYp5MCCgXLmJvOPQ_hS-Jw2yY3c/view?usp=drive_link


Ensure that all members have CrunchBaseURL

I will provide a list of elements which do not have a CrunchBaseURL in this request:
https://api-gw.platform.linuxfoundation.org/project-service/v1/public/projects/cncf/members?status=Active

These elements do not have a CrunchBaseURL property:
1&1 Mail&Media Development & Technology GmbH
1NCE GmbH
ADIDAS AG
ASUS Cloud Corporation
Acaisoft
Accurics
Acornsoft
Adfolks LLC
Alpha Bravo
Altinity
Ampere Computing
Anova
Ant Small and Micro Financial Services Group Co., Ltd.
Apolicy.io, Inc.
Appvia Ltd.
Architecht Information Technologies
Aspen Mesh
AuditBoard
Authkeys SRL
Balena, Inc.
BeOpenIt
Beijing Ruiyun Haotian Technology Co., Ltd.
Beijing Teamsun Technology Co., Ltd
Beijing Xuyun Technology Co., Ltd
Beijing Yan Rong Technology Co Ltd
Biqmind Pte Ltd
Blameless Inc
Blockchain Technology Partners
BoxBoat Technologies
Bridgecrew
Brobridge
Business-intelligence of Oriental Nations Corporation Ltd
CTO.ai
Carbon Relay
China-ASEAN Information Harbor Co., Ltd
Chronosphere, Inc.
CloudYuga
Cloudical
Clyso GmbH
Coinsquare
Component Soft
ControlPlane
Cookpad Inc. (UK)
Creationline, Inc.
Cuemby Inc.
Cyber Armor
D2iQ
DB Systel GmbH
Darumatic
Data Essential
Datadrivers
Decipher Technology Studios
Deepshore GmbH
DeployHub
Desotech srl
DevSpace Technologies Inc.
Dotscience
ELASTX
Elotl
Entegral
Entigo OÜ
Epsagon
Exoscale
F5 Networks, Inc.
FOSSA
Flant
Flowmill Inc.
Fullstaq
Futurewei Technologies, Inc.
Garden Technologies Inc.
HANGZHOU EMQ TECHNOLOGIES CO., LTD.
Hammerspace
Hangzhou FIT2CLOUD Information Technology Co., Ltd
Hangzhou HarmonyCloud Technology LTD.
Hangzhou Langhe Technology Co. Ltd. (Netease)
Hangzhou Launcher Technology Co., Ltd
IGNW
ILKI FRANCE
IMIDDLEWARE
INS Lab Inc.
In2tive FZCO
Infranetes sp. z o. o.
InwinSTACK
KBSYS Inc
KETI (Korea Electronics Technology Institute)
Kongsberg Satellite Services AS
KubeMQ Ltd.
Kubermatic
Kubernative GmbH
Kumina B.V
Layer5
Leftshift Solutions
Lenses.io Ltd.
Logiq.ai Inc.
Lunar
MHI Vestas Offshore Wind A/S
MathWorks, Inc.
Matrix I.T CloudZone LTD
MayaData
Meepl | Fision AG
Mia-Platform
Minio, Inc
Monostream AG
N-Able Opleidingen B.V.
N26 GmbH
N3NCLOUD
Nanjing eCloud Technology Co., Ltd.
Navitas Business Consulting Inc.
Nebulon
Neualto Technologies Private Limited
NexCloud
Nobl9
Noris Network AG
OGIS-RI Co., Ltd.
Octarine
Odo Security
OneCause, Inc.
Open Source Consulting Inc.
Ori Industries
Origoss Solutions
Ovoo Spółka z o. o.
PT Biznet Gio Nusantara
PT Boer Technology (BTech)
Packet Host, Inc.
Pixie Labs Inc.
PlanetScale Data
Platformer Cloud Pty Ltd
Polar Squad
Portshift
Projixi Europe
Pulumi
Raft
Rancher Federal
Red Kubes B.V.
Redeploy
Robin.io
Rookout
SIGHUP s.r.l.
SUSE LLC
Sakura Internet Inc.
Sensu, Inc
ServiceMEME
Shanghai eRoad Software Co., Ltd
Shenzhen Wise2C Technology Co.,Ltd
Shenzhen Yunduan Software Ltd.
SoKube
Sparkfabrik
Spectro Cloud Inc
Stackwatch Inc
Stakater AB
Stix Utvikling AS
Storm Reply GmbH
StreamNative
Structsure, LLC
Styra
Suzhou Beyondcent & Software Co., Ltd. (BoCloud)
Synadia Communications
TFcloud (Beijing) Technology  Co., Ltd.
Talos Systems
Tectonic Labs Ltd.
Telecommunications Technology Association
TenxCloud
TeraSky
Tetrate.io
Teuto.net Netzdienste GmbH
TmaxA&C
TriggerMesh Inc.
Upbound
Upsider
VA Linux Systems Japan K.K.
Ventus Cloud AG
Viable Data
Volterra Inc
Wangsu Science & Technology Co., Ltd.
WhizUs GmbH
Windmill Engineering
Xiaoju Science Technology (Hong Kong) Limited
Zebrium, Inc.
Zettabytes, Inc.
effx inc.
rdx.net
vChain, Inc.
x-ion GmbH

Those elements do not have a logo:
1&1 Mail&Media Development & Technology GmbH
1NCE GmbH
ASUS Cloud Corporation
Accurics
Adventure Box Technology AB
Aerospike
AllCloud Platforms Ltd
Alter Way Cloud Consulting
Anova
Ant Small and Micro Financial Services Group Co., Ltd.
Apolicy.io, Inc.
Architecht Information Technologies
BeOpenIt
Beijing Teamsun Technology Co., Ltd
Beijing Yan Rong Technology Co Ltd
Biqmind Pte Ltd
Blue Sentry
Bridgecrew
Business-intelligence of Oriental Nations Corporation Ltd
CA Technologies
Canada Health Infoway
CloudCover Pte. Ltd.
Concur Technologies, Inc.
Conde Nast International
DB Systel GmbH
Datastax
Die Mobiliar
Doc.ai
EngineerBetter Ltd
Entegral
Equinix
Fidelity Investments
Futurewei Technologies, Inc.
Groupon
Hangzhou Launcher Technology Co., Ltd
HashiCorp
Hobsons
IMIDDLEWARE
INS Lab Inc.
In2tive FZCO
JD Cloud
King.com Limited
Kongsberg Satellite Services AS
Leftshift Solutions
Lenses.io Ltd.
Logiq.ai Inc.
Logz.io
MHI Vestas Offshore Wind A/S
Meepl | Fision AG
N-Able Opleidingen B.V.
N26 GmbH
N3NCLOUD
NN Group
NS1
Nanjing eCloud Technology Co., Ltd.
National Association of Insurance Commissioners
Nebulon
NetMatch
Nobl9
Nordstrom, Inc.
OGIS-RI Co., Ltd.
Open Source Consulting Inc.
OpenTable
Optum/UnitedHealth Group
Ori Industries
PT Biznet Gio Nusantara
Pagero AB
PayIt, LLC
Projixi Europe
QingCloud Technologies Corp.
Qiniu Limited
Rakuten, Inc.
Rancher Federal
Shanghai eRoad Software Co., Ltd
Sky Betting and Gaming
Snapt
Snow Software AB
SoKube
Springer Nature
Stakater AB
Suzhou Beyondcent & Software Co., Ltd. (BoCloud)
T-Mobile PCS Holdings LLC
Tectonic Labs Ltd.
Thought Machine Group Ltd.
TmaxA&C
US Air Force
Ventus Cloud AG
Viable Data
Wangsu Science & Technology Co., Ltd.
Xiaoju Science Technology (Hong Kong) Limited
Yelp
Zettaset, Inc.
ricardo.ch

Now, members without a website:
1&1 Mail&Media Development & Technology GmbH
MHI Vestas Offshore Wind A/S
N26 GmbH

I can fetch a website from a crunchbase, @dankohn , should I fetch it from there or that api request should always return entries with a website field ?

We should fail if SFDC doesn't include a website.

I added websites for the 3 that were missing

For the Crunchbase entries, does the format in SFDC need to be /organization/companyname, rather than the full URL?

No, that's just how it shows up in the API. Please make it look like other SFDC entries.

@dankohn FYI, we have moved logos from the account logo object to account.

Thank you!
Here is a list of remaining entries
Beijing Teamsun Technology Co., Ltd
Conde Nast International
Entegral
Groupon
Hobsons
IMIDDLEWARE
N3NCLOUD
Nebulon
Nordstrom, Inc.
OpenTable
Qiniu Limited
US Air Force

@taylorwaggoner I dont see them in SFDC. Can you please add URL in SFDC?

Beijing Teamsun Technology Co., Ltd. - they haven't provided a logo yet
IMIDDLEWARE - they haven't provided a logo yet
Conde Nast International - not a public member, no logo
Entegral - not a public member, no logo
Groupon - not a public member, no logo
Hobsons - not a public member, no logo
Nebulon - not a public member, no logo
Nordstrom, Inc. - not a public member, no logo
OpenTable - not a public member, no logo
US Air Force - not a public member, no logo
N3NCLOUD - logo added to SFDC
Qiniu Limited - logo added to SFDC

@niravpatel27 Non-public members should not be served via the API. Is there a checkbox to prevent that, separate from whether we have a logo for them?

@dankohn @taylorwaggoner Lets brainstorm this.
Entegral has End-User Membership 2020 which is expiring in Aug 2020
Conde Nast International has End-User Membership 2020
Looks like all has End-User Membership 2020.
If you don't want to display End User Membership then could you please add logic while you looping over?
i.e skip where Membership.name = End-User Membership
  {
    "ID": "0012M00002Fy4USQAZ",
    "Name": "Entegral",
    "Membership": {
      "Family": "Membership",
      "ID": "01t41000002735mAAA",
      "Name": "End-User Membership",
      "Status": "Active"
    },
    "Website": "https://www.entegral.com"
  },

No, end user membership is orthogonal from nonpublic members. You can see on https://landscape.cncf.io/format=members&organization=non-public-unnamed-organization that we currently have 14 non-public members: 1 silver, 3 silver end user, 9 end user supporter, and 1 nonprofit.
It would probably be better if you could create an account on https://slack.cncf.io and ping me there to discuss.


Fix Missing error statements during deploy

This PR fixes an issue where deployment error messages where not properly
reported during prepare/deploy

Codecov Report

Merging #489 (d7bcb51) into develop (151e1c0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #489   +/-   ##
========================================
  Coverage    80.56%   80.56%
========================================
  Files           34       34
  Lines         1158     1158
  Branches       206      206
========================================
  Hits           933      933
  Misses         225      225

Continue to review full report at Codecov.

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


Potential Integration of Bitcoin Lightning Network's Zap Feature into Bluesky

Describe the Feature
Overview:
With the rise of digital microtransactions in social media platforms, integrating a feature similar to NOSTR's Zap via the Bitcoin Lightning Network could significantly enhance user interaction and add a valuable monetary layer to Bluesky. The Zap feature allows users to send small tips, or "sats," to each other quickly and with minimal fees, facilitating streamlined value exchange on the platform.
What are Zaps?
Zaps are microtransactions transmitted over the Bitcoin Lightning Network, primarily used as tips. They occur almost instantaneously and incur negligible transaction fees, making them an efficient way to send small amounts of Bitcoin.

Interaction with LNURL Server: The client's application communicates with an LNURL server associated with the recipient's Lightning wallet.
Generating an Invoice: The server confirms the wallet's compatibility and issues an invoice request.
Payment: The user pays the invoice through their Lightning wallet.
Broadcasting the Transaction: Once the payment is made, the recipient's wallet broadcasts a confirmation note to specified network relays.

Potential Benefits for Bluesky:

Increased User Engagement: By enabling users to tip content creators, engagement and content quality could see a boost.
Monetization Opportunities: Content creators and influencers could find new revenue streams without traditional advertising dependencies.
Cross-Platform Compatibility: Interoperability with existing Lightning wallets encourages seamless integration without reinventing the wheel.

Implementation:
To integrate this feature into Bluesky, partnering with a third-party provider that specializes in the Bitcoin Lightning Network could be a strategic move. Potential partners include:

LightSpark: Offers a robust infrastructure for seamless Lightning Network transactions.
Opennode: Provides a comprehensive API for integrating Bitcoin payments into various platforms.

Technical Considerations:

Security: Implement robust security protocols to protect both user data and transactions.
User Interface: Ensure the Zap feature is intuitive and easily accessible within the Bluesky app.
Compliance: Stay updated with financial regulations to ensure all transactions comply with local and international laws.

Conclusion:
Incorporating a feature akin to NOSTR's Zap into Bluesky could be a game-changer, fostering a new dimension of user interaction and financial transactions on the platform. By leveraging the speed and cost-effectiveness of the Bitcoin Lightning Network, Bluesky can reinforce its position as a forward-thinking social media platform.
Attachments
LightSpark: https://www.lightspark.com/
Opennode: https://opennode.com/
Lightning Network Wikipedia: https://en.wikipedia.org/wiki/Lightning_Network
What is NOSTR's Zap Feature?:
https://nostr.how/en/zaps
Describe Alternatives
No response
Additional Context
No response

@T3kn3vr4 Dear user
I understand that you have been experiencing some issues and I want to ensure you get the support you need as quickly as possible by using our live chat option.
Support : Support
1.	Access the Live Chat:
•	Navigate to our website’s home page.
•	Look for the chat icon located at the bottom right corner of the screen and start a 💬.

I'll be honest, I wouldn't like this added into bluesky and this can and will receive enormous pushback from a sizeable portion of the userbase.

I'll be honest, I wouldn't like this added into bluesky and this can and will receive enormous pushback from a sizeable portion of the userbase.

Just curious, why not?
Not that I'm super invested in the feature.


rancher-compose: init at 0.10.0

Motivation for this change
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

The version of rancher-compose must match with the corresponding rancher server. So I suppose because people deal with different environments the version of this package should be more flexible.


#8027: build_metal.sh cleanup

moved stubs generation to it's own script
moved git hooks intocreate_venv.sh
build_metal now has a description/instructions on how to use the cmake flow (not sure if it belongs there)

Fantastic
That huge essay in build_metal.sh is great but not sure if it's the right place either. I'm okay with it for now, but I'm wondering if either of these two options is better:

CONTRIBUTING.md#advanced-install
INSTALLING.md#advanced-install (we should ask Customer release team (Antonio / Shubham etc) if it's approriate)

Fantastic
That huge essay in build_metal.sh is great but not sure if it's the right place either. I'm okay with it for now, but I'm wondering if either of these two options is better:

CONTRIBUTING.md#advanced-install
INSTALLING.md#advanced-install (we should ask Customer release team (Antonio / Shubham etc) if it's approriate)

I was thinking we can put a trimmed down version of that essay in the install / contributing guide


Operator Patterns ID Localization.

Hi,
I added ID localization for concepts/extend-kubernetes/operator.md.
Thank you,
Aris.

Hi @ariscahyadi 👋 Any update on this?

thanks for translating this page, I learned a lot about Operator's useful resources for my daily work :P
I gave couple of comments, please address them. Most importantly:

We use "kamu" instead of "anda" in our translations, because it's more friendly and warm welcoming
All API objects must be written in CamelCase without Backtick, you can take a look at the list here
Italicize imported english word: write "controller" instead of "controller".
You also have to translate the hyperlink (the word inside [] bracket), and its anchor

I have pushed new commit.

Hi @ariscahyadi 👋 Any update on this?

I just pushed new commit.

Thank you, by the way can you please squash it to one commit?

/assign

Thank you, by the way can you please squash it to one commit?

In my branch? I am not sure how to do it :)

Yes on your branch.
git rebase -i master
After that you can see there is a several lines that either you can pick or squash.
Then you can change pick to squash. Usually we left the first pick clause as it is. And change the rest to squash.
https://github.com/wprig/wprig/wiki/How-to-squash-commits

Yes on your branch.
git rebase -i master
After that you can see there is a several lines that either you can pick or squash.
Then you can change pick to squash. Usually we left the first pick clause as it is. And change the rest to squash.
https://github.com/wprig/wprig/wiki/How-to-squash-commits

It is done! Thanks.

thanks mas @ariscahyadi , great work! 🎉  one last request from me, can you replace Kamu with lowercase kamu, then we can get this in

thanks mas @ariscahyadi , great work! 🎉 one last request from me, can you replace Kamu with lowercase kamu, then we can get this in

It's done :)
Please check!

Amazing, thanks! Looking forward to your next contribution 😄
/lgtm
/approve


sigfig:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: Explain what the package does and why it's useful.

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] excluded PDFs or README images, if any, but not the LICENSE
[x] tested my package locally on my system and it worked
[ ] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

(Don't know if the name is appropriate. Please tell me to change it if informal abbreviations like this are not allowed.)

Looks good, thanks :)


[TASK] Remove Guaranteed Engine Manager CPU, Guaranteed Replica Manager CPU, and Guaranteed Engine CPU settings.

Is your improvement request related to a feature? Please describe
After consolidating engine and replica instance managers, the Guaranteed Engine Manager CPU and Guaranteed Replica Manager CPU settings serve no other purpose than to trigger the instance manager pod deletion.
The Guaranteed Engine CPU is ineffective after introducing the above two settings.
Describe the solution you'd like
Remove Guaranteed Engine Manager CPU, Guaranteed Replica Manager CPU, and Guaranteed Engine CPU settings.
Describe alternatives you've considered
Handle setting removal in https://github.com/longhorn/longhorn/issues/5844.
Additional context
https://github.com/longhorn/longhorn/issues/5208

Verified on master-head 20230530

longhorn master-head (7b3b230)
longhorn-manager master-head (023dd3c)

Result Passed

[x] - doc: https://github.com/longhorn/website/pull/671
[x] The UI on the master branch no longer includes the options for Guaranteed Engine Manager CPU and Guaranteed Replica Manager CPU.
[x] After upgrading Longhorn from version 1.4.x to the master branch, the options for Guaranteed Engine Manager CPU and Guaranteed Replica Manager CPU were removed from the UI.
[] We have a typo in the PR. Once the typo is fixed, I will close this ticket.

I like the checklist which will prevent any missing criteria for closing the issue.
cc @longhorn/qa


simple_broadcast.mlir is invalid

No broadcast op is getting called, and it's expecting from device to perform the broadcast %2 = "ttnn.from_device"(%1) : (tensor<1xf32, #ttnn_layout1>) -> tensor<32xf32, #ttnn_layout>
#device = #tt.device<workerGrid = #tt.grid<7x8, (d0, d1) -> (0, d0, d1)>, l1Map = (d0, d1)[s0, s1] -> (0, d0 floordiv s0, d1 floordiv s1, (d0 mod s0) * s1 + d1 mod s1), dramMap = (d0, d1)[s0, s1] -> (0, 0, ((((d0 floordiv s0) * 8 + d1 floordiv s1) * (s1 * s0) + (d0 mod s0) * s1 + d1 mod s1) floordiv 8192) mod 12, (((d0 floordiv s0) * 8 + d1 floordiv s1) * (s1 * s0) + (d0 mod s0) * s1 + d1 mod s1) floordiv 98304 + (((d0 floordiv s0) * 8 + d1 floordiv s1) * (s1 * s0) + (d0 mod s0) * s1 + d1 mod s1) mod 8192), meshShape = , chipIds = [0]>
#dram = #ttnn.buffer_type<dram>
#system_desc = #tt.system_desc<[{role = host, target_triple = "x86_64-pc-linux"}], [{arch = <wormhole_b0>, grid = 7x8, l1_size = 1499136, num_dram_channels = 12, dram_channel_size =<PHONE_NUMBER>, noc_l1_address_align_bytes = 16, pcie_address_align_bytes = 32, noc_dram_address_align_bytes = 32, l1_unreserved_base = 98816, erisc_l1_unreserved_base = 102624, dram_unreserved_base = 32, dram_unreserved_end =<PHONE_NUMBER>, physical_cores = {worker = [ 2x1,  2x2,  2x3,  2x4,  2x6,  2x7,  2x8,  2x9,  3x1,  3x2,  3x3,  3x4,  3x6,  3x7,  3x8,  3x9,  4x1,  4x2,  4x3,  4x4,  4x6,  4x7,  4x8,  4x9,  5x1,  5x2,  5x3,  5x4,  5x6,  5x7,  5x8,  5x9,  7x1,  7x2,  7x3,  7x4,  7x6,  7x7,  7x8,  7x9,  8x1,  8x2,  8x3,  8x4,  8x6,  8x7,  8x8,  8x9,  9x1,  9x2,  9x3,  9x4,  9x6,  9x7,  9x8,  9x9] dram = [ 1x0,  1x5,  2x5,  3x5,  5x0,  5x5,  7x0,  7x5,  8x5,  9x5,  11x0,  11x5] eth = [ 6x9] eth_inactive = [ 0x1,  0x2,  0x3,  0x4,  0x6,  0x7,  0x8,  0x9,  6x2,  6x3,  6x6,  6x7,  6x8]}, supported_data_types = [<f32>, <f16>, <bf16>, <bfp_f8>, <bfp_bf8>, <bfp_f4>, <bfp_bf4>, <bfp_f2>, <bfp_bf2>, <u32>, <u16>, <u8>], supported_tile_sizes = [ 4x16,  16x16,  32x16,  4x32,  16x32,  32x32], num_cbs = 32}, {arch = <wormhole_b0>, grid = 7x8, l1_size = 1499136, num_dram_channels = 12, dram_channel_size =<PHONE_NUMBER>, noc_l1_address_align_bytes = 16, pcie_address_align_bytes = 32, noc_dram_address_align_bytes = 32, l1_unreserved_base = 98816, erisc_l1_unreserved_base = 102624, dram_unreserved_base = 32, dram_unreserved_end =<PHONE_NUMBER>, physical_cores = {worker = [ 1x1,  1x2,  1x3,  1x4,  1x6,  1x7,  1x8,  1x9,  2x1,  2x2,  2x3,  2x4,  2x6,  2x7,  2x8,  2x9,  4x1,  4x2,  4x3,  4x4,  4x6,  4x7,  4x8,  4x9,  5x1,  5x2,  5x3,  5x4,  5x6,  5x7,  5x8,  5x9,  7x1,  7x2,  7x3,  7x4,  7x6,  7x7,  7x8,  7x9,  8x1,  8x2,  8x3,  8x4,  8x6,  8x7,  8x8,  8x9,  9x1,  9x2,  9x3,  9x4,  9x6,  9x7,  9x8,  9x9] dram = [ 1x0,  1x5,  2x5,  3x5,  5x0,  5x5,  7x0,  7x5,  8x5,  9x5,  11x0,  11x5] eth = [ 0x9] eth_inactive = [ 0x2,  0x3,  0x4,  0x6,  0x7,  0x8,  6x1,  6x2,  6x3,  6x4,  6x6,  6x7,  6x8,  6x9]}, supported_data_types = [<f32>, <f16>, <bf16>, <bfp_f8>, <bfp_bf8>, <bfp_f4>, <bfp_bf4>, <bfp_f2>, <bfp_bf2>, <u32>, <u16>, <u8>], supported_tile_sizes = [ 4x16,  16x16,  32x16,  4x32,  16x32,  32x32], num_cbs = 32}], [0, 1], [3 : i32, 0 : i32], [ 0x0x0x0], [<[0, 8, 0], [1, 0, 0]>]>
#system_memory = #ttnn.buffer_type<system_memory>
#ttnn_layout = #ttnn.ttnn_layout<(d0) -> (0, d0), <1x1>, memref<1x32xf32, #system_memory>>
#ttnn_layout1 = #ttnn.ttnn_layout<(d0) -> (0, d0), <1x1>, memref<1x1xf32, #dram>, interleaved>
module attributes {tt.device = #device, tt.system_desc = #system_desc} {
  func.func public @broadcast() -> tensor<32xf32, #ttnn_layout> {
    %0 = "ttnn.get_device"() <{mesh_shape = #ttnn<mesh_shape 1x1>}> : () -> !tt.device<#device>
    %1 = "ttnn.empty"(%0) <{dtype = #tt.supportedDataTypes<f32>, layout = #ttnn.layout<row_major>, memory_config = #ttnn.memory_config<<interleaved>, #dram, <<1x1>>>, shape = #ttnn.shape<1>}> : (!tt.device<#device>) -> tensor<1xf32, #ttnn_layout1>
    %2 = "ttnn.from_device"(%1) : (tensor<1xf32, #ttnn_layout1>) -> tensor<32xf32, #ttnn_layout>
    "ttnn.deallocate"(%1) <{force = false}> : (tensor<1xf32, #ttnn_layout1>) -> ()
    %3 = "ttnn.to_layout"(%2) <{layout = #ttnn.layout<row_major>}> : (tensor<32xf32, #ttnn_layout>) -> tensor<32xf32, #ttnn_layout>
    "ttnn.deallocate"(%2) <{force = false}> : (tensor<32xf32, #ttnn_layout>) -> ()
    return %3 : tensor<32xf32, #ttnn_layout>
  }
}

Yes this is currently not supported, maybe we can support it later when we have support for broadcast Op in TTNN or else a workaround, but for now you can delete it or replace with another test where the output of broadcast is consumed by an Eltwise Operation.

I have fixed the simple_broadcast.mlir test in this PR #1353

@jnie-TT What do you think about this comment from @mtopalovicTT  https://github.com/tenstorrent/tt-mlir/pull/1353/files#r1851559230

@uazizTT From what I understand we want to test the verifiers? If that's the case maybe we can add a test under Dialect and remove the Silicon one. What do you think?