Unable to upgrade to 2.2.1 from 1.12.0

Slack us first!
The easiest and fastest way to help you is via Slack. There's a free and easy signup to join our #defectdojo channel in the OWASP Slack workspace: Get Access.
If you're confident you've found a bug, or are allergic to Slack, you can submit an issue anyway.
Be informative
Please enter as much information as possible, otherwise we can't provide support. If possible upgrade to the latest release or dev version and try again.
Bug description
We are upgrading defect dojo from v 1.12.0 to 2.2.1 and facing issues with initializer container.
Unknown column 'dojo_test_type.active' in 'field list'
Steps to reproduce
Steps to reproduce the behavior:
upgrade to 2.2.1 from 1.12.0
Untar source code into previous folder containing old code(v 1.12.0)
docker build
docker compose
Expected behavior
A clear and concise description of what you expected to happen.
Deployment method (select with an X)

[ X] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Environment information

Operating System: [e.g. Ubuntu 18.04]
DefectDojo version (see footer) or commit message: [use git show -s --format="[%ci] %h: %s [%d]"]

Logs
initializer_1   | [13/Sep/2021 11:08:44] INFO [dojo.models:3616] enabling audit logging
initializer_1   | Operations to perform:
initializer_1   |   Apply all migrations: admin, auditlog, auth, authtoken, contenttypes, django_celery_results, dojo, sessions, sites, social_django, tagging, watson
initializer_1   | Running migrations:
initializer_1   |   Applying dojo.0088_import_history_cicd...Traceback (most recent call last):
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | MySQLdb._exceptions.OperationalError: (1060, "Duplicate column name 'branch_tag'")
initializer_1   |
initializer_1   | The above exception was the direct cause of the following exception:
initializer_1   |
initializer_1   | Traceback (most recent call last):
initializer_1   |   File "manage.py", line 11, in
initializer_1   |     execute_from_command_line(sys.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 401, in execute_from_command_line
initializer_1   |     utility.execute()
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 395, in execute
initializer_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 330, in run_from_argv
initializer_1   |     self.execute(*args, **cmd_options)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute
initializer_1   |     output = self.handle(*args, **options)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 85, in wrapped
initializer_1   |     res = handle_func(*args, **kwargs)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 245, in handle
initializer_1   |     fake_initial=fake_initial,
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
initializer_1   |     state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
initializer_1   |     state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
initializer_1   |     state = migration.apply(state, schema_editor)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply
initializer_1   |     operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/operations/fields.py", line 106, in database_forwards
initializer_1   |     field,
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/schema.py", line 89, in add_field
initializer_1   |     super().add_field(model, field)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 487, in add_field
initializer_1   |     self.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 142, in execute
initializer_1   |     cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 66, in execute
initializer_1   |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
initializer_1   |     return executor(sql, params, many, context)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 90, in exit
initializer_1   |     raise dj_exc_value.with_traceback(traceback) from exc_value
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | django.db.utils.OperationalError: (1060, "Duplicate column name 'branch_tag'")
initializer_1   | Admin user: admin
initializer_1   | [13/Sep/2021 11:08:53] INFO [dojo.models:3616] enabling audit logging
initializer_1   | Admin password: Initialization detected that the admin user admin already exists in your database.
initializer_1   | If you don't remember the admin password, you can create a new superuser with:
initializer_1   | $ docker-compose exec uwsgi /bin/bash -c 'python manage.py createsuperuser'
initializer_1   | Initialization of test_types
initializer_1   | [13/Sep/2021 11:08:55] INFO [dojo.models:3616] enabling audit logging
initializer_1   | Traceback (most recent call last):
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | MySQLdb._exceptions.OperationalError: (1054, "Unknown column 'dojo_test_type.active' in 'field list'")
initializer_1   |
initializer_1   | The above exception was the direct cause of the following exception:
initializer_1   |
initializer_1   | Traceback (most recent call last):
initializer_1   |   File "manage.py", line 11, in
initializer_1   |     execute_from_command_line(sys.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 401, in execute_from_command_line
initializer_1   |     utility.execute()
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 395, in execute
initializer_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 330, in run_from_argv
initializer_1   |     self.execute(*args, **cmd_options)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute
initializer_1   |     output = self.handle(*args, **options)
initializer_1   |   File "/app/dojo/management/commands/initialize_test_types.py", line 9, in handle
initializer_1   |     initialize_test_types()
initializer_1   |   File "/app/dojo/tools/factory.py", line 59, in initialize_test_types
initializer_1   |     test_type, created = Test_Type.objects.get_or_create(name=scan_type)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/manager.py", line 85, in manager_method
initializer_1   |     return getattr(self.get_queryset(), name)(*args, **kwargs)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 573, in get_or_create
initializer_1   |     return self.get(**kwargs), False
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 425, in get
initializer_1   |     num = len(clone)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 269, in len
initializer_1   |     self._fetch_all()
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 1308, in _fetch_all
initializer_1   |     self._result_cache = list(self._iterable_class(self))
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 53, in iter
initializer_1   |     results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql
initializer_1   |     cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 66, in execute
initializer_1   |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
initializer_1   |     return executor(sql, params, many, context)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 90, in exit
initializer_1   |     raise dj_exc_value.with_traceback(traceback) from exc_value
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | django.db.utils.OperationalError: (1054, "Unknown column 'dojo_test_type.active' in 'field list'")
defectdojo_initializer_1 exited with code 1
Sample scan files
If applicable, add sample scan files to help reproduce your problem.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context (optional)
Add any other context about the problem here.

Duplicate column name 'branch_tag'
Unknown column 'dojo_test_type.active' in 'field list'

this usually indicates an error in an earlier attempt to upgrade or earlier run of the initializer. can you provide all available logs, or try again from 1.12.0 and provide all logs.

Complete logs till point of failure:
docker-compose up
Starting defectdojo_mysql_1      ... done
Recreating defectdojo_rabbitmq_1  ... done
Starting defectdojo_initializer_1    ... done
Starting defectdojo_uwsgi_1          ... done
Recreating defectdojo_celeryworker_1 ... done
Recreating defectdojo_celerybeat_1   ... done
Attaching to defectdojo_mysql_1, defectdojo_rabbitmq_1, defectdojo_initializer_1, defectdojo_uwsgi_1, defectdojo_celerybeat_1, defectdojo_celeryworker_1
celerybeat_1    | wait-for-it.sh: waiting max 30 seconds for mysql:3306
celeryworker_1  | wait-for-it.sh: waiting max 30 seconds for mysql:3306
initializer_1   | wait-for-it.sh: waiting max 60 seconds for mysql:3306
mysql_1         | [Entrypoint] MySQL Docker Image 8.0.23-1.1.19
mysql_1         | [Entrypoint] Starting MySQL 8.0.23-1.1.19
uwsgi_1         | wait-for-it.sh: waiting max 30 seconds for mysql:3306
mysql_1         | 2021-09-13T11:08:28.621431Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.23) starting as process 24
mysql_1         | 2021-09-13T11:08:28.630011Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
mysql_1         | 2021-09-13T11:08:28.988920Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
mysql_1         | 2021-09-13T11:08:29.231394Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
mysql_1         | 2021-09-13T11:08:29.582335Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
mysql_1         | 2021-09-13T11:08:29.593205Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
mysql_1         | 2021-09-13T11:08:29.984266Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
mysql_1         | 2021-09-13T11:08:29.984551Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
mysql_1         | 2021-09-13T11:08:30.010678Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.23'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server - GPL.
rabbitmq_1      |
rabbitmq_1      |               RabbitMQ 3.6.15. Copyright (C) 2007-2018 Pivotal Software, Inc.
rabbitmq_1      |   ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
rabbitmq_1      |   ##  ##
rabbitmq_1      |   ##########  Logs<EMAIL_ADDRESS>rabbitmq_1      |   ######  ##<EMAIL_ADDRESS>rabbitmq_1      |   ##########
rabbitmq_1      |               Starting broker...
initializer_1   | wait-for-it.sh: mysql:3306 is available after 1 seconds
initializer_1   | Initializing.
uwsgi_1         | wait-for-it.sh: mysql:3306 is available after 1 seconds
celerybeat_1    | wait-for-it.sh: mysql:3306 is available after 1 seconds
celerybeat_1    | uid=0(root) gid=0(root) groups=0(root)
celeryworker_1  | wait-for-it.sh: mysql:3306 is available after 1 seconds
uwsgi_1         | AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
celeryworker_1  | uid=0(root) gid=0(root) groups=0(root)
initializer_1   | Waiting for database to be reachable [13/Sep/2021 11:08:32] INFO [dojo.models:3616] enabling audit logging
initializer_1   |
initializer_1   | Making migrations
celeryworker_1  | Waiting for database to be reachable [13/Sep/2021 11:08:32] INFO [dojo.models:3616] enabling audit logging
celerybeat_1    | Waiting for database to be reachable [13/Sep/2021 11:08:32] INFO [dojo.models:3616] enabling audit logging
rabbitmq_1      |  completed with 0 plugins.
celeryworker_1  |
celerybeat_1    |
initializer_1   | [13/Sep/2021 11:08:34] INFO [dojo.models:3616] enabling audit logging
celerybeat_1    | [13/Sep/2021 11:08:35] INFO [dojo.models:3616] enabling audit logging
celeryworker_1  | [13/Sep/2021 11:08:35] INFO [dojo.models:3616] enabling audit logging
uwsgi_1         | [uWSGI] getting INI configuration from /etc/httpd/uwsgi.ini
uwsgi_1         | [uwsgi-static] added mapping for /static => /app/dojo/static/
uwsgi_1         | *** Starting uWSGI <IP_ADDRESS> (64bit) on [Mon Sep 13 11:08:35 2021] ***
uwsgi_1         | compiled with version: 4.8.5 20150623 (Red Hat 4.8.5-44.0.3) on 13 September 2021 10:01:09
uwsgi_1         | os: Linux-4.14.35-2025.404.1.1.el7uek.x86_64 #2 SMP Tue Jan 5 12:57:13 PST 2021
uwsgi_1         | nodename: fed4c053a4d6
uwsgi_1         | machine: x86_64
uwsgi_1         | clock source: unix
uwsgi_1         | pcre jit disabled
uwsgi_1         | detected number of CPU cores: 8
uwsgi_1         | current working directory: /app
uwsgi_1         | detected binary path: /usr/local/bin/uwsgi
uwsgi_1         | uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1         | *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
uwsgi_1         | *** WARNING: you are running uWSGI without its master process manager ***
uwsgi_1         | your memory page size is 4096 bytes
uwsgi_1         | detected max file descriptor number: 1048576
uwsgi_1         | building mime-types dictionary from file /etc/mime.types...1060 entry found
uwsgi_1         | lock engine: pthread robust mutexes
uwsgi_1         | thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi_1         | uwsgi socket 0 bound to TCP address <IP_ADDRESS>:3031 fd 3
uwsgi_1         | uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1         | *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
uwsgi_1         | Python version: 3.7.7 (default, Jul 30 2020, 17:38:22)  [GCC 4.8.5 20150623 (Red Hat 4.8.5-39.0.5)]
uwsgi_1         | Python main interpreter initialized at 0xe66100
uwsgi_1         | uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1         | *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
uwsgi_1         | python threads support enabled
uwsgi_1         | your server socket listen backlog is limited to 100 connections
uwsgi_1         | your mercy for graceful operations on workers is 60 seconds
uwsgi_1         | mapped 166752 bytes (162 KB) for 4 cores
uwsgi_1         | *** Operational MODE: preforking+threaded ***
uwsgi_1         | [13/Sep/2021 11:08:37] INFO [dojo.models:3616] enabling audit logging
uwsgi_1         | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0xe66100 pid: 1 (default app)
uwsgi_1         | uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1         | *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
uwsgi_1         | *** uWSGI is running in multiple interpreter mode ***
uwsgi_1         | spawned uWSGI worker 1 (pid: 1, cores: 2)
uwsgi_1         | spawned uWSGI worker 2 (pid: 29, cores: 2)
uwsgi_1         | spawned 8 offload threads for uWSGI worker 1
uwsgi_1         | spawned 8 offload threads for uWSGI worker 2
initializer_1   | No changes detected in app 'dojo'
celerybeat_1    | [13/Sep/2021 11:08:42] INFO [celery.beat:634] beat: Starting...
celeryworker_1  | /usr/local/lib/python3.7/site-packages/celery/platforms.py:835: SecurityWarning: You're running the worker with superuser privileges: this is
celeryworker_1  | absolutely not recommended!
celeryworker_1  |
celeryworker_1  | Please specify a different user using the --uid option.
celeryworker_1  |
celeryworker_1  | User information: uid=0 euid=0 gid=0 egid=0
celeryworker_1  |
celeryworker_1  |   uid=uid, euid=euid, gid=gid, egid=egid,
celeryworker_1  |
celeryworker_1  |  -------------- celery@9347c127dee4 v5.1.2 (sun-harmonics)
celeryworker_1  | --- ***** -----
celeryworker_1  | -- ******* ---- Linux-4.14.35-2025.404.1.1.el7uek.x86_64-x86_64-with-redhat-7.9-Maipo 2021-09-13 11:08:42
celeryworker_1  | - *** --- * ---
celeryworker_1  | - ** ---------- [config]
celeryworker_1  | - ** ---------- .> app:         dojo:0x7f4ae4cb3d10
celeryworker_1  | - ** ---------- .> transport:   amqp://guest:@rabbitmq:5672//
celeryworker_1  | - ** ---------- .> results:
celeryworker_1  | - *** --- * --- .> concurrency: 1 (solo)
celeryworker_1  | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
celeryworker_1  | --- ***** -----
celeryworker_1  |  -------------- [queues]
celeryworker_1  |                 .> celery           exchange=celery(direct) key=celery
celeryworker_1  |
celeryworker_1  |
celeryworker_1  | [tasks]
celeryworker_1  |   . dojo.celery.debug_task
celeryworker_1  |   . dojo.finding.helper.post_process_finding_save
celeryworker_1  |   . dojo.jira_link.helper.add_comment
celeryworker_1  |   . dojo.jira_link.helper.add_epic
celeryworker_1  |   . dojo.jira_link.helper.add_jira_issue_for_finding
celeryworker_1  |   . dojo.jira_link.helper.add_jira_issue_for_finding_group
celeryworker_1  |   . dojo.jira_link.helper.close_epic
celeryworker_1  |   . dojo.jira_link.helper.update_epic
celeryworker_1  |   . dojo.jira_link.helper.update_jira_issue_for_finding
celeryworker_1  |   . dojo.jira_link.helper.update_jira_issue_for_finding_group
celeryworker_1  |   . dojo.notifications.helper.send_mail_notification
celeryworker_1  |   . dojo.notifications.helper.send_msteams_notification
celeryworker_1  |   . dojo.notifications.helper.send_slack_notification
celeryworker_1  |   . dojo.risk_acceptance.helper.expiration_handler
celeryworker_1  |   . dojo.tasks.add_alerts
celeryworker_1  |   . dojo.tasks.async_dupe_delete
celeryworker_1  |   . dojo.tasks.async_sla_compute_and_notify_task
celeryworker_1  |   . dojo.tasks.celery_status
celeryworker_1  |   . dojo.tasks.cleanup_alerts
celeryworker_1  |   . dojo.tasks.fix_loop_duplicates_task
celeryworker_1  |   . dojo.tasks.jira_status_reconciliation_task
celeryworker_1  |   . dojo.tools.tool_issue_updater.tool_issue_updater
celeryworker_1  |   . dojo.tools.tool_issue_updater.update_findings_from_source_issues
celeryworker_1  |   . dojo.utils.add_external_issue
celeryworker_1  |   . dojo.utils.calculate_grade
celeryworker_1  |   . dojo.utils.close_external_issue
celeryworker_1  |   . dojo.utils.do_dedupe_finding_task
celeryworker_1  |   . dojo.utils.reopen_external_issue
celeryworker_1  |   . dojo.utils.update_external_issue
celeryworker_1  |
celeryworker_1  | [13/Sep/2021 11:08:42] INFO [celery.worker.consumer.connection:22] Connected to amqp://guest:@rabbitmq:5672//
celeryworker_1  | [13/Sep/2021 11:08:42] INFO [celery.worker.consumer.mingle:40] mingle: searching for neighbors
initializer_1   | Migrating
celeryworker_1  | [13/Sep/2021 11:08:43] INFO [celery.worker.consumer.mingle:49] mingle: all alone
celeryworker_1  | [13/Sep/2021 11:08:43] INFO [celery.apps.worker:176] celery@9347c127dee4 ready.
initializer_1   | [13/Sep/2021 11:08:44] INFO [dojo.models:3616] enabling audit logging
initializer_1   | Operations to perform:
initializer_1   |   Apply all migrations: admin, auditlog, auth, authtoken, contenttypes, django_celery_results, dojo, sessions, sites, social_django, tagging, watson
initializer_1   | Running migrations:
initializer_1   |   Applying dojo.0088_import_history_cicd...Traceback (most recent call last):
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | MySQLdb._exceptions.OperationalError: (1060, "Duplicate column name 'branch_tag'")
initializer_1   |
initializer_1   | The above exception was the direct cause of the following exception:
initializer_1   |
initializer_1   | Traceback (most recent call last):
initializer_1   |   File "manage.py", line 11, in
initializer_1   |     execute_from_command_line(sys.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 401, in execute_from_command_line
initializer_1   |     utility.execute()
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 395, in execute
initializer_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 330, in run_from_argv
initializer_1   |     self.execute(*args, **cmd_options)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute
initializer_1   |     output = self.handle(*args, **options)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 85, in wrapped
initializer_1   |     res = handle_func(*args, **kwargs)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 245, in handle
initializer_1   |     fake_initial=fake_initial,
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
initializer_1   |     state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
initializer_1   |     state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
initializer_1   |     state = migration.apply(state, schema_editor)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply
initializer_1   |     operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/operations/fields.py", line 106, in database_forwards
initializer_1   |     field,
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/schema.py", line 89, in add_field
initializer_1   |     super().add_field(model, field)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 487, in add_field
initializer_1   |     self.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 142, in execute
initializer_1   |     cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 66, in execute
initializer_1   |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
initializer_1   |     return executor(sql, params, many, context)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 90, in exit
initializer_1   |     raise dj_exc_value.with_traceback(traceback) from exc_value
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | django.db.utils.OperationalError: (1060, "Duplicate column name 'branch_tag'")
initializer_1   | Admin user: admin
initializer_1   | [13/Sep/2021 11:08:53] INFO [dojo.models:3616] enabling audit logging
initializer_1   | Admin password: Initialization detected that the admin user admin already exists in your database.
initializer_1   | If you don't remember the admin password, you can create a new superuser with:
initializer_1   | $ docker-compose exec uwsgi /bin/bash -c 'python manage.py createsuperuser'
initializer_1   | Initialization of test_types
initializer_1   | [13/Sep/2021 11:08:55] INFO [dojo.models:3616] enabling audit logging
initializer_1   | Traceback (most recent call last):
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | MySQLdb._exceptions.OperationalError: (1054, "Unknown column 'dojo_test_type.active' in 'field list'")
initializer_1   |
initializer_1   | The above exception was the direct cause of the following exception:
initializer_1   |
initializer_1   | Traceback (most recent call last):
initializer_1   |   File "manage.py", line 11, in
initializer_1   |     execute_from_command_line(sys.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 401, in execute_from_command_line
initializer_1   |     utility.execute()
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 395, in execute
initializer_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 330, in run_from_argv
initializer_1   |     self.execute(*args, **cmd_options)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute
initializer_1   |     output = self.handle(*args, **options)
initializer_1   |   File "/app/dojo/management/commands/initialize_test_types.py", line 9, in handle
initializer_1   |     initialize_test_types()
initializer_1   |   File "/app/dojo/tools/factory.py", line 59, in initialize_test_types
initializer_1   |     test_type, created = Test_Type.objects.get_or_create(name=scan_type)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/manager.py", line 85, in manager_method
initializer_1   |     return getattr(self.get_queryset(), name)(*args, **kwargs)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 573, in get_or_create
initializer_1   |     return self.get(**kwargs), False
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 425, in get
initializer_1   |     num = len(clone)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 269, in len
initializer_1   |     self._fetch_all()
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 1308, in _fetch_all
initializer_1   |     self._result_cache = list(self._iterable_class(self))
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 53, in iter
initializer_1   |     results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql
initializer_1   |     cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 66, in execute
initializer_1   |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
initializer_1   |     return executor(sql, params, many, context)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 90, in exit
initializer_1   |     raise dj_exc_value.with_traceback(traceback) from exc_value
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
initializer_1   |     return self.cursor.execute(sql, params)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 73, in execute
initializer_1   |     return self.cursor.execute(query, args)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 206, in execute
initializer_1   |     res = self._query(query)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/cursors.py", line 319, in _query
initializer_1   |     db.query(q)
initializer_1   |   File "/usr/local/lib/python3.7/site-packages/MySQLdb/connections.py", line 259, in query
initializer_1   |     _mysql.connection.query(self, query)
initializer_1   | django.db.utils.OperationalError: (1054, "Unknown column 'dojo_test_type.active' in 'field list'")
defectdojo_initializer_1 exited with code 1
celerybeat_1    | [13/Sep/2021 11:09:42] INFO [celery.beat:285] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
celeryworker_1  | [13/Sep/2021 11:09:42] INFO [celery.worker.strategy:155] Task dojo.tasks.async_dupe_delete[b0fe3769-65f3-4b17-bf61-bfa5831a4b50] received
celeryworker_1  | [13/Sep/2021 11:09:42] INFO [celery.app.trace:131] Task dojo.tasks.async_dupe_delete[b0fe3769-65f3-4b17-bf61-bfa5831a4b50] succeeded in 0.0040963999927043915s: None
celerybeat_1    | [13/Sep/2021 11:10:42] INFO [celery.beat:285] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
celeryworker_1  | [13/Sep/2021 11:10:42] INFO [celery.worker.strategy:155] Task dojo.tasks.async_dupe_delete[6930080e-57df-4dab-881d-e440d4620f9e] received
celeryworker_1  | [13/Sep/2021 11:10:42] INFO [celery.app.trace:131] Task dojo.tasks.async_dupe_delete[6930080e-57df-4dab-881d-e440d4620f9e] succeeded in 0.004426013678312302s: None
celerybeat_1    | [13/Sep/2021 11:11:42] INFO [celery.beat:285] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
celeryworker_1  | [13/Sep/2021 11:11:42] INFO [celery.worker.strategy:155] Task dojo.tasks.async_dupe_delete[eb738db1-8e09-4512-a1a9-8f09c9c42cdb] received
celeryworker_1  | [13/Sep/2021 11:11:42] INFO [celery.app.trace:131] Task dojo.tasks.async_dupe_delete[eb738db1-8e09-4512-a1a9-8f09c9c42cdb] succeeded in 0.004256213083863258s: None
celerybeat_1    | [13/Sep/2021 11:12:42] INFO [celery.beat:285] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
celeryworker_1  | [13/Sep/2021 11:12:42] INFO [celery.worker.strategy:155] Task dojo.tasks.async_dupe_delete[f79b818e-5369-4733-aff8-b261e39243b3] received

Is that the log output when upgrading from 1.12.0? It doesn't look like it is because the branch_tag field in migration 0088 was only added in 1.15.0. Can you restore your 1.12.0 instance, upgrade, start the containers and capture the logs?

Yes, this is the log output when running docker compose up on top of 1.12.0 installation with 2.2.1 source code
IF you can tell us which file, and line needs to be commented in this case then it will be helpful.

Issue resolved after restore and upgrade


App should be resilient to invalid Ajax responses

Type of issue

[x] Bug
[ ] New feature
[ ] Improvement

Description
When any of the background HTTP requests receive an error, which could be either plain text or XML, the application breaks with a fatal error.
All HTTP requests should go through one client, designed to be resilient to unexpected responses, logging an error, and maybe letting the user know that something went wrong (without flooding the user with error messages on the screen though).
Ideally there should be a "debugging mode", which might be just the browser console logs, where one can see:

which request failed
why they failed
the impact of the failure, e.g. "unable to retrieve list of devices"

Fixed.


Fix remove getAllJhipsterConfig

Co-authored-by: Adil Abed<EMAIL_ADDRESS>

This PR fixes this problem

@atomfrede : what do you think about

keeping current master branch, compatible with generator-jhipster v6
going on new release of jhipster vuejs, with new features and bug fixes
start a develop branch for v7, so we can merge this one

Sounds good.

@atomfrede : sorry, but after thinking about it, it will be not necessary. I'm starting to integrate Vue.js to main generator-jhipster, as it's well deserved. I love too much Vue.js and it should be in main !

My roadmap will be:

integrate Vue.js to main generator-jhipster
put all CI and npm test
once it's stable enough, open a new ticket for Vue.js v3
maybe propose to have Vue.js as default option :D


Error on env vars

api:build: > Build error occurred
api:build: Error: Invalid environment variables
api:build: at onValidationError (/vercel/path0/node_modules/.pnpm/https://github.com/t3-oss+env-core@0.11.1_typescript@5.6.3_zod@3.23.8/node_modules/@t3-oss/env-core/dist/index.js:109:15)
api:build: at createEnv (/vercel/path0/node_modules/.pnpm/https://github.com/t3-oss+env-core@0.11.1_typescript@5.6.3_zod@3.23.8/node_modules/@t3-oss/env-core/dist/index.js:116:16)
api:build: at createEnv (/vercel/path0/node_modules/.pnpm/https://github.com/t3-oss+env-nextjs@0.11.1_typescript@5.6.3_zod@3.23.8/node_modules/@t3-oss/env-nextjs/dist/index.js:74:35)
api:build: at Object. (/vercel/path0/packages/env/index.ts:57:36)
api:build: at mod.compile (/vercel/path0/node_modules/.pnpm/next@15.0.2https://github.com/babel+core@7.26.0_@opentelemetry+api@1.9.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/next-config-ts/require-hook.js:67:33)
api:build: at require.extensions. (/vercel/path0/node_modules/.pnpm/next@15.0.2_@babel+core@7.26.0_@opentelemetry+api@1.9.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/next-config-ts/require-hook.js:69:20)
api:build:  ELIFECYCLE  Command failed with exit code 1.
api:build: ERROR: command finished with error: command (/vercel/path0/apps/api) /pnpm9/node_modules/.bin/pnpm run build exited (1)
api#build: command (/vercel/path0/apps/api) /pnpm9/node_modules/.bin/pnpm run build exited (1)
Tasks: 1 successful, 2 total
This error are happening to me, but all env var are filled, have some change I need to do on my side?

Hi @ktfth, which version of next-forge are you using? Check the package.json version field - I may have recently fixed this

@gt-codes can you tell me which version of next-forge you are using? Check the package.json version field.

I had similar issue , added latest to the init command
https://github.com/haydenbleasel/next-forge/compare/main...yamz8:next-forge:patch-1

I am having the same issue as well -- using version 2.12.8


Update project tt_um_wokwi_413387122850717697 (slackfarmer/tiny-tape-out-intro)

Update project tt_um_wokwi_413387122850717697 to commit slackfarmer/tiny-tape-out-intro@e378b3bfcf05635aeb95c664ce099f5795218b9f
Project title: And Gates that don't do much
Tiles: 1x1
Workflow: https://github.com/slackfarmer/tiny-tape-out-intro/actions/runs/11637703559

View in Wokwi

@slackfarmer the title says "and gates", but there are no "and gates" in the Wokwi project, you may want to check it out.


Add dbconfig.xml options to stop health warnings

As of version 7.1.4, JIRA will show a warning about the database not being configured as recommended. The health check states that the database config is missing settings for validation-query, pool-test-on-borrow and pool-test-while-idle:

For further explanation see the official docs: How can I resolve this?
This patch is based on code from that page and should eliminate the warnings.

Thanks for the update, saved me some time!


chore(release): 27.1.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.076%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1168

Relevant Lines:
1196

💛  - Coveralls

@ahnpnl @kulshekhar looks like this hasn't been published to npm yet - is that intentional?

i am waiting for #3124 :)


Added a shortcut to run tests from within a docker, #11019

Closes #11019

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:Plantain/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

@Plantain Thanks for your contribution! I added "Closes #11019" to your description, next time don't forget to add it it helps close the correct issue :)

LGTM
Ping @tianon

If we do this, I think we need to change the Makefile to actually use it so that we don't have the same list twice (which will inevitably get out of sync).
I'm on the fence on whether I like this, though.  Doesn't this make it less obvious to the user which bundles are actually executed?

whats wrong with ./hack/make.sh w no arguements... that does everything :D

I really am kinda a -1 on this because it is an extra level of abstraction I do not think we need, seeing as it could bring about this or the makefile to get out of sync with one another. I think the makefile is perfect for the level of abstraction we need.
and i agree with

Doesn't this make it less obvious to the user which bundles are actually executed?
if anything the user can run hack/make.sh with no arguments and it will run all the test which is basically this and we already have that
Sorry!


[Bug]: Not finish checkout, in the mobile device. It´s Showed two buttons checkout.

What happened?
On the line 3, the "disabled" status  concat with other status and cause fail:

class="checkout-btn btn btn-primary {{ $locationIsClosed ? 'disabled' : '' }} btn-block btn-lg"

Only orders on desktop pc are ok.
In my copy, i insert a space, to resolve. But, others fails occur.
The orders can be completed, in the mobile phone. But, not show about order info status for the client.
What did you expect to happen?
to show one button "checkout" and show the status after the finish order.
Version
3.0.x
What browser are you seeing the problem on?
Chrome, Microsoft Edge
Relevant log output
No response

hmm that shouldn't be happening as there are spaces around the blade opening and closing tags. But if you're seeing it in production then it should be simple to open a pull request with the required change?

In the DevTools of the browser is possible see the tags concated.

yet i not discovery the cause of the other fail who not let be show about order info status after tap in the button for send the order.

Not reproducible in the latest release. Please reopen this issue if it still occurs, with a set of reproducible steps.


Implement Snapshot Lifecycle Management APIs

This commit implements the Snapshot Lifecycle APIs in both the high level and low level clients.
Unit tests for URLs, integration tests for the SLM API flow.
The slm.get_lifecycle JSON spec is patched so that policy_id is a list and the Ids type is used to model multiple ids.

ported to master


Http Error 400

Hello!
I upgraded my titanium proxy from 3.0.362 -> 3.1.1397 but the function that used to work doesn't work well.
I don't know what's wrong.
Chrome occurs http 400 error.
I am using VS2022 and DotNet 4.5.1
Thank you for your help.

This is my code.
                proxyServer.BeforeRequest += OnRequest;
                proxyServer.BeforeResponse += OnResponse;
                proxyServer.ServerCertificateValidationCallback += OnCertificateValidation;
                proxyServer.ClientCertificateSelectionCallback += OnCertificateSelection;
                proxyServer.EnableTcpServerConnectionPrefetch = false;

                explicitEndPoint = new ExplicitProxyEndPoint(IPAddress.Any, 8000, true)
                {
                    //Use self-issued generic certificate on all https requests
                    //Optimizes performance by not creating a certificate for each https-enabled domain
                    //Useful when certificate trust is not required by proxy clients
                    //GenericCertificate = new X509Certificate2(Path.Combine(System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location), "rootCert.pfx"), "")
                };

                //Fired when a CONNECT request is received
                explicitEndPoint.BeforeTunnelConnectRequest += OnBeforeTunnelConnectRequest;

                proxyServer.AddEndPoint(explicitEndPoint);
                proxyServer.Start();

PS)
If i set UpstreamProxy, 400 error disappears and it works well.
What's the problem?
                    proxyServer.UpStreamHttpsProxy = new ExternalProxy();
                    proxyServer.UpStreamHttpsProxy.HostName = proxy_host;
                    proxyServer.UpStreamHttpsProxy.Port = proxy_port;
                    proxyServer.UpStreamHttpsProxy.UserName = proxy_user;
                    proxyServer.UpStreamHttpsProxy.Password = proxy_pass;


Would it be possible to support for source map support in Build.js?

https://github.com/gohugoio/hugo/blob/0256959a358bb26b983c9d9496862b0fdf387621/resources/resource_transformers/js/build.go#L154
Would it be possible to read a sourceMap true inside of the build options, or will the sourcemap output not get stored in the right place because the target is a path and not a directory?

There is already an open issue about this.


Strange References to .Handlebars files that DNE?

A couple of errors are thrown while starting the dev environment via Cygwin (might be thrown through other terminals as well), yet the server ends up running seemingly fine. Screenshot of errors attached and currently investigating.

Those errors are in starting webpack, and are what you get if you didn't
successfully run npm install, I think...
    -Tim Abbott

On Wed, Mar 23, 2016 at 9:03 PM, Ryan Fletcher<EMAIL_ADDRESS>wrote:

A couple of errors are thrown while starting the dev environment via
Cygwin (might be thrown through other terminals as well), yet the server
ends up running seemingly fine. Screenshot of errors attached and currently
investigating.
[image: run-dev error on windows]
https://cloud.githubusercontent.com/assets/6963222/14008100/aaabd00c-f153-11e5-9235-18dd16fc009b.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/zulip/zulip/issues/581

I think this should be resolved when we fix the symlink issue on windows, so closing this ticekt.


TLS refinements and tidy

Refinements to the code that manages the TLS certificates
Add admin user for SASL #44
Resolution of inconsistent whitespace and trimming
Update license declarations
Allow certificate passwords to be configured in values yaml
Allow specification of cluster id
Update pod management policy to ordered ready

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

Thanks for the PR @redp01 ! I see this PR conflicts with https://github.com/redpanda-data/helm-charts/pull/51 . What do you suggest for resolving this? I would normally focus on the first PR and merge, but wanted to get your thoughts.

@redp01 I think this PR can now be close since you are working on #117 (which includes some TLS updates). Let me know if that's the case.

Closing since this PR is out of date due to all the recent updates.


Allow ability to change a default index

Currently it seems with the splunk_metadata.csv you must iterate over an exhaustive list of vendor_product combinations to switch a default index to something else. It'd be nice to have a way to fully replace a default index with another option.
An example would be how there's a default index of osnix - if one would like to have all the data that would normally go to osnix to instead go to an index called foo, goal of this enhancement request would be to have that as an option via the metadata config files.

@mstopa-splunk wrote a small app conf to replace the default index with unique name sometime back as an example , same can be customised and used.
block parser app-dest-rewrite-index() {
    channel {
        rewrite {
            r_set_splunk_dest_update_v2(
                index("${.splunk.index}_unique-suffix")
            );
        };
    };
};

application app-dest-rewrite-index[sc4s-postfilter] {
    parser { app-dest-rewrite-index(); };
};


Framework support (Omi)

Is your feature request related to a problem? Please describe.
I'm trying to make the storybook work with the Omi framework : https://github.com/Tencent/omi
Describe the solution you'd like
I'd like a way to create a story by using my own rendering method.
To clarify and by taking the example of React; instead of returning a React element in the story:
storiesOf('MyComponent', module).add('default', () => <MyComponent/>)

I would to write something like this:
storiesOf('MyComponent', module).add('default', () => ReactDOM.render(<MyComponent />, document.getElementById('root')))

(maybe it can be an other mathods than add)
Describe alternatives you've considered
As the Omi framework generates web component I tried the @storybook/html package.
And It works:
storiesOf('MyComponent', module).add('default', () => '<my-component />')

But the Omi framework has a built-in store that you bind to your app by calling the render method:
render(<my-component />, '#root', store);

The store does not only contains data, it also contains methods that you can't pass by using the web component notation.
Are you able to assist bring the feature to reality?
Maybe we can create a wrapper like for react, angular...etc.
But as JS Framework are always growing and changing, is it really the right choice ?
I'am wondering if lower level methods exist that allow you to create your own wrapper.
Is it possible to have that kind of generic approach ?

Hey @tonai

(maybe it can be an other mathods than add)

Probably it can't. add() is a part of the SB core stories API

Maybe we can create a wrapper like for react, angular...etc.
But as JS Framework are always growing and changing, is it really the right choice ?
I'am wondering if lower level methods exist that allow you to create your own wrapper.
Is it possible to have that kind of generic approach ?

I am not sure I got what do you mean. Are you talking about adding the @storbyook/omisupport ?

Hi @igor-dv,
Sorry I was not clear enough (it was quite late friday :sleeping: ).

I am not sure I got what do you mean. Are you talking about adding the @storbyook/omisupport ?

In fact, I think this is the default choice.
So my answer is: yes maybe.
I haven't looked at the code of the core yet, so I'm just questionning here if there is a more generic way of adding a story than using the add method.
Because; maintaining all those versions of storybook must be quite hard.
And maybe adding Omi support is not worth it, because not a lot of people will use it...
And that also may be the case for an homemade framework.
So I don't know if adding the Omi framework support is a good choice.
But perhaps, adding the Omi framework support, is the only way of doing it... (for now)
In that case, and in your opinion, is it possible to create that kind of integration method ?
Thanks,

maintaining all those versions of storybook must be quite hard.

What versions 🤔
If you add it as a new framework to SB, you only need to support SB >= 4

I'm talking about maintaining all storybook variant:

@storybook/react
@storybook/angular
@storybook/vue
@storybook/ember
...etc.

I don't think it will be really hard to create the @storbyook/omi variant as it is very close to the @storybook/react one.
So we may duplicate it and adapt it to omi but that will be a lot of duplicated code won't it ?

Most of the common code is located in @storybook/core. The only difference if the rendering mechanism. Take a look at the recent ember addition: #4237


openblas: 0.3.10 -> 0.3.12

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/92458
Things done

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

[X] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

cc @FRidh

Please test/build numpy, scipy, and octave.

[X] numpy
[X] scipy
[ ] octave

octave seems to be fine too - this should however target staging due to the amount of rebuilds.

😢 that wasn't what I wanted

octave seems to be fine too - this should however target staging due to the amount of rebuilds.

done.

This needs a rebase.

This needs a rebase.

done

Apparently this wasn't pushed, or at least GitHub still shows a conflict.

for real this time

this breaks numpy for me, or at least now, it segfaults when running tests with 32 cores
store/gvkhgh813chlsvdsnxgwhv72xns08xcp-python3-3.8.6/bin/python3.8 -c 'import numpy; numpy.test("fast", verbose=10)'
builder for '/nix/store/s7azf4dald37gw9sa9shpvvpgldnjwgz-python3.8-numpy-1.19.1.drv' failed with exit code 139
error: build of '/nix/store/s7azf4dald37gw9sa9shpvvpgldnjwgz-python3.8-numpy-1.19.1.drv' failed
3b4cd4f4dacd7db4011e88d819a1ae5acc3f3aff is the first bad commit
commit 3b4cd4f4dacd7db4011e88d819a1ae5acc3f3aff
Author: Griffin Smith<EMAIL_ADDRESS>Date:   Mon Oct 26 13:08:56 2020 -0400

    openblas: 0.3.10 -> 0.3.12

 ...-optimised-aarch64-dgemm_beta-pending-fix.patch | 26 ----------------------
 .../libraries/science/math/openblas/default.nix    |  8 +------
 2 files changed, 1 insertion(+), 33 deletions(-)
 delete mode 100644 pkgs/development/libraries/science/math/openblas/0001-Disable-optimised-aarch64-dgemm_beta-pending-fix.patch
bisect run success
[11:22:55] jon@nixos ~/projects/nixpkgs ((3b4cd4f4dac...)|BISECTING)
$ git bisect run nix-build -A python3Packages.numpy

testing now if turning down the cores helps

can confirm that python3Packages.numpy builds fine on my machine

interesting, not sure why mine just segfaults

I'm not sure how this all works, but can we ask Hydra to build it for us?

I think ofborg was able to build this for us. Still, this shouldn't be happening :(

This PR did not bump the version attribute. I am a bit confused how all of you did run tests but not notice the hash mismatch.

Reverted in 4e29151910288bf478248d793f77d18226bf3f6d.

This PR did not bump the version attribute. I am a bit confused how all of you did run tests but not notice the hash mismatch.

Maybe it was lost in the rebase / force push? Does github record a history of pull requests somehow?

Version was there in https://github.com/NixOS/nixpkgs/commit/858e5dc235b70b6102cae2c9ddf0731522374514 before the force push.

:facepalm: sorry about that - that's what I get for trying to multitask as much as I was


Use openid/AppAuth-Android library with the IdentityServer4

I'm developing an ASP.Net MVC application and an Android app for my client. Back end service will be an ASP.Net Core API service.
And I want to use IdentityServer4 for authentication and authorization for my apps. I managed to configure the IdentityServer4 for the ASP.Net client and it's working great with the HybridAndClientCredentials grant type. My Android app is native and developed in JAVA, so I can't use "IdentityModel.OidcClient" library. So I'm looking for the openid's library AppAuth-Android , but I couldn't find any help or samples on this.
So how can I authorize my Android client with the AppAuth-Android library?
Can any one help me on this?
Any help is greatly appreciated.

AppAuth is not our library. It should work with IdentityServer4, but I haven't tried it myself yet.

Working fine with GrantTypes.Code and required PKCE, but not working with the GrantTypes.Hybrid.
Getting "Invalid grant type for client: authorization_code" error.

OK - then they probably don't support hybrid. Thanks!

That's OK. Thanks for the great framework.

@madhuteja I'm also trying to use IS4 with an android app. Have you achieved it? It would be really helpful if you could pass the client definition you used for android app.
How are you receiving tokens at client end ? via custom Uri scheme? What is the RedirectUri you defined in client definition?

@neerajyadav try this client configuration in IdSvr4
new Client                 {                     ClientId = "mobile",                     ClientName = "Mobile Client",                     AllowedGrantTypes = GrantTypes.Code,                     RedirectUris = { "com.yourcompany.yourapp://oidccallback" },                     AllowedScopes =                     {                         StandardScopes.OpenId.Name,                         StandardScopes.Profile.Name,                         StandardScopes.OfflineAccess.Name,                         "api1"                     }  }
How to implement in Android app? below link will help you.
https://codelabs.developers.google.com/codelabs/appauth-android-codelab/#0

@madhuteja Doesn't it require RequirePkce = true and AllowAccessTokensViaBrowser = true ?

@neerajyadav  Ahhh!, I forgot it. It only requires RequirePkce = true

@madhuteja I configured the client. When I pass openid or profile  in scopes from android client, it says invalid scope, however passing api1 works.
@leastprivilege does code client without secret be treated as public client? Also why does passing identity scopes from authorization code client give invalid_scope ?

you need to check the logs.

For those who are looking to configure android client with IdentityServer4, here is how your client configuration should look like in IS.
new Client
               {
                   ClientId = "client.android",
                   RequireClientSecret = false,
                   ClientName = "Android app client",
                   AllowedGrantTypes = GrantTypes.Code,
                   RequirePkce = true,
                   //AllowAccessTokensViaBrowser = true,
                   RequireConsent = false,

                   RedirectUris = { "com.yourcompany.app://oidccallback" },
                   AllowedScopes =
                   {
                       IdentityServerConstants.StandardScopes.OpenId,
                       IdentityServerConstants.StandardScopes.Profile,
                       IdentityServerConstants.StandardScopes.Email,
                       IdentityServerConstants.StandardScopes.Phone,
                       "api1"
                   },
                   AllowOfflineAccess = true
               }

Three main things you need to make sure, RequirePkce = true,  RequireClientSecret = false, AllowedGrantTypes = GrantTypes.Code . I wasted two days to figuring out RequireClientSecret should be false. With a lot of logging on production server I learned that.
This client is working fine with Android - AppAuth library. Also while sending scopes from android client, you need to make sure to include openid scope.
I will publish a sample repo for android client and IS both, as soon as I get free time.

I have made a simple using AppAuth-android with Identity Server 4 , check it here


Skipping device 'F-02F - 4.4.2' for 'app:debug': minSdkVersion [21] > deviceApiLevel [19]

Description
React Native app is not installing on tablet F-02F showing > Task :app:installDebug FAILED error but installed and running on Galaxy J7
Device Info
Build unsuccess on
Tablet Fujitsu Arrows Tab F-02F
Andriod Version 4.4.2
Build success on
Samsung Galaxy J7 2016
Andriod Version 8.1.0
React Native version:
System:
    OS: Windows 10 10.0.19041
    CPU: (4) x64 Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz
    Memory: 7.35 GB / 11.80 GB
  Binaries:
    Node: 12.18.3 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.1
      System Images: android-27 | Google APIs Intel x86 Atom
      Android NDK: Not Found
    Windows SDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>26763
    Visual Studio: Not Found
  Languages:
    Java: 1.8.0_211 - C:\Program Files\Java\jdk1.8.0_211\bin\javac.EXE
    Python: 3.8.5 - C:\Python38\python.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

Conclusion
I think I get this error because my Tab F-02F Andriod version is too old but I need to test my app on a physical Android tab device.
Expected Results
Running on my Fujitsu Arrows Tab F-02F and Samsung J7  device
build.gradle
buildscript {
    ext {
        buildToolsVersion = "29.0.2"
        minSdkVersion = 21
        compileSdkVersion = 29
        targetSdkVersion = 29
    }
    ...
}

Error
> Task :app:installDebug FAILED
Skipping device 'F-02F - 4.4.2' for 'app:debug': minSdkVersion [21] > deviceApiLevel [19]

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
488 actionable tasks: 2 executed, 486 up-to-date

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:installDebug'.
> Failed to install on any devices.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2m 12s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>android: `react-native run-android`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>android script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\chawki\AppData\Roaming\npm-cache\_logs\2020-08-29T09_51_27_289Z-debug.log

HI, @usama-asfar thx for the issue but I don't think this is a react-native bug.
The minSdkVersion of your app is API Level 21 ( Android 5.0 ). Because you are trying to install the app on a device with Andriod Version 4.4.2 Gradle will skip your device because it's lower than Android 5.0.
Do your app use native modules that are dependant on android API level >= 21? if not you can try to lower your minSdkVersion to API Level 19 ( Android 4.4)

Closing per @gedeagas comment. Thanks


index.js:12655 Uncaught TypeError: Cannot read properties of undefined (reading 'theme')

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce
打开
https://zb36pz.csb.app/

Environment
Info

f2
4.0.12

System
macos 12.1

Browser
Google Chrome 100.0.4896.60

index.js:12655 Uncaught TypeError: Cannot read properties of undefined (reading 'theme')
    at Chart.getStyle (index.js:12655:28)
    at new Chart (index.js:12598:24)
    at window.onload ((index):216:24)

请问怎么解决的

应该是文档的版本有问题,看另外一个版本的文档就好了,我忘了


Allow disabling of storage driver redirects

Storage drivers can implement a method called URLFor which can return a direct url for a given path. The functionality allows the registry to direct clients to download content directly from the backend storage. This is commonly used with s3 and cloudfront. Under certain conditions, such as when the registry is not local to the backend, these redirects can hurt performance and waste incoming bandwidth on pulls. This feature addition allows one to disable this feature, if required.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Closes #432. #739 must be merged before this PR.

LGTM.  Ping @aaronlehmann @dmp42

LGTM


refactor(connlib): unify peer storage

this is part of preparation for #
Build on top of #3743 (don't want to remove those changes from here because I still want to remove parking_lot from our dependencies)
This is basically ready, I'm just waiting to write some unit tests for the peer store before marking as ready.

@conectado perf flake (connection timeout) 😢

@conectado Fixed the conflicts for you :)


S3 Bucket Fails to Create Due to Missing ObjectOwnership

11:57:08 AM | CREATE_FAILED        | AWS::S3::Bucket                          | ServerAccessLogs48D8D751
Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting (Service: Amazon S3; Status Code: 400; Error Code: InvalidBucketAclWithO
bjectOwnership; Request ID: 1Y8MKVTBJ67WM4D9; S3 Extended Request ID: KWuGXVNqRylG2LSLGHg7JwdUEsalgRGAMBXqyWuGoOIX7sqd1r3shHW7K8ibGSXSZ8760I+t07dj3wcxb
Qnp2w==; Proxy: null)

 ❌  CdkEksInterAzVisibility failed: Error: The stack named CdkEksInterAzVisibility failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting (Service: Amazon S3; Status Code: 400; Error Code: InvalidBucketAclWithObjectOwnership; Request ID: 1Y8MKVTBJ67WM4D9; S3 Extended Request ID: KWuGXVNqRylG2LSLGHg7JwdUEsalgRGAMBXqyWuGoOIX7sqd1r3shHW7K8ibGSXSZ8760I+t07dj3wcxbQnp2w==; Proxy: null)
    at FullCloudFormationDeployment.monitorDeployment (/Users/tolub/Documents/DevEnv/amazon-eks-inter-az-traffic-visibility/node_modules/aws-cdk/lib/index.js:380:10236)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async deployStack2 (/Users/tolub/Documents/DevEnv/amazon-eks-inter-az-traffic-visibility/node_modules/aws-cdk/lib/index.js:383:145458)
    at async /Users/tolub/Documents/DevEnv/amazon-eks-inter-az-traffic-visibility/node_modules/aws-cdk/lib/index.js:383:128776
    at async run (/Users/tolub/Documents/DevEnv/amazon-eks-inter-az-traffic-visibility/node_modules/aws-cdk/lib/index.js:383:126782)

The related PR was merged, closing this issue.


Connection error in Vivaldi on Fedora 25

Hello,
as first, a great thanks for this extension.
I've just a small problem. I tried to install it. As Vivaldi is optimized for Chrome and using the same directory for NativeMessaging i choose that option.
I installed the extension on both ways (Webstore & Local)
Can somebody, how i produce useful logs (Inspector view just displays connection errors) or give me some advice?
Greetings.

Hey @pbeckmann,
I'm not entirely sure if this will be compatible but if they share most of the Chrome API then it certainly shouldn't be too hard. I'll try to take a look at providing Vivaldi compatibility this Friday!

Hey,
Thanks for your Response.
Vivaldi uses the webkit engine to Display the Websites and https://help.vivaldi.com/article/extensions/ says that users should install Extensions from the Chrome WebStore.
Thats why i think it could be a Problem with the NativeMessaging Part.
Greetings
P.S.: Sry for the bad english. I can't Change the autocorrection of my browser atm.

Hey,
so i found the solution for Linux.
The Native Messaging File must be at ~/.config/vivaldi/NativeMessagingHosts/
If you want i push it as a Pull Request to the install.sh.
Do you have some contributors, who can test the paths for Windows (i could do it in a VM tomorrow) and Mac?
Greetings

Hi @pbeckmann,
Great news, nice find! So with the native messaging host installed in the right place, it works as expected? That's awesome. A pull request would be great, but if not I'll probably get to it on Friday.
I have a Windows machine available to run tests but have yet to look at it. #25 is quite an active issue on adding Windows support.

Could this also solve issues with #28?

So i've just tested it. If i'm just remove the execution bit from the binary, i got "Error talking to pass". And with the executable bit, the autofill works as expected.
At the moment i'm looking for the systemwide installation for the NativeMessagingHost. When i found it, i'll add a push request with "Vivaldi on Linux" as an option.
Another bug (but for this i'll file a new issue) is, that i have some graphical bugs with the extension. (But i have this with all chrome extensions in vivaldi)
So No i do not think, that its something to help with #28

Same issue here, copying the files from .config/chromium to .config/vivaldi solved it.


fix: pass only relavent props to each field

Looks like we were passing the field props directly to the field component which end up setting extra props like initialError, errorId or descriptionId on the element as well.
<input id="edit-profile-name" placeholder=" " name="name" initialerror="[object Object]" form="edit-profile" errorid="edit-profile-name-error" descriptionid="edit-profile-name-description" class="h-14 w-full rounded-lg border border-night-400 bg-night-700 px-4 pt-4 text-body-xs caret-white outline-none focus:border-accent-purple disabled:bg-night-400" value="Kody">

This PR restrict what we are passing by using the conform helper.

I'd be happy to create a PR for this @edmundhung

Hi @andrecasal, thanks for checking

I would leave redirectTo as is since there is no validation needed.
It looks like Kent has fixed the username setup already on the latest main branch
It is indeed missed. Feel free to create a PR. Thanks!

Turns out Kent had already fixed both 1. and 2.
Here's a PR for the app/routes/_auth+/signup.tsx.


Testing mutation component

I have a pie chart with a legend. When a legend label is clicked the corresponding pie slice gets a highlight color, and so does the legend label itself. This is the test for my Legend.tsx component.
I am getting the following error:
Missing field setActiveChart in {
      "activeChart": {
        "activeSegment": "Journal article",
        "type": "ResearchOutput"
      }
    }

Here is my test file:
import { ApolloClient } from 'apollo-client'
import { MockLink } from 'apollo-link-mock'
import React from 'react'
import { ApolloProvider } from 'react-apollo-hooks'
import { fireEvent, render } from 'react-testing-library'
import Legend from './'

const SET_ACTIVE_CHART = gql`
  mutation setActiveChart($activeSegment: String!, $type: String!) {
    setActiveChart(activeSegment: $activeSegment, type: $type) @client {
      activeSegment
    }
  }

const mocks = [
  {
    request: {
      query: SET_ACTIVE_CHART,
      variables: {
        activeSegment: 'Journal article',
        type: 'ResearchOutput',
      },
    },
    result: {
      data: {
        activeChart: {
          activeSegment: 'Journal article',
          type: 'ResearchOutput',
        },
      },
    },
  },
]
const data = [
  {
    name: 'Journal article',
    value: 75,
    colour: '#b2d5e0',
    percentage: 75,
  },
  {
    name: 'Books',
    value: 5,
    colour: '#99c7d5',
    percentage: 10,
  },
]
// afterEach(cleanup)

const createClient = clientmocks => {
  return new ApolloClient({
    cache: new InMemoryCache(),
    link: new MockLink(clientmocks),
  })
}

const waitForNextTick = () => new Promise(resolve => setTimeout(resolve))

describe('Legend: ResearchOutputByType', () => {
  const mockFunction = jest.fn()
  const client = createClient(mocks)
  const utils = render(
    <ApolloProvider client={client}>
      <Legend data={data} activeSegments={[]} setHoveredSegment={mockFunction} />
    </ApolloProvider>
  )
  test('Should render legend items', () => {
    expect(utils.container.textContent).toContain('Journal article')
  })
  test('Should update legend badge color on click', async () => {
    const el = utils.container.querySelector('#pie-legend-badge-0')
    const event = fireEvent.click(el)
    console.log('Badge click success:', event)
    await waitForNextTick()
    expect(true).toBe(false)
  })
})```

@mo-tottenham your result part of the mock seems incorrect. Please try to replace:
    result: {
      data: {
        activeChart: {

with
    result: {
      data: {
        setActiveChart: {

@trojanowski Ah yes I thought the result should match what the mutation returns which in my case was activeChart.
I've applied your suggested changes but then got an error about missing field __typename. So then I changed my mock mutation to this:
const SET_ACTIVE_CHART = gql`
  mutation setActiveChart($activeSegment: String!, $type: String!) {
    setActiveChart(activeSegment: $activeSegment, type: $type) @client {
      activeSegment
      type
    }
  }`

const mocks = [
  {
    request: {
      query: SET_ACTIVE_CHART,
      variables: {
        __typename: 'ActiveChart',
        activeSegment: 'Journal article',
        type: 'ResearchOutput',
      },
    },
    result: {
      data: {
        setActiveChart: {
          activeSegment: 'Journal article',
          type: 'ResearchOutput',
          __typename: 'ActiveChart',
        },
      },
    },
  },
]

Which gives me the following error:
No more mocked responses for the query: mutation setActiveChart($activeSegment: String!, $type: String!) {
      setActiveChart(activeSegment: $activeSegment, type: $type) @client {
        activeSegment
        __typename
      }
    }
    , variables: {"activeSegment":"Journal article","type":"ResearchOutput"}

Note: I also think the fact I am using the client directive as this mutation manages local state, could be an issue.

I also think the fact I am using the client directive as this mutation manages local state, could be an issue.

@mo-tottenham Yes, it could be the reason. Do you use Apollo Client 2.5? If so I think you should add your resolvers to the ApolloClient options.


Add new coverage to Telemetry Inventory Test

Pull Request Functional Test Report for #2395 / b25e604c07f22a5bee02b59e5403b9c42c71cdb3
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

gNMI-1.4: Telemetry: Inventory
eb606dea
Log

Cisco 8000E

gNMI-1.4: Telemetry: Inventory
d7290719
Log

Cisco XRd

gNMI-1.4: Telemetry: Inventory
ad81c1d2
Log

Juniper cPTX

gNMI-1.4: Telemetry: Inventory
6928e617
Log

Juniper ncPTX

gNMI-1.4: Telemetry: Inventory
63e6a4f1
Log

Nokia SR Linux

gNMI-1.4: Telemetry: Inventory
5749809c
Log

Openconfig Lemming

gNMI-1.4: Telemetry: Inventory
851f164e
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

gNMI-1.4: Telemetry: Inventory

Cisco 8808

gNMI-1.4: Telemetry: Inventory

Juniper PTX10008

gNMI-1.4: Telemetry: Inventory

Nokia 7250 IXR-10e

gNMI-1.4: Telemetry: Inventory

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.704%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1541

Relevant Lines:
3164

💛  - Coveralls


Fixed Issue #1755

Pull request checklist

[x] All tests pass. Demo project builds and runs.
[x] I have resolved any merge conflicts.
[x] I have followed the coding style, and reviewed the contributing guidelines. Confirmation: 💪😎👊

This fixes issue
#1755
What's in this pull request?
There was an extra reference to share.png in the xibs
Removed them and the demo project builds and run fine
without the pesky error message

@asifmohd This is good if Jesse's intention is to remove. I'm not sure. @jessesquires

thanks! 👍 🎉


Working with Frame parameters for Replica feature fusion

Thank you for this great repository! The documentation is very clear too.
I have a recording of a space with no semantic labels. So I am using the Replica dataset processing files. I was able to preprocess the 3D ply file. For 2D preprocessing, I have all the frames, but it is also asking me for a trajectory.txt file. What is this file supposed to contain? The app I used for getting the data did not provide this file. Instead, for each frame, I get a JSON whose structure is like this:
{
  "intrinsics" : [
    1327.18115234375,    0,<PHONE_NUMBER>2890625,     0,     1327.18115234375,<PHONE_NUMBER>75,
    0,     0,     1
  ],
  "averageAngularVelocity" : 0.83692288398742676,
  "motionQuality" : 0.76087915897369385,
  "frame_index" : 91,
  "exposureDuration" : 0.01666666753590107,
  "averageVelocity" : 0.41746380925178528,
  "cameraPoseARFrame" : [
    -0.35722801089286804,     0.7659410834312439,     -0.53453010320663452,     0.63373279571533203,
    -0.8567434549331665,     -0.040781203657388687,     0.51412779092788696,    0.10553276538848877,
    0.37199276685714722,     0.64161604642868042,     0.67078316211700439,     -1.9972312450408936,
    0,     0,     0,     1
  ],
  "cameraGrain" : 0,
  "time" : 98064.684786291691,
  "projectionMatrix" : [
    1.3824803829193115,     0,     -0.00012767314910888672,     0,     0,     1.8433071374893188,
    0.00086534023284912109,     0,     0,     0,     -0.9999997615814209,     -0.00099999981466680765,
    0,     0,     -1,     0
  ]
}

Which parameter is supposed to be used out of these to get the trajectory.txt? Thanks in advance!

Hi @pratikratadiya
You can use the script provided in NICE-SLAM to download the unprocessed Replica data, which contains the traj.txt file. You need to find a way to adjust your .json so that the 2D Replica data processing code is working.

Hi, thanks for responding. I was able to get this running by combining all the "cameraPoseARFrame" attributes. I got the 3D features too, and now when I run the inference script (I am using pretrained model, not distilling my own), I get out of memory error.
I have 4 x 16 GB GPU, but did not modify the code so I think it is only able to use a single GPU 0. How can I modify the config/replica/ours_openseg_pretrained.yaml file to be able to use multiple smaller GPUs for the predictions?

Hi @pengsongyou , any advice on how I can use a multi-GPU setup (4x16GB) for running the eval.sh script? Is this possible? If so, What things do I need to change?

Hi @pratikratadiya I actually have never tried to do inference with multiple GPUs. Maybe you can check how we do the multi-GPU training in the distill.py file?


STDIN for Terminal

Can't write to stdin using the terminal emulator

How is difficult to implement it?
P.S: We use this terminal in PlatformIO IDE beta but people request STDIN :(
Thanks in advance!

Hello, thanks for your interest.

How is difficult to implement it?

I'm not really sure. Several CLIs require "real-time" input, so my idea was to capture keydown events in the whole terminal simulator (while it has a child process running) and write the inputted character to the child process' stdin stream.
I'm quite time constrained at the moment and I'm not sure how well that idea would work out in practice, but I'm open to pull requests in case anyone wants to give it a try.


Errors running on Python 3.11

Installing with the commands below (with protobuf > 3.20 it throws even more errors).
pip install pycrunch-trace
pip install protobuf==3.20

Running example code:
from pycrunch_trace.client.api import Trace

tracer = Trace()
tracer.start('recording_name')

def some_code():
    print('hi')

some_code()

tracer.stop()

Error
\Cython\Compiler\Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: \pycrunch_trace\events\file_contents_in_protobuf.pyx
  tree = Parsing.p_module(s, pxd, full_module_name)

Error compiling Cython file:
------------------------------------------------------------
...
    cdef NativeStackFrame parent
    cdef NativeExecutionCursor cursor
    cdef int id

cdef class NativeCodeEvent:
    cpdef str event_name
          ^
------------------------------------------------------------

\pycrunch_trace\native\native_models.pxd:15:10: Variables cannot be declared with 'cpdef'. Use 'cdef' instead.
Traceback (most recent call last):
  File "\pyximport\_pyximport3.py", line 314, in create_module
    so_path = build_module(spec.name, pyxfilename=spec.origin, pyxbuild_dir=self._pyxbuild_dir,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "\pyximport\_pyximport3.py", line 197, in build_module
    so_path = pyxbuild.pyx_to_dll(pyxfilename, extension_mod,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "\pyximport\pyxbuild.py", line 103, in pyx_to_dll
    dist.run_commands()
  File "\setuptools\_distutils\dist.py", line 969, in run_commands
    self.run_command(cmd)
  File "\setuptools\dist.py", line 976, in run_command
    super().run_command(command)
  File "\setuptools\_distutils\dist.py", line 988, in run_command
    cmd_obj.run()
  File "\setuptools\_distutils\command\build_ext.py", line 359, in run
    self.build_extensions()
  File "\setuptools\_distutils\command\build_ext.py", line 479, in build_extensions
    self._build_extensions_serial()
  File "\setuptools\_distutils\command\build_ext.py", line 505, in _build_extensions_serial
    self.build_extension(ext)
  File "\Cython\Distutils\build_ext.py", line 130, in build_extension
    new_ext = cythonize(
              ^^^^^^^^^^
  File "\Cython\Build\Dependencies.py", line 1154, in cythonize
    cythonize_one(*args)
  File "\Cython\Build\Dependencies.py", line 1321, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: \pycrunch_trace\events\file_contents_in_protobuf.pyx

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "\pyximport\_pyximport3.py", line 336, in exec_module
    return super().exec_module(module)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap_external>", line 1241, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "native_write_strategy.pyx", line 8, in init pycrunch_trace.client.networking.strategies.native_write_strategy
  File "\pyximport\_pyximport3.py", line 332, in create_module
    raise exc.with_traceback(tb)
  File "\pyximport\_pyximport3.py", line 314, in create_module
    so_path = build_module(spec.name, pyxfilename=spec.origin, pyxbuild_dir=self._pyxbuild_dir,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "\pyximport\_pyximport3.py", line 197, in build_module
    so_path = pyxbuild.pyx_to_dll(pyxfilename, extension_mod,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "\pyximport\pyxbuild.py", line 103, in pyx_to_dll
    dist.run_commands()
  File "\setuptools\_distutils\dist.py", line 969, in run_commands
    self.run_command(cmd)
  File "\setuptools\dist.py", line 976, in run_command
    super().run_command(command)
  File "\setuptools\_distutils\dist.py", line 988, in run_command
    cmd_obj.run()
  File "\setuptools\_distutils\command\build_ext.py", line 359, in run
    self.build_extensions()
  File "\setuptools\_distutils\command\build_ext.py", line 479, in build_extensions
    self._build_extensions_serial()
  File "\setuptools\_distutils\command\build_ext.py", line 505, in _build_extensions_serial
    self.build_extension(ext)
  File "\Cython\Distutils\build_ext.py", line 130, in build_extension
    new_ext = cythonize(
              ^^^^^^^^^^
  File "\Cython\Build\Dependencies.py", line 1154, in cythonize
    cythonize_one(*args)
  File "\Cython\Build\Dependencies.py", line 1321, in cythonize_one
    raise CompileError(None, pyx_file)
ImportError: Building module pycrunch_trace.events.file_contents_in_protobuf failed: ['Cython.Compiler.Errors.CompileError: pycrunch_trace\\events\\file_contents_in_protobuf.pyx\n']

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "\test.py", line 1, in <module>
    from pycrunch_trace.client.api import Trace
  File "\pycrunch_trace\client\api\__init__.py", line 1, in <module>
    from .trace_decorator import trace
  File "\pycrunch_trace\client\api\trace_decorator.py", line 2, in <module>
    from pycrunch_trace.client.api.trace import Trace
  File "\pycrunch_trace\client\api\trace.py", line 8, in <module>
    from pycrunch_trace.client.networking import event_queue
  File "\pycrunch_trace\client\networking\__init__.py", line 1, in <module>
    from .ClientOutgoingQueueThread import event_queue
  File "\pycrunch_trace\client\networking\ClientOutgoingQueueThread.py", line 13, in <module>
    from pycrunch_trace.client.networking.strategies.native_write_strategy import NativeLocalRecordingStrategy
  File "\pyximport\_pyximport3.py", line 340, in exec_module
    raise ImportError("Executing module %s failed %s" % (
ImportError: Executing module \.pyxbld\lib.win-amd64-cpython-311\pycrunch_trace\client\networking\strategies\native_write_strategy.cp311-win_amd64.pyd failed ["ImportError: Building module pycrunch_trace.events.file_contents_in_protobuf failed: ['Cython.Compiler.Errors.CompileError: pycrunch_trace\\\\events\\\\file_contents_in_protobuf.pyx\\n']\n"]

For anyone trying to make it work - can confirm that I got it working by using Python 3.10 and pip install protobuf==3.11.3 Cython==0.29.27 (latests version of python and cython based for the current last commit 2d047a216393ab9d983629dfbc0dc862c929086f, protobuf version comes from requirements.txt)


reggen spits out a warning about the extra key "hier_path" in ALERT_HANDLER

The extra key was added by PR #2486 (commit 0768219). Looking at this conversation, @weicaiyang originally added it to the list of optional keys in reggen, but then had to remove it again.
Can we just add it back in? I've attached a patch that fixes up the obvious breakage, but I don't want to do a PR without understanding how this is all supposed to work. Oh, and I had to rename the file .txt because apparently GitHub doesn't support patches (huh?!).
0001-Add-hier_path-to-list-of-optional-keys-in-validate.txt
@weicaiyang, @eunchan

I was not aware of the warning. Looks like it makes sense to add it. Thanks for fixing this.
@eunchan WDYT?

Yup. I agree adding it to optional field.

On Oct 7, 2020, at 10:29 AM, weicaiyang<EMAIL_ADDRESS>wrote:
I was not aware of the warning. Looks like it makes sense to add it. Thanks for fixing this.
@eunchan https://github.com/eunchan WDYT?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/issues/3732#issuecomment-705084900, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3ROAOOZRRYXCGQJBPTSJSQRJANCNFSM4SHPTZEA.


State template

By templating the Prior over the State, we can avoid having to serialize and de-serialize to and from proto every time we sample with a SemiConjugateUpdater.
In a benchmark one-dimensional example with 2 clusters, this gives a 30% performance improvement. It is likely that the improvement will eventually be irrelevant in more challenging scenarios with multivariate data.
At the moment, only the NNIGHierarchy has been changed.

All the classes have been ported


Changing the default rotation on the Rotate control is very difficult

When initializing a map that is not oriented north (i.e. a map rotated 180 degrees), the reset rotation control is very difficult to reorient along side it. The only way to do so currently is to redefine the render and resetNorth functions entirely at the time of the Rotate control's creation.
Can we add a parameter to the Rotate control that does one or both of the following?:

Add a parameter for the default orientation. Rename "resetNorth" to something more broad, like "resetRotation" and modify the reset and render functions to use the new default rather than 0
Add a boolean to the control (or a function) that tells it to set the default to map's current rotation.

https://github.com/openlayers/openlayers/blob/main/src/ol/control/Rotate.js#L133

See also https://github.com/openlayers/openlayers/issues/11080

@EvertEt I'm debating opening a PR for this myself, as it seems like a pretty easy change. I hadn't considered that the arrow's default should be adjustable as well to accommodate. That would look really clean. Maybe that could be set to a boolean param like "realignArrow"?

I think all that would be needed is a defaultRotation option in the constructor and a setDefaultRotation to update it, both taking radians.  https://codesandbox.io/s/simple-forked-tzhm0  The value could also be used to control autohide.  However, the view would then need a similar option and method so constrainRotation snaps to the same default (or fractions offset from it) instead from 0 - that might be a bigger change.


LMDE 5, trouble finding it

This is really cool! Probably user error (linux newbie but learning), but there were enough inconsistencies with the instructions and my distro (LMDE - Debian based Mint) in case anyone else is struggling. Doesn't seem to be listed under installed applications, or available as an applet, or a Desklet.
Place the chatgpt-gnome-desktop@chat-gpt-gnome-desktop folder in ~/.local/share/gnome-shell/extensions/
I do not have that destination folder, I put it in /usr/share/gnome-shell/extensions instead
I did restart Gnome a few times
I'm running x11, but Gnome Shell 3.38.6
When trying to run sudo apt install libgtk-4-dev I get Unable to locate package - seems like updating to 42 would be a major change that I'm not in a place to do, but not sure if that would stop it from showing up somewhere.
Thanks!

Do not touch usr/share/...
Make sure you have gnome-extensions installed.
You can enable the extension in the gnome-extensions app.
Once installed, put the chatgpt-gnome-desktop@chat-gpt-gnome-desktop folder in ~/.local/share/gnome-shell/extensions/
Then restart Gnome Desktop Enviorment or Log out and log back in

Are you even using the Gnome DE?

@Nam-Ram Are you even using the Gnome DE?

Hmm, I'm not sure.
$ echo $XDG_CURRENT_DESKTOP returns X-Cinnamon, which seems to be a fork of Gnome3.

X-Cinnamon != Gnome.

I have not tested how the extension works on forks of Gnome. In the extensions early development stage, Gnome 42 is used with focus on bringing compatibility to Gnome 43.


iOS: Articles getting closed after refresh

When the Refresh to Clear Read Articles option is enabled, you get kicked out of an article if you opened it while refreshing:

Does it happen when you have the unread filter turned off?

No, articles are only closed if something makes them disappear from the article list. It does not happen if you mark the article as unread before refreshing finishes.
The same happens if an article marked as read is selected and you turn on the unread filter.

This behavior has been changed and will be in the next release.


'ceylon test' should succeed if there are no tests

Reported by @tomekpiotrowski on gitter, running ceylon test on a module that has no tests should succeed.

Per the original report, other build tools expect test runs to succeed when there are no tests
In case of misconfiguration, it should be pretty obvious to someone that none of their tests are being run without the help of having ceylon test result in error

@tomekpiotrowski this is fixed and should be available on the next 1.3.3-SNAPSHOT build.
I didn't try it using the maven plugin, so please test if you want to be 100% sure this fixes your problem.

@jvasileff Thanks! This looks like it should work. I'll try to test soon.


Go Style Guide — Go Tip Episodes & Unit Testing Practices

Are there any plans to release the Go Tip Episodes and Unit Testing Practices found under External References in the Google Go Style Guide? Many parts of the style guide reference the Go Tips which are unavailable at this time.

Publishing the Go Tip episodes has been on the mind of the Go Tip editors (and to an extent that of the Go Style maintainers).  It's hard to know when any of this would land, though.  It takes quite a bit of work to externally publish material (cf. Testing on the Toilet).  The Go Tip material would land in a place outside of the style material here.
The story for the Unit Testing Practices material is similar but involves a different audience.
Overall, I sympathize a lot with what you are asking for.


how increase speed of transfering ?

I start with 20 plots the first 2-3 plots it does without waiting after the 3 plot it waits until it is transferred to the hdd at the beginning everything went well why does this happen to me now
Or how i increase speed of transferring maybe  the queue of transferring is full but i dont know how can some one help me please

Yeah - my copies via USB 3.0 are taking an hour.

then there is something wrong with your USB3.. i can clear >100mb/s on mine.
make sure you don't have any other usb 2 crap plugged into your usb string. and check the internal routing of your "USB3" is not tied to some other bottle neck...
or go optical...... it's not that expensive, i just spent another $40 on a second hand 20GB/s intel card, which bottle necks at the physical drives rather than the network.

Are you on Linux and drives formatted as NTFS?


Add possibility to set a Drawable to searchItem

Currently it is only possible to add a ressource reference.

Ok. I will add it.