Can't apply migrations on PostgreSQL

While trying to update the Docker-Environment for version 3, I stumbled upon the problem, that I can't apply the migrations to a fresh postres-instance:
postgres_1_b93c2e922be2 | Creating replication user: repluser
postgres_1_b93c2e922be2 | Starting PostgreSQL 9.6...
postgres_1_b93c2e922be2 | LOG:  database system was shut down at 2018-11-06 10:54:57 UTC
postgres_1_b93c2e922be2 | LOG:  MultiXact member wraparound protections are now enabled
postgres_1_b93c2e922be2 | LOG:  autovacuum launcher started
postgres_1_b93c2e922be2 | LOG:  database system is ready to accept connections
postgres_1_b93c2e922be2 | ERROR:  relation "motions_workflow" does not exist at character 101
postgres_1_b93c2e922be2 | STATEMENT:  SELECT "motions_workflow"."id", "motions_workflow"."name", "motions_workflow"."first_state_id" FROM "motions_workflow"
server_1_4d493c88160b | Traceback (most recent call last):
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
server_1_4d493c88160b |     return self.cursor.execute(sql, params)
server_1_4d493c88160b | psycopg2.ProgrammingError: relation "motions_workflow" does not exist
server_1_4d493c88160b | LINE 1: ...."name", "motions_workflow"."first_state_id" FROM "motions_w...
server_1_4d493c88160b |                                                              ^
server_1_4d493c88160b |
server_1_4d493c88160b |
server_1_4d493c88160b | The above exception was the direct cause of the following exception:
server_1_4d493c88160b |
server_1_4d493c88160b | Traceback (most recent call last):
server_1_4d493c88160b |   File "manage.py", line 11, in <module>
server_1_4d493c88160b |     exit(main())
server_1_4d493c88160b |   File "/app/openslides/__main__.py", line 41, in main
server_1_4d493c88160b |     execute_from_command_line(sys.argv)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
server_1_4d493c88160b |     utility.execute()
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 357, in execute
server_1_4d493c88160b |     django.setup()
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/__init__.py", line 24, in setup
server_1_4d493c88160b |     apps.populate(settings.INSTALLED_APPS)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/apps/registry.py", line 120, in populate
server_1_4d493c88160b |     app_config.ready()
server_1_4d493c88160b |   File "/app/openslides/core/apps.py", line 55, in ready
server_1_4d493c88160b |     set_constants(get_constants_from_apps())
server_1_4d493c88160b |   File "/app/openslides/utils/constants.py", line 16, in get_constants_from_apps
server_1_4d493c88160b |     out.update(get_angular_constants())
server_1_4d493c88160b |   File "/app/openslides/core/apps.py", line 147, in get_angular_constants
server_1_4d493c88160b |     config_groups[-1]['subgroups'][-1]['items'].append(config_variable.data)
server_1_4d493c88160b |   File "/app/openslides/core/config.py", line 305, in data
server_1_4d493c88160b |     choices=self.choices() if callable(self.choices) else self.choices
server_1_4d493c88160b |   File "/app/openslides/motions/config_variables.py", line 14, in get_workflow_choices
server_1_4d493c88160b |     for workflow in Workflow.objects.all()]
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 268, in __iter__
server_1_4d493c88160b |     self._fetch_all()
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 1186, in _fetch_all
server_1_4d493c88160b |     self._result_cache = list(self._iterable_class(self))
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 54, in __iter__
server_1_4d493c88160b |     results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1065, in execute_sql
server_1_4d493c88160b |     cursor.execute(sql, params)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 100, in execute
server_1_4d493c88160b |     return super().execute(sql, params)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 68, in execute
server_1_4d493c88160b |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers
server_1_4d493c88160b |     return executor(sql, params, many, context)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
server_1_4d493c88160b |     return self.cursor.execute(sql, params)
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 89, in __exit__
server_1_4d493c88160b |     raise dj_exc_value.with_traceback(traceback) from exc_value
server_1_4d493c88160b |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
server_1_4d493c88160b |     return self.cursor.execute(sql, params)
server_1_4d493c88160b | django.db.utils.ProgrammingError: relation "motions_workflow" does not exist
server_1_4d493c88160b | LINE 1: ...."name", "motions_workflow"."first_state_id" FROM "motions_w...

It can be reproduced with a local setup, so it isn't a docker-issue.

You can recreate the issue by starting up a postres instance. e.g via:
docker run --name os-postgres -p 5432:5432 -e POSTGRES_PASSWORD=openslides -e POSTGRES_USER=openslides postgres

and change the db-part in the settings to:
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql',
        'NAME': 'openslides',
        'USER': 'openslides',
        'PASSWORD': 'openslides',
        'HOST': '<IP_ADDRESS>',
        'PORT': '5432',
    }
}

The log from postgres will tell you:
PostgreSQL init process complete; ready for start up.
2018-11-06 11:18:12.430 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2018-11-06 11:18:12.430 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2018-11-06 11:18:12.436 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2018-11-06 11:18:12.471 UTC [62] LOG:  database system was shut down at 2018-11-06 11:18:12 UTC
2018-11-06 11:18:12.478 UTC [1] LOG:  database system is ready to accept connections
2018-11-06 11:18:18.851 UTC [69] ERROR:  relation "motions_workflow" does not exist at character 101
2018-11-06 11:18:18.851 UTC [69] STATEMENT:  SELECT "motions_workflow"."id", "motions_workflow"."name", "motions_workflow"."first_state_id" FROM "motions_workflow"

The python manage.py migrate will tell you:
% python manage.py migrate
Traceback (most recent call last):
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
psycopg2.ProgrammingError: relation "motions_workflow" does not exist
LINE 1: ...."name", "motions_workflow"."first_state_id" FROM "motions_w...
                                                             ^

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

Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    exit(main())
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/openslides/__main__.py", line 41, in main
    execute_from_command_line(sys.argv)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/core/management/__init__.py", line 357, in execute
    django.setup()
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/apps/registry.py", line 120, in populate
    app_config.ready()
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/openslides/core/apps.py", line 55, in ready
    set_constants(get_constants_from_apps())
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/openslides/utils/constants.py", line 16, in get_constants_from_apps
    out.update(get_angular_constants())
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/openslides/core/apps.py", line 147, in get_angular_constants
    config_groups[-1]['subgroups'][-1]['items'].append(config_variable.data)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/openslides/core/config.py", line 305, in data
    choices=self.choices() if callable(self.choices) else self.choices
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/openslides/motions/config_variables.py", line 14, in get_workflow_choices
    for workflow in Workflow.objects.all()]
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/models/query.py", line 268, in __iter__
    self._fetch_all()
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/models/query.py", line 1186, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/models/query.py", line 54, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1065, in execute_sql
    cursor.execute(sql, params)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/backends/utils.py", line 100, in execute
    return super().execute(sql, params)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/backends/utils.py", line 68, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/jochen/VCS/GIT/jsaalfeld/OpenSlides/.virtualenv/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "motions_workflow" does not exist
LINE 1: ...."name", "motions_workflow"."first_state_id" FROM "motions_w...
                                                             ^

Since #3988 is merged. This is fixed now.


Suggestions "limit" settings

Hi,
There is a problem when the suggestions size equals to the limit settings, no suggestion appears.
After debugging, I noticed that slicing an array with arguments (0, 0) is maybe the problem (@see typeahead.jquery.js line 811 @version 0.11.1)

Hi, I can confirm this issue. It makes my autocomplete quite unreliable. Please take a look at this (expected) results table.

Also discovered this problem today. The table illustrates the exact problem we were having.

I also think there is a problem with the suggestion limit. I'm doing some tests. On a prefetched table of 3 items (json), the typeahead suggestion list only presents 2 items. If I use a limit of 3, the suggestion list still displays 2 items. If I use a limit of 10, it displays all the 3 items of my prefetched table.
Any explanation about this issue is welcome.
Thanks!

https://github.com/twitter/typeahead.js/pull/1319 does fix it. This should be merged asap ;-)

:+1:

Does this persist in current versions?


fix(proptypes): relax proptypes errors on pagewizard

Closes #1227
Summary

Relax the required proptypes for pagewizardstep as they shouldn't be required

Change List (commits, features, bugs, etc)

fix(ListItemWrapper): invalid proptype for children
fix(PageWizard): remove the required proptypes for the functions as single step page wizards don't need them

Acceptance Test (how to verify the PR)

Only propTypes changes, no functional changes

:tada: This PR is included in version 2.100.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


🌱 Improvements to ginkgo E2E test suite

Summary
This PR makes various improvements to the ginkgo E2E test suite.
There is a bug fix regarding excessive enqueuing.
This PR adds missing calls to ginkgo.GinkgoHelper. This PR also replaces use of offset with use of ginkgo.GinkgoHelper.
This PR adds the ability to pass all allowed setup-kubestellar.sh flags/args through the ginkgo command.
The are improvements to debug logging.
Related issue(s)
Fixes #

/cc @effi-ofer
/cc @waltforme

/lgtm


ice: too many arguments to fn_ptr: log (got 2 args, expected 1)

//! Issue #56309

extern "C" {
    fn log(message_data: u32, message_size: u32);
}

pub fn main() {
    let message = "Hello, world!";
    unsafe {
        log(message.as_ptr() as u32, message.len() as u32);
    }
}

libgccjit.so: error: gcc_jit_context_new_call_through_ptr: too many arguments to fn_ptr: log (got 2 args, expected 1)
gcc_jit_rvalue_get_type: NULL rvalue
libgccjit.so: error: gcc_jit_function_new_local: NULL type
libgccjit.so: error: gcc_jit_block_add_assignment: NULL lvalue
gcc_jit_lvalue_as_rvalue: NULL lvalue

log is a function in libm. Gcc likely has it pre-declared with the same signature as the libm version to be able to replace it with a faster version at compile time. LLVM has the exact samw problem as I understand it. And in the past it also used to have to be an issue when #[link(wasm_import_module)] was used to import from a non-default module: https://github.com/rust-lang/rust/issues/56309 The test is not meant to work outside of webassembly with #[link(wasm_import_module)]. https://github.com/rust-lang/rust/blob/e5bb341f0e1db4e4407f129d9834f9ada2030b7c/tests/run-make/wasm-symbols-different-module/log.rs


Improve Option documentation and add MaybeSome function

Fix Option doc comment and add MaybeSome function for pointer conversion.

I pushed a new tag fn/v1.2.4 for this.


Craft 5 support

This makes the few changes needed for Craft 5.
Not sure how you want to handle branching between versions so I made the PR against master for now.
Fixes #12

Thanks @janhenckens we integrated this into our latest release. Thanks again for the help on this 🎉


feat: Make one click binding form controls searchable

Description
Make one-click binding form controls searchable. Leverage design system showSearch property
PR fixes following issue(s)
Fixes https://github.com/appsmithorg/appsmith/issues/27772
Type of change

New feature (non-breaking change which adds functionality)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview skipTests=true

@sbalaji1192 Can we show the pointer cursor over clickable elements like the Clear all and dropdown action?

@laveena-en This is an issue with design system select component, Could you please raise an issue there?

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


Arch Linux build error

Getting this error at build stage
x86_64 Linux 4.14.52-1-lts
[ 67%] Built target libcef_dll_wrapper [ 67%] Building CXX object brick/CMakeFiles/brick.dir/client_handler_linux.cc.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:89,                  from /home/user/tmp/brick/brick/client_handler_linux.cc:5: /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:59:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved1’ [-Werror=parentheses]    void (*__gtk_reserved1);         ^ /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:60:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved2’ [-Werror=parentheses]    void (*__gtk_reserved2);         ^ /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:61:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved3’ [-Werror=parentheses]    void (*__gtk_reserved3);         ^ /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:62:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved4’ [-Werror=parentheses]    void (*__gtk_reserved4);         ^ /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:63:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved5’ [-Werror=parentheses]    void (*__gtk_reserved5);         ^ /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:64:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved6’ [-Werror=parentheses]    void (*__gtk_reserved6);         ^ /usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:65:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved7’ [-Werror=parentheses]    void (*__gtk_reserved7);         ^ In file included from /usr/include/gtk-2.0/gtk/gtk.h:173,                  from /home/user/tmp/brick/brick/client_handler_linux.cc:5: /usr/include/gtk-2.0/gtk/gtkstatusicon.h:76:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved1’ [-Werror=parentheses]    void (*__gtk_reserved1);         ^ /usr/include/gtk-2.0/gtk/gtkstatusicon.h:77:8: error: unnecessary parentheses in declaration of ‘__gtk_reserved2’ [-Werror=parentheses]    void (*__gtk_reserved2);         ^ cc1plus: all warnings being treated as errors make[2]: *** [brick/CMakeFiles/brick.dir/build.make:209: brick/CMakeFiles/brick.dir/client_handler_linux.cc.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:141: brick/CMakeFiles/brick.dir/all] Error 2 make: *** [Makefile:130: all] Error 2

For anyone that stumbles upon this: build works fine even without the attached PR if -wError flags are removed. They are "just" warnings after all.


Incorrect use of aria-expanded attribute

The aria-expanded attribute is meant to be used on the button, not on the toggled container element.

Thanks!! Fixed in v2.2.4.


How to customize the animation ?

Great project, easy to implement and works very well.
Is there a way to customize the animation ? The widgets i want to animate are quite big so the scaling effect is a bit too jarring for what i want, i'd love to be able to make the widget scale a bit smaller than what it currently is.

Hey @lamarios  yes there is
AnimateFrom(
      key: _animateToController.tag(index),
      child: ...
      builder: (context, child, animation) {
       /// You can build your animation inside this builder
      ///
      /// By default I'm using a TweenSequanceto scale up then
      /// Start scaling down at the middle of the animation
        return ScaleTransition(
          scale: TweenSequence<double>([
            TweenSequenceItem<double>(
              tween: Tween(begin: 1, end: 3),
              weight: 50,
            ),
            TweenSequenceItem<double>(
              tween: Tween(begin: 3, end: .2),
              weight: 50,
            ),
          ]).animate(animation),
          child: child,
        );
 })


build failed

➜  tact-template git:(tact-release-1.5.0) ✗ yarn build
yarn run v1.22.22
$ tact --config ./tact.config.json
💼 Compiling project sample...
Tact compilation failed
Error: Line 33, col 9:
  32 |         self.add(1);
> 33 |         self.reply("incremented".asComment());
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  34 |     }
Type "SampleTactContract" does not have a function named "reply"
    at throwError (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/grammar/ast.js:49:11)
    at resolveCall (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/types/resolveExpression.js:264:34)
    at resolveExpression (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/types/resolveExpression.js:393:16)
    at processStatements (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/types/resolveStatements.js:80:61)
    at resolveStatements (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/types/resolveStatements.js:195:19)
    at precompile (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/pipeline/precompile.js:91:53)
    at build (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/pipeline/build.js:34:43)
    at Object.compileProjects (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/main.js:49:33)
    at /home/longer/workspace/private/tact-template/node_modules/ton-tact/bin/tact:18:20
    at Object.<anonymous> (/home/longer/workspace/private/tact-template/node_modules/ton-tact/bin/tact:23:3)
Done in 0.44s.

also it seems that tact doesn't suppoort += operator
➜  tact-template git:(tact-release-1.5.0) ✗ yarn build
yarn run v1.22.22
$ tact --config ./tact.config.json
💼 Compiling project sample...
Tact compilation failed
Error: Line 24, col 23:
  23 |         // Update counter
> 24 |         self.counter += v;
                             ^
  25 |     }
Expected "\"", "initOf", "null", "_", "A".."Z", "a".."z", "false", "true", a digit, "0X", "0x", "(", "!", "+", or "-"
    at parse (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/grammar/grammar.js:538:15)
    at parseImports (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/grammar/grammar.js:545:13)
    at processImports (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/pipeline/precompile.js:55:46)
    at precompile (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/pipeline/precompile.js:73:5)
    at build (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/pipeline/build.js:34:43)
    at Object.compileProjects (/home/longer/workspace/private/tact-template/node_modules/ton-tact/dist/main.js:49:33)
    at /home/longer/workspace/private/tact-template/node_modules/ton-tact/bin/tact:18:20
    at Object.<anonymous> (/home/longer/workspace/private/tact-template/node_modules/ton-tact/bin/tact:23:3)
    at Module._compile (node:internal/modules/cjs/loader:1546:14)
    at Object..js (node:internal/modules/cjs/loader:1689:10)
Done in 0.18s.

Did you do yarn install before trying to build your contract?

Did you do yarn install before trying to build your contract?

It works well. Thanks


moving to ansible v2.2 compatibility

Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

@ktdreyer @alfredodeza @andrewschoen
@samdoran do we also need to do the with_together loops?

test this please

Looks good to me, I've changed the CI to use ansible==2.2 for that test I just started up.

All the tests seem to be failing at:
TASK [ceph-mon : stat for ceph config and keys] ********************************
task path: /home/jenkins-build/build/workspace/ceph-ansible-pull-requests/DIST/ceph_ansible_pr_centos7/ceph-ansible/roles/ceph-mon/tasks/docker/checks.yml:13
fatal: [localhost]: FAILED! => {
    "failed": true,
    "msg": "'ceph_config_keys' is undefined"
}

https://jenkins.ceph.com/job/ceph-ansible-pull-requests/792/DIST=ceph_ansible_pr_centos7/console

@andrewschoen , @ktdreyer @alfredodeza Alright, it's a critical move, once we have this we need to branch out for "1.9.4 to 2.1.x" and explain this won't bring more features into the other branch, just bug fixes.

Signed-off-by: Julien Francoz<EMAIL_ADDRESS>

thanks @jfcoz

It would be a good idea to create a "version-1" branch at this point to maintain Ansible 1.9 compatibility, and then master can be tagged with "v2.0", "v2.1", etc.

@ktdreyer I just pushed a branch called: ansible-1.9, how does that sound for you?
Can we merge this now?

@leseb, would you please clarify what tags we should expect to see on each branch, going forward?
For example, will "1.0.z" tags be on the ansible-1.9 branch? If so, what tags will be on master?

@ktdreyer well going forward the ansible-1.9 branch will only receive bug fixes so I haven't thought about doing any tags for it. I'd like to keep our focus on 2.x, Ansible 2.x has been around for more than almost a year now, and most of the distro are shipping it so I believe it's fair.
In order to not confuse people and try to stay consistent I think next's master tag should be v2.x. What do you think?

I did a quick test and the ansible-1.9 branch isn't compatible with ansible 1.9.4.
I get:
ERROR: yum_repository is not a legal parameter in an Ansible task or handler

I think next's master tag should be v2.x. What do you think?

That's great, thanks for explaining.

@andrewschoen thanks for testing, do you mind having a closer look and submit a fix directly into the branch?
Thanks!
@ktdreyer np! Let's wait a bit until we have a working 1.9 branch then we will merge this one.


Add transitions and effects in the about section

Add transitions and effects to the buttons and the cards.

@Vanshiii203 Go for it.


Sensitivity

Hello.
I noticed that mouse pointer moves when you are moving out side the gaze circe. Is there an option or some parameter to change gaze circle size/radius?
By that, I want to achieve that, pointer will move more frequently - and will be triggered by smaller eye movement.
Issue example:

If there are two icons inside Gaze circle with such big radius, then pointer will not move between icons.

Have you had a chance to figure out how to use the precision pointer yet? This will allow you to select smaller targets within the circle, such as one of the two icons. In my case, I use my head rotation for the precision pointer. I like to use eViacam for tracking my head rotation because it's accurate and I don't need to wear any headgear. It just uses a standard webcam to track my head position.
By having a smaller gaze circle, there is more chance that the pointer could move unexpectedly due to random noise in the eye tracker. However, if you are getting better eye tracking accuracy than I am it might make sense to reduce the size of the circle.

I'm sorry, I'm not sure what you mean by "precision pointer". I don't know how to enable this option. Could you please advice how to use it?

Also... If you could advice how to change gaze circle it would be most appriciated.
Is this size parameter located in some file? so I can just edit it.

Read the "how it works" section here https://precisiongazemouse.com/. One important thing to understand about the mouse is that there are two ways of moving the mouse. The first is that it can warp instantly to a location on the screen using eye gaze. For more precise control, you can use head tracking to place the cursor within a pixel of your target.
It may not be necessary to reduce the size of the tracking circle in order to click on the location you desire. That's because you should be able to use head tracking to move the cursor precisely.
However, if you still prefer to reduce the size of the warp circle, you can do so by editing this line in the code: https://github.com/PrecisionGazeMouse/PrecisionGazeMouse/blob/master/PrecisionGazeMouse/WarpPointers/EyeXWarpPointer.cs#L21. You will have to build the program again. You can do so using the free Visual Studio community edition.

The reason why I'm stubborn about changing gaze circle size instead of using head movement tracking is because my Daughter's condition not allow to use this method of tracking.
By using relavively larger buttons/symbols for comunication she is able to point them quite precisely.
Thank you once again for your help. I will try to make size changes. I will back to you in couple of days to let you know how it works.

Oh that's cool I haven't thought about that use before but it makes sense! By the way, for full eye control Microsoft offers a free version integrated into Windows https://blogs.msdn.microsoft.com/accessibility/2017/08/01/from-hack-to-product-microsoft-empowers-people-with-eye-control-for-windows-10/. Of course, I would love you for you to use precision gaze mouse, I just want to share solutions I've heard of.

Thank for hint. I belive I saw this Windows beta eye control plugin but it was still not enough satisfying for us.
If you are curiouse... we are using you program to control aplication called Eyefeel - produced by AssisTech from Poland.
There is EN language and 30days trial version for download if you want to take a look. Here is the link: https://assistech.eu/en/eyefeel-en/

This could become a configuration setting similar to #17. Will take some work. Marking it as help wanted for now.

Hey just wanted to let you know that I addressed this issue in version 1.11. If you download the newest version you can configure it in the Windows user settings. I didn't make it part of the UI because I'm not sure that everyone needs this feature. However, this makes it accessible to you without having to compile the code.
To change the size of the warp threshold, first install and run the new version. Now open Windows Explorer and enter in the address bar %LocalAppData%\PrecisionGazeMouse. Next, find the newest folder and open user.config. Paste in the following:
<setting name="EyeXWarpThreshold" serializeAs="String">
    <value>500</value>
</setting>

Set the size of the circle to any size you like, in pixels. If you can't get it working just let me know! Closing for now but reopen if needed.

Hi,
Thank you very much for your help. I will test latest update shortly. I really appreciate your help.

Hi Nash,
I've tested your update. Setting new size of gaze treshold by changing value in config file is working. Thank you for that! 👍

Glad it works! If there's anything else I can do just let me know.


windows defender found the conteban trojan.

Can the author explain this?

It's called a false positive, the code is all here if you want to read it.

is opensource, use virustotal for check it !


Dark Mode

Dark Mode should be more like a grey tone and (maybe) customizable.

What app/window are you talking about?
I think it would be good to stick with the usual, native implementation of window theme colors.

I am talking about the main/ settings window. In dark mode it is like
completely black but I think it should be more like a grey-ish.

we use OS level brushes.


⚠ Jenkins Plugins Artifactory has degraded performance

In dabaa14, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1238 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 9f0a7ea after 12 minutes.


String.insert() not working correctly

Godot version:

3.1.1-stable
OS/device including version:

Windows 10, latest
Issue description:

Inserting in a string only seems to be working with a string directly instead of declaring a var first and then inserting in this var.
For example this is working:
var a = "12345".insert(2,"x")
print(a)

However, the piece of code below does not work.
Steps to reproduce:
This should be enough to reproduce the issue:
var a = "12345"
a.insert(2,"x")
print(a)

Minimal reproduction project:

This is probably intended, but documentation doesn't clarify it properly. The method returns the resulting String, so the original one doesn't get modified.

More than just a documentation question, I think this issue raises a more global programming design question.
The design choice for String is: all methods that modify the input string return a new String and do not actually modify the input. If you want to replace the input with output value, you'll need to do a = a.insert(2, "x").
On the contrary, Spatial.rotate() does modify the input object and returns nothing.
IMHO, all methods should comply the "setter/modifier methods do modify the input and return nothing".
In terms of memory, this means 1 less variable allocation.
The "return new value" policy is sometimes considered as bad practice, or more likely a old-fashioned way. But it is really subject to personal tastes.
However, such design change will bring backwards incompatibility, so it may not happen (soon).

Thanks @KoBeWi, looks like I missed the return type here. Like @StraToN and you mentioned, the documentation is quite confusing IMHO.
On one hand you have functions like String insert that return a new string, on the other there is e.g. void erase that just returns nothing while doing it's job.
Anyways, I'm going to close this issue as it's only been a misunderstanding on my part, thanks!

I'd say that documentation could be improved here. Now that I look at String docs, some methods say that they return a value and some just say about modifying string. It should be more consistent. But that's another issue probably.


Add diff-poetry-lock to PR actions for Poetry lock diff improvements

diff-poetry-lock can produce really nice report comments in PRs to show what changed in a poetry.lock.

It's lagging a little behind in updates so let's wait until it supports Poetry 1.7+ before using it.

Completed satisfactorily in 954d48c8f5d62f785c07c57977f09c385739012b


ID-398 - Fix Paper ID "Exit ID" not working

Purpose
Exit ID link was not taking into account the base path: /lpa/identity-check
Fixes https://opgtransform.atlassian.net/browse/ID-398
Approach
Using twig filter basepath which grabs it from the environment variable PREFIX
Tested locally and on an isolated deployment at https://id-398.development.sirius.opg.service.justice.gov.uk/

I tried to avoid having to any PHP for this one. One liner in twig.


Debug log ID
49P3YIFF-euc
What happened?
My BetterBibTeX export fails again. This time the error message is:
Unexpected Zotero Item type "dataset"itemToCSLJSON
I googled and found this:
https://forums.zotero.org/discussion/104104/saved-online-with-no-account-database-corrupt
There were two new item types introduced about ten days ago and that's about the time when the export ran successfully for the last time.
Thus maybe my problem is caused by the new item types?
Regards,
Mela

Does it work if you export without checking "background export"?

I'm using the automatic export. Need to look where I even find that option.

Found it.
Yes, export worked when "Background export" was unchecked.

Can you verify that it works?

Export finished without errors.


Improve StringUtil#replace throughput

Motivation:
StringUtil#replace uses substring to append a String region into a
StringBuilder. This causes useless copies, as StringBuilder#append
can take start and end indexes.
Modification:
Use proper StringBuilder#append
[overload](https://docs.oracle.com/javase/8/docs/api/java/lang/StringBui
lder.html#append-java.lang.CharSequence-int-int-).
Result:
Better throughput. See https://github.com/apache/commons-lang/pull/300
for impact of similar change on commons-lang3.

benchmark executed -> here

Wow nice catch!


Switch to MIT license

Before merging this PR, we will need approval from all contributors

I approve the change to MIT license.
The other human authors are @jdhoffa and @2diiKlaus. Not sure how to get approval from the institutional author "2 Degrees Investing Initiative"; maybe you Klaus or Jakob can represent 2DII?
Authors@R:
    c(person(given = "Mauro",
             family = "Lepore",
...
      person(given = "Jackson",
             family = "Hoffart",
...
      person(given = "Klaus",
             family = "Hagedorn",
...
      person(given = "2 Degrees Investing Initiative",
...
             email = "contact@2degrees-investing.org"))

@2diiKlaus, If you support the change to MIT license, can you please write a comment here stating so, e.g.

I approve the change to MIT license.

Also, who can approve on behalf of 2DII? Is it you too?

@jdhoffa, as the author of this PR I assume you support the change to MIT license; but to leave no doubts, can you please write a comment here stating so, e.g.

I approve the change to MIT license.

I approve the change to MIT license.

I support changing the license of this package to MIT.

@jdhoffa, given our discussion on Slack, it seems 2DII's directors approved this change. I suggest we merge and try get this to CRAN.


Allow user to set TARGET_FPS_FOREGROUND & TARGET_FPS_BACKGROUND

Feature/enhancement description:
I would love the option to set these two values:
TARGET_FPS_FOREGROUND
TARGET_FPS_BACKGROUND

Yeah good idea. I'm a bit busy at the moment, but this seems like a good feature for a first pull request if you want to tackle it ;)

Yeah, I'd love to contribute!
I'll look into it

Implemented in #32


karpenter: cloudformation deployment fails

Describe the bug
With the new blueprint version v1.0.3, the blueprintmanifestdefaultprovisioner resource in cloudformation fails with the following error.
Received response status [FAILED] from custom resource. Message returned: Error: b'error: error validating "/tmp/manifest.yaml": error validating data: ValidationError(Provisioner.spec.taints): invalid type for sh.karpenter.v1alpha5.Provisioner.spec.taints: got "map", expected "array"; if you choose to ignore these errors, turn validation off with --validate=false\n'
Expected Behavior
I was expecting it to just work after upgrading to version from 1.0.3 from 1.0.2. No other changes were deployed.
Current Behavior
Blueprint pipeline failed.
Reproduction Steps
Can just deploy a blueprint project with karpenter addon.
Possible Solution
maybe need to update the custom resource python lambda function as seen in the error
Additional Information/Context
No response
CDK CLI Version
2.29.1
EKS Blueprints Version
1.0.3
Node.js Version
16.14.2
Environment details (OS name and version, etc.)
macOS
Other information
No response

@tusharf5 We just released 1.0.4 with the fixes in. Please take a look and let me know if it works on your end.

@youngjeong46 I'll try it and #427 this weekend. Thanks for the quick fix.

Works now. Thanks.


having a PR for bumping version seems useful

Description

Release process documentation change.
Motivation and Context

It would be easier to understand what PRs have been merged since last release.
Have you tested this? If so, how?

N/A

Never mind, I think I misinterpreted how Github PR list works. And it seems we missed some PRs in the latest release note. I will fix.

When I look for PR's that's been going in I usually just look at the commit list and let GitHub figure out which PR they are associated with.


Docker standalone-cluster flags

Feedback
Some flags (at least their doc strings) in tanzu standalone-cluster create seem a bit misleading/lack of details.
Example 1:
-i, --infrastructure string   Infrastructure to deploy the standalone cluster on. Only needed when using -i docker. < but apparently the other infrastructure providers don't need it - so why have this flag at all?
Example 2:
-f, --file string             Configuration file from which to create a standalone cluster. I could not find documentation about the configuration file format (not in the docs either). Is this a valid kind config file?
Suggested Changes
Example 1:
Instead of -i docker make it -docker to indicate a docker option and not confuse this flag with other infrastructures, e.g. vsphere. Unless in future releases we want to open -i for other infra providers. Then consider rewording the help to provide the supported ENUMs, e.g. Infrastructure to deploy the standalone cluster on. Valid options: "docker" and later expand the section with other providers.
Example 2:
Give details on the expected configuration file, e.g. kind config, etc.

Environment Details

Build version (tanzu version):

tanzu version
version: v1.3.0
buildDate: 2021-06-03
sha: b261a8b

Operating System (client): OSX

Closing - there is a new standalone-cluster proposal that uses a different model with a much liter weight methodology. Please look at the proposal, try it out, and give your feedback there!
Since the current standalone-cluster plugin is being deprecated in a future release, we will not be accepting new features.


API: form submitted twice (two XHR requests)

There is no example within the documentation on how to combine form AJAX API https://semantic-ui.com/behaviors/api.html#response-callbacks with form validation  https://semantic-ui.com/behaviors/form.html#/examples
After much searching, I finally found a way to combine both in a way that was apparently working. But now, I notice that pressing enter (as opposed to clicking the 'submit' button) will submit the form twice via XHR.
I will post a test case. Meanwhile, could a full working example combining form validation + ajax be posted within the documentation?
Thanks.

For the record, I found several issues referring to the same symptom: XHR being fired twice:
Bug with Api when using with form (makes 2 requests):  https://github.com/Semantic-Org/Semantic-UI/issues/4298 . The sample code provided there looks like mine, with both .api() and .form() being attached to the same form element.
Form + api is making 2 requests  https://github.com/Semantic-Org/Semantic-UI/issues/4161  by the same user, who for some reason closed the issues without explanation.
[API] PUT Method fires twice  https://github.com/Semantic-Org/Semantic-UI/issues/3997
Search make 2 requests!!! https://github.com/Semantic-Org/Semantic-UI/issues/3282 This issue is labelled "Needs Test Case" and closed, even though there is an included fiddle which still displays the same buggy behaviour.

Here is my definition for the form :
       $('#login-form')
                .form({
                        on: 'submit',
                        debug: true,
                        fields: {
                                username: {
                                        identifier: 'username',
                                        rules     : [
                                                {type  : 'empty',
                                                prompt: 'Enter your username.'},
                                        ]
                                },
                                password: {
                                        identifier: 'password',
                                        rules     : [
                                                {type  : 'empty',
                                                prompt: 'Enter your password.'},
                                        ]
                                },
                        }
                })
                .api({
                        url: '/login',
                        method       : 'POST',
                        serializeForm: true,
                        onResponse   : function(response) {
                                console.log("onResponse");
                                console.log(response);
                        },
                        onSuccess    : function(response) {
                                console.log("success");
                                console.log(response);
                        },
                        onFailure    : function(response) {
                                console.log("failule");
                                alert(response);
                        },
                });

As I said, the form behaves when clicking the 'submit' button, but just after reloading the page, the buggy behaviour is observed when pressing 'enter' after filling in the text fields.

If I remove the .form() definition above, I cannot reproduce the bug.
If we have both .form() and .api() attached to the same form, then the bug occurs.
I have enabled debug: true and verbose: true for both behaviours (form and api).
Without .form(), the api console table has the following entries:
Extending existing data with form data
Using specified url
Querying URL
Using AJAX settings
Sending request
Adding loading state to element
Created server request
Response is not JSON, skipping validation
Removing loading state from element
Successful API Response

with .form(), the api console.table has the following entries:

Extending existing data with form data
Using specified url
Querying URL
Using AJAX settings
Sending request
Adding loading state to element
Created server request
Interrupting previous request
Cancelling API request
Extending existing data with form data
Using specified url
Querying URL
Using AJAX settings
Sending request
Adding loading state to element
Created server request
XHR request determined to be aborted
Removing loading state from element
XHR Aborted (Most likely caused by page navigation or CORS Policy)
Response is not JSON, skipping validation

The above output should confirm the existence of a  bug in the semantic-UI API.

I added:
keyboardShortcuts: false, to the .form() definition, and it appears to resolve the issue.
I am not sure whether the observed behaviour is intended. It appears that many users have stumbled upon this issue.
However, as stated in my opening comment, there is no example in the official documentation on how to properly combine both .form() and .api().  I think a working example would be a necessary addition, with the gotcha (bug) discussed above being clearly documented.

Yes, this appears to be a legitimate bug.
Semantic UI adds a keyboard shortcut of its own that submits the form when you press enter, but this submission seems to bypass the validation mechanism for some reason.
Not sure how to get around this outside of not using SUI's API behavior.

Double submit via enter key was fixed in the upcoming 2.9.0 of the community fork Fomantic-UI by https://github.com/fomantic/Fomantic-UI/pull/2038


All Journal entries are offset from correct map coordinate

All journal entires are placed in the incorrect location. Near the bottom of the image, the entries are placed slightly below where they should be. Near the top of the image, the journal entries are very far below their POI on the map image

Unable to reproduce, must be user error


Segmentation fault and bus error when running qcec

Environment information
OS: MacOS
MQT version: 2.6.0
Compiler: C++
Description
I'm trying to run a circuit equivalence check for two particular circuits (Steane code).
There are no mid-circuit measurements, and I have
I get

segmentation fault with qcec.verify("circ1.qasm", "circ2.qasm", transform_dynamic_circuit=True)
bus error with qcec.verify("circ1.qasm", "circ2.qasm")

Circ1.qasm is an actual code of Steane code circuit
Circ2.qasm is a hardware aware compiled circuit for the following coupling map:
 connection=[
        (0, 1),
        (1, 2),
        (2, 3),
        (2, 5),
        (4, 5),
        (5, 6),
        (5, 8),
        (7, 8),
        (8, 9),
        (9, 10),
        (3, 11),
        (7, 12),
        (10, 13),
        (0, 14),
    ],

Qubit 13 and 14 on the coupling graph are special, and cannot be used for any gates, only measuring the rest of the qubits.
circ1.qasm:
OPENQASM 2.0;
include "qelib1.inc";
qreg q[13];
creg c[3];
x q[5];
cx q[0],q[7];
cx q[2],q[7];
cx q[4],q[7];
cx q[6],q[7];
cx q[1],q[8];
cx q[2],q[8];
cx q[5],q[8];
cx q[6],q[8];
cx q[3],q[9];
cx q[4],q[9];
cx q[5],q[9];
cx q[6],q[9];
measure q[7] -> c[0];
measure q[8] -> c[1];
measure q[9] -> c[2];

circ2.qasm
OPENQASM 2.0;
include "qelib1.inc";
qreg q[15];
creg c[3];
cx q[3],q[2];
cx q[7],q[8];
cx q[9],q[8];
cx q[5],q[8];
cx q[5],q[2];
cx q[1],q[2];
cx q[2],q[1];
cx q[1],q[2];
cx q[4],q[5];
cx q[5],q[4];
cx q[4],q[5];
cx q[2],q[5];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[8],q[5];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
rx(pi) q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[8];
cx q[8],q[7];
cx q[7],q[8];
cx q[7],q[12];
cx q[8],q[9];
cx q[8],q[5];
cx q[5],q[8];
cx q[8],q[5];
cx q[5],q[8];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[0],q[1];
cx q[1],q[0];
cx q[0],q[1];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
measure q[13] -> c[0];
measure q[10] -> c[0];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
measure q[13] -> c[1];
measure q[10] -> c[1];
measure q[14] -> c[2];
measure q[0] -> c[2];

Expected behavior
Output with whether circuits are equivalent or not
How to Reproduce
from mqt import qcec

Code:
    print("With transform_dynamic_circuit")
    result = qcec.verify("circ1.qasm", "circ2.qasm", transform_dynamic_circuit=True)

Terminal Output:
    With transform_dynamic_circuit
    zsh: segmentation fault  /opt/anaconda3/envs/smt_compiler/bin/python

Code:
    print("Without transform_dynamic_circuit")
    result = qcec.verify("circ1.qasm", "circ2.qasm")

Terminal ouput:
    Without transform_dynamic_circuit
    zsh: bus error  /opt/anaconda3/envs/smt_compiler/bin/python

Hey 👋🏻
Many thanks for opening this issue and for the complete description of the problem.
I am currently on vacation and will only be able to look more deeply next week.
However, let me clarify a few things first:
In what sense would you consider these circuits equivalent? They act on different numbers of qubits (13 vs 15) and contain a different number of measurements (3 vs 6), but the same number of classical registers (3).
I am fairly sure this is what trips up QCEC, i.e. repeated measurements into a single classical bit without any action in between.
In general, I think I'd like to understand a bit more about the kind of equivalence you are looking for.

I tried removing the measurements of q[13] and q[14] from circ2.qasm
OPENQASM 2.0;
include "qelib1.inc";
qreg q[15];
creg c[3];
cx q[3],q[2];
cx q[7],q[8];
cx q[9],q[8];
cx q[5],q[8];
cx q[5],q[2];
cx q[1],q[2];
cx q[2],q[1];
cx q[1],q[2];
cx q[4],q[5];
cx q[5],q[4];
cx q[4],q[5];
cx q[2],q[5];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[8],q[5];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
rx(pi) q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[8];
cx q[8],q[7];
cx q[7],q[8];
cx q[7],q[12];
cx q[8],q[9];
cx q[8],q[5];
cx q[5],q[8];
cx q[8],q[5];
cx q[5],q[8];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[0],q[1];
cx q[1],q[0];
cx q[0],q[1];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
measure q[10] -> c[0];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
measure q[10] -> c[1];
measure q[0] -> c[2];

And I get this error
ValueError: DD for non-unitary operation not available!

I want them to be equivalent in terms of the quantum state at the end of all the gates

I tried removing the measurements of q[13] and q[14] from circ2.qasm
OPENQASM 2.0;
include "qelib1.inc";
qreg q[15];
creg c[3];
cx q[3],q[2];
cx q[7],q[8];
cx q[9],q[8];
cx q[5],q[8];
cx q[5],q[2];
cx q[1],q[2];
cx q[2],q[1];
cx q[1],q[2];
cx q[4],q[5];
cx q[5],q[4];
cx q[4],q[5];
cx q[2],q[5];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[8],q[5];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
rx(pi) q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[8];
cx q[8],q[7];
cx q[7],q[8];
cx q[7],q[12];
cx q[8],q[9];
cx q[8],q[5];
cx q[5],q[8];
cx q[8],q[5];
cx q[5],q[8];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[0],q[1];
cx q[1],q[0];
cx q[0],q[1];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
measure q[10] -> c[0];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
measure q[10] -> c[1];
measure q[0] -> c[2];

And I get this error ValueError: DD for non-unitary operation not available!

One of the reasons that particular example is throwing an error is because you are measuring q[10], but then apply further gates on that qubit after the measurement.
You are also subsequently measuring that qubit again.
Is there any reason for not writing that circuit as
OPENQASM 2.0;
include "qelib1.inc";
qreg q[15];
creg c[3];
cx q[3],q[2];
cx q[7],q[8];
cx q[9],q[8];
cx q[5],q[8];
cx q[5],q[2];
cx q[1],q[2];
cx q[2],q[1];
cx q[1],q[2];
cx q[4],q[5];
cx q[5],q[4];
cx q[4],q[5];
cx q[2],q[5];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[8],q[5];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
rx(pi) q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[2],q[3];
cx q[3],q[2];
cx q[2],q[3];
cx q[3],q[11];
cx q[11],q[3];
cx q[3],q[11];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[8];
cx q[8],q[7];
cx q[7],q[8];
cx q[7],q[12];
cx q[8],q[9];
cx q[8],q[5];
cx q[5],q[8];
cx q[8],q[5];
cx q[5],q[8];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[2],q[1];
cx q[0],q[1];
cx q[1],q[0];
cx q[0],q[1];
cx q[2],q[5];
cx q[5],q[2];
cx q[2],q[5];
cx q[9],q[10];
cx q[10],q[9];
cx q[9],q[10];
cx q[8],q[9];
cx q[9],q[8];
cx q[8],q[9];
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];
measure q[10] -> c[0];
measure q[9] -> c[1];
measure q[0] -> c[2];

Furthermore, are you sure that the last part of the circuit as written here is as you intended it to be?
The sequence
cx q[12],q[7];
cx q[7],q[12];
cx q[7],q[12];
cx q[12],q[7];
cx q[7],q[12];

at the end, simply reduces to
cx q[7],q[12];

I want them to be equivalent in terms of the quantum state at the end of all the gates Physical qubits 13 and 14 both have to be |0> at the end. I can provide the final mapping at the end to compare the circuits.

Ok, so let me try to get this straight:

the first circuit acts on 13 qubits and measures 3 of them at the end of the circuit
the second circuit acts on 15 qubits and also measures 3 of them at the end of the circuit
you are not interested in the value of the three measured qubits in both circuits
you want q[13] and q[14] in the second circuit to be zero at the end
you want the remaining 10 qubits in both circuits to represent the same state
in all of this, you are only interested in the resulting state when you start with the all-zero state |0...0>

Please correct me if anything of the above is wrong.
As of now, QCEC is not equipped for verifying that kind of equivalence out of the box.
It typically considers a much stricter notion of equivalence (unitary equivalence).
If I understood correctly, what you are looking for is "simply" a question of simulating both circuits with the all-zero state input and comparing the resulting states.
It should be possible to make this possible with QCEC, but might require some implementation work.

It works with the following code bit:
qcec.verify("circ1.qasm", "circ2.qasm",
                     transform_dynamic_circuit=True,
                     backpropagate_output_permutation=True,
                     fix_output_permutation_mismatch=True)


Fix docs for "unless-stopped" restart policy

Proposed changes
This part:

or Docker itself is stopped or restarted.

is not accurate. When you restart docker daemon containers with unless-stopped policy are also restarted, as long as they haven't been explicitly stopped before the docker daemon restart.
Please read correct examples of documentation for unless-stopped restart policy:

https://github.com/moby/moby/blob/766d9edf39b79e11018bb0f55056b5bd915ddf3c/api/swagger.yaml#L314
https://github.com/moby/moby/blob/766d9edf39b79e11018bb0f55056b5bd915ddf3c/api/types/container/host_config.go#L279

If you are still in doubt please read the MR that added unless-stopped restart policy:
https://github.com/moby/moby/pull/15348
and the inital ticket for it:
https://github.com/moby/moby/issues/11008

Hang on. @thaJeztah .... the original text came directly from the cli and docker-ce docs:
https://github.com/docker/cli/blob/master/docs/reference/commandline/run.md
https://github.com/docker/docker-ce/blob/18.03/components/cli/docs/reference/commandline/run.md

Restart the container unless it is explicitly stopped or Docker itself is stopped or restarted.

@gbarr01 this one: https://github.com/docker/cli/blob/master/docs/reference/run.md#restart-policies---restart is correct

Always restart the container regardless of the exit status, but do not start it on daemon startup if the container has been put to a stopped state before.

@adw1n, actually, this seems to be the correct doc:
https://github.com/docker/cli/blob/master/docs/reference/commandline/run.md#restart-policies---restart
The commit in reference/commandline/run.md was much later than reference/run.md:
https://github.com/docker/cli/commit/df39b014
https://github.com/docker/cli/commit/d281b72a
https://github.com/docker/cli/commit/e9ce688d
The question is, why do they differ? The restart policies in reference/run.md should match those in reference/commandline/run.md.
cc: @thajeztah

@adw1n , I'm going to revert this commit. If I'm wrong, I can reapply. But I think the real problem is that the 2 CLI docs need to be in sync. Sorry for the confusion and thanks for the PR.


Make Anchor Output Sweeps configurable.

The sweeping of anchor outputs is not really aligned with incentives when mempool conditions do not allow 1 sat/vbyte transactions to be confirmed in a reasonable amount of time. Always sweeping anchor outputs although they have no real chance to be confirmed will cost more eventually when one needs to use the funds which were used to sweep this output. In addition anchor sweeps are mostly bumped by third parties which can lead to a mandatory restart because lnd does not monitor the mempool when RBFs happen.
Therefore noderunners have now the possibility to switch off the anchor recovery. I did not switch it off by default because a lot of unit test would fail as a consequence.
--sweeper.notrecoveranchoroutputs=true
fixes #7602
Checking for the tests to pass ....

I don't think we want to never sweep anchors. Never sweeping them means we can never use it to automatically fee bump. In that case, then BumpFee will need to be used to bump the fee for the anchor output. With the way things are set up right now, you still need to offer the inputs to the sweeper, as otherwise it won't know how to sweep it (it's a "special" output).
I think something like this could be a middleground: https://github.com/lightningnetwork/lnd/pull/7965#issuecomment-1718627997

This change would still need one or two integration tests to finalize, if we wanna go this route.

Further to this change, it should be granted that any zero-conf wallet input which is the result of a sweep-transaction should not be allowed to open a channel with (when using zero-conf utxos) because those can always be RBFed by the sweeper in the background leading to all sorts of side-effects.

Obsolete with the new sweeper subsystem.


Add k8s cluster creation on AWS

Hi,
I ve created k8s cluster creation on aws.
I don't have modify exercise 4 who deal with adding a node on GCloud and not in AWS. I can add another PR if needed.
Hope this tuto will help you.
Let me know if update is necessary.
Regards

I have to change size of node and master to a small one `--node-size t2.micro \

--master-size t2.micro  ` could you modify inline?
Sorry for that

I made those changes.  The changes look great!  Thank you for the contribution.


Signal pallet from scratch

The Signal pallet was created from scratch https://github.com/gamedaoco/gamedao-protocol/issues/65
Interface changes:

One extrinsic for all proposal types.
One extrinsic for all voting types.

New features:

https://github.com/gamedaoco/gamedao-protocol/issues/22
https://github.com/gamedaoco/gamedao-protocol/issues/62
Automated slashing.
Scheduled proposal activation, if start > current block (Created -> Activated).
Majority types (Simple, Relative, Absolute) https://github.com/gamedaoco/gamedao-haiku/issues/108
Voting power: Unit (Person, Token), Scale (Linear, Quadratic).
Quorum.
Token weighted voting.
MultiCurrency support for Withdrawal and Spending proposals (Flow Campaigns still don't support it).
Early finalization: Absolute majority > 50% or everybody voted.
Add validation for voting: org members allowed for General or Spending proposals, and campaign contributors allowed for Withdrawal proposals.

Other changes:

Storage reduced from 27 to 6 items https://github.com/gamedaoco/gamedao-protocol/issues/57
Naming changes for Events (I was inspired by FRAME pallets) - could be a discussion.
Types changes
Tests, mocks, benchmarks, weights.

Next steps:

Create documentation - in progress.
Flow pallet: add support for multiple currencies https://github.com/gamedaoco/gamedao-protocol/issues/70
Testing approach should be reconsidered since its current implementation has too much of repeated code (create test framework, refactor, etc.).
on_finalize seems to be heavy. Find out the proper value for MaxProposalsPerBlock
Add docs. Some are missing.
Multiple options/choices voting - this is not ready yet. Medium size task up to 5 SP.

Extrinsics:
pub fn proposal(
	origin: OriginFor<T>,
	proposal_type: ProposalType,
	org_id: T::Hash,
	title: BoundedVec<u8, T::StringLimit>,
	cid: BoundedVec<u8, T::StringLimit>,
	expiry: T::BlockNumber,
	majority: Majority,
	unit: Unit,
	scale: Scale,
	// Optional params:
	start: Option<T::BlockNumber>,
	quorum: Option<Permill>,
	deposit: Option<T::Balance>,
	// Optional proposal specific params:
	campaign_id: Option<T::Hash>,
	amount: Option<T::Balance>,
	beneficiary: Option<T::AccountId>,
	currency_id: Option<T::CurrencyId>,
)

pub fn vote(
	origin: OriginFor<T>,
	proposal_id: T::Hash,
	approve: bool,
	deposit: Option<T::Balance>,
)

After the recent discussion, the Spending proposal logic should be changed.

remove Failed proposal status -> should be finalized
add funds reserving on proposal start
transfer reserved funds at the end

I am switching PR to draft.

Wrong target branch, changes reverted. New PR https://github.com/gamedaoco/gamedao-protocol/pull/79


Fix atomic store in WebGPU

Fixes the previously failing test_jit_assign_int8
Instead of just atomicAdd-ing the packed data into position, we first clear the position by atomicAnd-ing with a mask, then perform the atomicAdd

Nice!


createPalette - Remix - SyntaxError: Cannot use import statement outside a module

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Building a ssr app in Remix I have a fully custom theme and for the palette I use the createPalette function. In there I do lots of overrides and additions. What I have works as expected in Create React App and I can assume it's webpack doing the magic there with babel.
The error when starting Remix dev
/Users/jeffbaumgardt/Projects/dashboard-remix/node_modules/@mui/material/styles/createPalette.js:1
import _extends from "@babel/runtime/helpers/esm/extends";
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:355:18)
    at wrapSafe (node:internal/modules/cjs/loader:1022:15)
    at Module._compile (node:internal/modules/cjs/loader:1056:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:996:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at Object.<anonymous> (/Users/jeffbaumgardt/Projects/dashboard-remix/app/style/theme.ts:2:27)
    at Module._compile (node:internal/modules/cjs/loader:1092:14)

If I do not use createPalette and just pass a generic palette object to the theme it works as expected.
Expected behavior 🤔
I assume the issue is with the babel import, since that's the error it calls out in the stack. But I would assume createPalette to work outside a module or whatever is needed. I am using the @latest of all @mui packages and @emotion. I have not included babel in my project.
The basic example I can provide is:
import {createTheme} from '@mui/material'
import createPalette from '@mui/material/styles/createPalette'

export const theme = createTheme({
    palette: createPalette({
        primary: {
            main: '#3f51b5',
            light: '#7986cb',
            dark: '#303f9f',
        },
    }),
})

Naïve example but I'm doing much more in my use case by adding many more colors and changing existing palette colors to my design theme.
Steps to reproduce 🕹
Steps:

Create a remix app npx create-remix follow prompts
Install all necessary @mui + @emotion packages to add a ThemeProvider and theme.
Add ThemeProvider to entry.client and entry.server as per example Remix-with-typescript Example
Create a new theme as per example above using createPalette.
npm run dev - open browser to provided uri
Notice error
Go back to theme and remove createPalette import and modify createTheme to a generic palette object per official remix example
Refresh browser and notice the error is removed.

Context 🔦
In a broader scope this is my built theme that I'm am using, in production in CRA.
import createPalette from '@mui/material/styles/createPalette'
import type { PaletteColorOptions, Palette, PaletteOptions } from '@mui/material';
import designTokens from './designTokens.json'

type SimpleDesignTokenColor = {value: string; type: string}
type DesignTokenColor = {
    Main: {value: string; type: string}
    Light?: {value: string; type: string}
    Dark?: {value: string; type: string}
}

type Color = keyof typeof designTokens.Color
// Hardcoded colors based in the design tokens, very hard to read in automatically.
type CustomPaletteColors = 'white' | 'midnightPurple' | 'gray' | 'teal' | 'yellow' | 'brightBlue' | 'brightGreen' | 'red'
type CustomPalette = Record<CustomPaletteColors, PaletteColorOptions>

const tokenColors = Object.keys(designTokens.Color) as Color[]

const customPalette = tokenColors.reduce((prev, curr) => {
    const colorName = (curr[0].toLowerCase() + curr.slice(1)) as CustomPaletteColors

    if (!prev[colorName]) {
        let main = ''
        let light = ''
        let dark = ''
        if ((designTokens.Color[curr] as SimpleDesignTokenColor).value) {
            main = (designTokens.Color[curr] as SimpleDesignTokenColor).value
        } else {
            const designTokenColor = designTokens.Color[curr] as DesignTokenColor
            if (designTokenColor.Main) {
                main = designTokenColor.Main.value
            }
            if (designTokenColor.Light) {
                light = designTokenColor.Light.value
            }
            if (designTokenColor.Dark) {
                dark = designTokenColor.Dark.value
            }
        }
        prev[colorName] = {
            main,
            light,
            dark,
        }
    }

    return prev
}, {} as CustomPalette)

const palette = createPalette({
    ...customPalette,

    primary: {
        main: designTokens.Theme.Primary.Main.value,
        light: designTokens.Theme.Primary.Light.value,
    },
    warning: {
        main: designTokens.Theme.Warning.Main.value,
        light: designTokens.Theme.Warning.Light.value,
    },
    info: {
        main: designTokens.Theme.Info.Main.value,
        light: designTokens.Theme.Info.Light.value,
    },
    success: {
        main: designTokens.Theme.Success.Main.value,
    },
    error: {
        main: designTokens.Theme.Error.Main.value,
        light: designTokens.Theme.Error.Light.value,
    },
    text: {
        primary: designTokens.Theme.Text.Primary.value,
        secondary: designTokens.Theme.Text.Secondary.value,
    },
    divider: designTokens.Theme.Divider.value,
    background: {
        paper: designTokens.Theme.Background.Paper.value,
        default: designTokens.Theme.Background.Default.value,
    },
})

export default palette
export interface VisionPalette extends Palette {
    white: Palette['primary']
    midnightPurple: Palette['primary']
    gray: Palette['primary']
    teal: Palette['primary']
    yellow: Palette['primary']
    brightBlue: Palette['primary']
    brightGreen: Palette['primary']
    red: Palette['primary']
}
export interface VisionPaletteOptions extends PaletteOptions {
    white: PaletteOptions['primary']
    midnightPurple: PaletteOptions['primary']
    gray: PaletteOptions['primary']
    teal: PaletteOptions['primary']
    yellow: PaletteOptions['primary']
    brightBlue: PaletteOptions['primary']
    birghtGreen: PaletteOptions['primary']
    red: PaletteOptions['primary']
}

declare module '@mui/material/styles/createPalette' {
    export interface Palette {
        white: Palette['primary']
        midnightPurple: Palette['primary']
        gray: Palette['primary']
        teal: Palette['primary']
        yellow: Palette['primary']
        brightBlue: Palette['primary']
        brightGreen: Palette['primary']
        red: Palette['primary']
    }
    export interface PaletteOptions {
        white: PaletteOptions['primary']
        midnightPurple: PaletteOptions['primary']
        gray: PaletteOptions['primary']
        teal: PaletteOptions['primary']
        yellow: PaletteOptions['primary']
        brightBlue: PaletteOptions['primary']
        brightGreen: PaletteOptions['primary']
        red: PaletteOptions['primary']
    }
}

As you can see I do a fair amount of changes and additions.
Elsewhere I export the ThemeProvider with theme already attached. Build and publish to a package repository. The import into an app is just a new context provider that takes no props since the theme is already attached.
Your environment 🌎

`npx @mui/envinfo`
  System:
    OS: macOS 12.3.1
  Binaries:
    Node: 15.14.0 - ~/.nvm/versions/node/v15.14.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 7.7.6 - ~/.nvm/versions/node/v15.14.0/bin/npm
  Browsers:
    Chrome: 102.0.5005.61
    Edge: Not Found
    Firefox: 88.0.1
    Safari: 15.4
  npmPackages:
    @emotion/react: ^11.9.0 => 11.9.0
    @emotion/styled: ^11.8.1 => 11.8.1
    @mui/base:  5.0.0-alpha.83
    @mui/icons-material: ^5.8.2 => 5.8.2
    @mui/lab: ^5.0.0-alpha.84 => 5.0.0-alpha.84
    @mui/material: ^5.8.2 => 5.8.2
    @mui/private-theming:  5.8.0
    @mui/styled-engine:  5.8.0
    @mui/styles: ^5.8.0 => 5.8.0
    @mui/system:  5.8.2
    @mui/types:  7.1.3
    @mui/utils:  5.8.0
    @mui/x-date-pickers:  5.0.0-alpha.1
    @types/react: ^17.0.45 => 17.0.45
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    typescript: ^4.6.4 => 4.7.2

   I am currently using Chrome, I have not yet tested in FF or Safari

I'll leave it as a note here for anyone else. I've done a lot of various research, experimenting with babel configs, rollup/esbuild configs and lots of back and forth.
I did not solve the actual problem, but I did remove createPalette and am just returning an object with my palette config. That config does make it to the createTheme and should make its way there. As far as I can suspect is it might have to do with createPalette not actually being exported in the styles directory like others. I can't be sure but it's really the only difference between createTheme and createPalette code wise. Both have the same babel runtime import, so I have to venture a guess that the imports are in fact being transformed somewhere, how/where I have no idea.
So createPalette as of now in my view is a mui only tool and an end user shouldn't expect to use it straight. But rather send an object through the createTheme and it should pick up.
Actual Change:
const palette = {
    ...customPalette,

    primary: {
        main: designTokens.Theme.Primary.Main.value,
        light: designTokens.Theme.Primary.Light.value,
    },
    warning: {
        main: designTokens.Theme.Warning.Main.value,
        light: designTokens.Theme.Warning.Light.value,
    },
    info: {
        main: designTokens.Theme.Info.Main.value,
        light: designTokens.Theme.Info.Light.value,
    },
    success: {
        main: designTokens.Theme.Success.Main.value,
    },
    error: {
        main: designTokens.Theme.Error.Main.value,
        light: designTokens.Theme.Error.Light.value,
    },
    text: {
        primary: designTokens.Theme.Text.Primary.value,
        secondary: designTokens.Theme.Text.Secondary.value,
    },
    divider: designTokens.Theme.Divider.value,
    background: {
        paper: designTokens.Theme.Background.Paper.value,
        default: designTokens.Theme.Background.Default.value,
    },
}

export default palette

** Note: Only the palette itself changed, no more createPalette wrap.

I solved this by adding @babel/runtine to `serverDependenciesToBundle´ in remix.config.js.
serverDependenciesToBundle: [/^<EMAIL_ADDRESS>


Limit error size return from api to avoid size exceed error

{
  "message": "Failure exceeds size limit.",
  "source": "",
  "stackTrace": "",
  "encodedAttributes": null,
  "cause": {
    "message": "",
    "source": "GoSDK",
    "stackTrace": "",
    "encodedAttributes": null,
    "cause": null,
    "applicationFailureInfo": {
      "type": "STATE_API_FAIL_MAX_OUT_RETRY_ERROR_TYPE",
      "nonRetryable": false,
      "details": null
    }
  },
  "serverFailureInfo": {
    "nonRetryable": false
  }
}

We should truncate the error before returning back to activity result.
based on a convo with Temporal, there is a limit of 4K for activity failure. So we need to truncate it to 3K(to be safer because our error also have other stuff). The error message is composed in https://github.com/indeedeng/iwf/blob/064da989953c4102ec866e6e83de62b523a006c4/service/interpreter/activityImpl.go#L111 using "Sprintf"
See thread: https://temporalio.slack.com/archives/CTDTU3J4T/p1685675923648969

This is not a problem anymore within Indeed because we have an internal controller wrapper to truncate the error already, but we should still fix it in the server to prevent this and fixing it for the community

done https://github.com/indeedeng/iwf/pull/429


update python-certifi package to resolve CVE-2023-37920

Latest available triagebot image is affected by  CVE-2023-37920
Last image was built on 2023-06-11:
$ skopeo inspect docker://$(oc get pod/triagebot-15-dr2xt -o json | jq  '.spec.containers[0].image' | tr -d "\"") | jq '.Created'
"2023-06-11T00:00:46.376035372Z"

and contains vulnerable version 2023.5.7:
$ oc exec pod/triagebot-15-dr2xt pip-3 list | grep certifi
...
certifi            2023.5.7

It should be sufficient just to rebuild the image and push to quay.io (trigger GitHub workflow manually?). After rebuilding locally, the image uses certifi package version 2023.7.22 required by jira package which is not vulnerable according to this CVE:
# pipdeptree
...
jira==3.5.2
├── defusedxml [required: Any, installed: 0.7.1]
├── packaging [required: Any, installed: 23.1]
├── requests [required: >=2.10.0, installed: 2.31.0]
│   ├── certifi [required: >=2017.4.17, installed: 2023.7.22]
...
├── requests-oauthlib [required: >=1.1.0, installed: 1.3.1]
│   ├── oauthlib [required: >=3.0.0, installed: 3.2.2]
│   └── requests [required: >=2.0.0, installed: 2.31.0]
│       ├── certifi [required: >=2017.4.17, installed: 2023.7.22]
...
├── requests-toolbelt [required: Any, installed: 1.0.0]
│   └── requests [required: >=2.0.1,<3.0.0, installed: 2.31.0]
│       ├── certifi [required: >=2017.4.17, installed: 2023.7.22]
...

Thanks for the notification. We'll take a look.

$ skopeo inspect docker://$(oc get pod/triagebot-7ff7665754-8gtbm -o json | jq  '.spec.containers[0].image' | tr -d "\"") | jq '.Created'
"2023-09-13T14:50:14.469512649Z"
$ oc exec pod/triagebot-7ff7665754-8gtbm pip-3 list | grep certifi
certifi            2023.7.22
```


pull request for e2e test at 12/07/2016 10:45:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Success stories

Can anyone share his (or her) success story related to OpenSpiel ?
Especially for the board games (perfect, zero sum)

Hi @StepHaze, I'd prefer to use the Issues forum for actual OpenSpiel issue tracking.
Probably the best place for something like this is the discussions section:
https://github.com/google-deepmind/open_spiel/discussions

Ok, thank you


Update New-SPClaimTypeMapping.md

Added SharePoint 2010 applicability. Fixed example formatting.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/New-SPClaimTypeMapping.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Circular Linked List in JAVA

A circular linked list is a type of linked list where the last node's next pointer points back to the first node, creating a circular structure. Unlike a regular linked list, which has a null or "tail" pointer at the end, a circular linked list does not have a distinct end. This circular arrangement allows for continuous traversal and enables efficient operations on the list.
🛠 Issue (1402)
#1402
👨💻 Changes proposed
I have added solution and explanation to the problem of Circular Linked List
Made program menu driven.

✔ Check List (Check all the applicable boxes)

[✅] My code follows the code style of this project.
[✅] This PR does not contain plagiarized content.
[✅] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
Insert nodes into the list:
a. Create a new node with the given data.
b. If the head is null, make the new node the head and set its next pointer to itself, forming a circular reference.
c. If the head is not null, traverse the list until the last node is reached (i.e., the node whose next pointer points to the head).
d. Set the next pointer of the last node to the new node.
e. Set the next pointer of the new node to the head, completing the circular reference.
Traverse the circular linked list:
a. Set a temporary node variable to the head.
b. Start a loop that continues until the temporary node variable becomes equal to the head again (indicating completion of a full traversal).
c. Within the loop, process the data of the current node.
d. Update the temporary node variable to its next pointer for the next iteration.

📷 Screenshots

The update function is implemented. Please review it


Provide an elevation profile widget

It should work like the other widgets. Once the widget is activated and if a feature is selected it should perform the profile computation and display the result using a chart

Linked to https://github.com/kalisio/k2/issues/6.

Closed by https://github.com/kalisio/kdk/commit/7d579a39c8caa812d3e824c8e518cbb380ca5ea7.


Remove Create React App

The last release of Create React App was 5.0.1 in April 2022. react.dev no longer recommends it for starting new React projects.
For ease of maintenance, we should eject the configuration and build dependencies (Webpack, Jest etc.), then maintain them separately.

Just popping in to say that I'm finding Vite to be a very nice replacement for single page React apps that were built with CRA. Migration can be done in less than a day eg. https://github.com/pkpdapp-team/pkpdapp/pull/424.


#154 fix broken icon + remove huge dependency

What is this PR

Removed simple-icons dependency.
It's a huge library ~9Mb but we used only one SVG
Removed webpack settings for SVG files.
Looks like we don't need any specific settings for SVG with last wabpack4. It works out of the box. The previous settings caused broken images. But not sure that I'm not missing something important here.

Looks good to me!


failed to lookup transaction error

connection.execute triggers an internal server error on the following script:
START TRANSACTION;
CREATE MIGRATION test TO {
    module default {
        scalar type MyEnum extending enum<"A", "B">;
        type Row {
            property an_enum -> MyEnum;
        }
    }
};
COMMIT MIGRATION test;
COMMIT;

See also https://spectrum.chat/edgedb/general/struggling-with-enum-creating-with-python~274f6e6d-e45a-4b94-a430-652ddc89814e

Another instance of this error: https://spectrum.chat/edgedb/general/how-to-create-autoincrement-and-change-default-id-property-type~e05f7402-eb3d-438e-8e77-df582a9fa89c


CellType Inference : Facing CUDA Issue

I am running scGPT on Databricks environment using g5 Cluster Type, i have been facing multiple issues,
1 - I have created multiNode cluster but ony Driver Node GPU is being used in Training and Inference activity. is it something that is expected.
2- I have successfully fine tuned the model using one of my datasets, but facing below issue when i try to tun it for any other dataset. could you please let me know what is the possible cause of below error.
RuntimeError: CUDA error: CUBLAS_STATUS_NOT_INITIALIZED when calling cublasCreate(handle)

Hi @naveedaq91 , sorry for the waiting. To answer your questions:

I have not used the particular environment or g5 cluster so far, but were you running any one of the tutorial notebooks? Those notebooks by default would use one GPU. You probably need to make the node and GPU device accessible and explicitly put the model onto the specific device in the script. If you would like to share more information about the environment, I could try to help further

I personally have not met this error message before, but it looks like it could be triggered by dimension mismatch on some cloud gpus https://stackoverflow.com/questions/61473330/cuda-error-cublas-status-alloc-failed-when-calling-cublascreatehandle Let me know if this can solve your questions


NTR: ferroptosis

For the records. Stemming from review of the latest recommendations from the Nomenclature Committee on Cell Death (PMID: 25236395), I will add a new term as below:
name: ferroptosis
is_a: programmed cell death
def: A programmed cell death characterized morphologically by the presence of smaller than normal mitochondria with condensed mitochondrial membrane densities, reduction or vanishing of mitochondria crista, and outer mitochondrial membrane rupture. Activation of mitochondrial voltage-dependent anion channels and mitogen-activated protein kinases, upregulation of endoplasmic reticulum stress, and inhibition of cystine/glutamate antiporter are involved in the induction of ferroptosis. This process is characterized by the accumulation of lipid peroxidation products and lethal reactive oxygen species (ROS) derived from iron metabolism. Glutathione peroxidase 4 (GPX4), heat shock protein beta-1, and nuclear factor erythroid 2-related factor 2 function as negative regulators of ferroptosis by limiting ROS production and reducing cellular iron uptake, respectively. In contrast, NADPH oxidase and p53 act as positive regulators of ferroptosis by promotion of ROS production and inhibition of expression of SLC7A11 (a specific light-chain subunit of the cystine/glutamate antiporter), respectively. Misregulated ferroptosis has been implicated in multiple physiological and pathological processes.
dbxrefs: GOC:mtg_apoptosis, PMID: 25236395, PMID: 26794443
synonym: iron-dependent programmed cell death (related)

Added GO:0097707 ferroptosis


usb privileged version

Hey,
Perhaps you would be interested in a version that allows usb debugging and connecting an actual device to the docker container.
There's a security drawback - the container must run in privileged mode, which mean it has actual root access and it can't be that trusted. That's why I'm proposing this PR separately to another one I'm pushing simultaneously. If you have an idea on some kind of a switch I could add it later.
Best,
Mike

Hey, I'll be developing a little bit here - it seems not running fine any more with screen.

Did you know that it's possible to run adb over the network?
# On the host, run adb in daemon mode:
sudo adb -a fork-server server

# Inside the container, set an alias for adb (adb is used from the build path)
alias adb='/home/cmbuild/android/out/host/linux-x86/bin/adb -H <ip of your host>'

# Test:
adb devices

Works fine for me without any modifications to the Docker image.
However, we could still let users run Docker in privileged mode and forward the USB device. Ok with me, however this should be configurable right from the start. Can you update the PR please?

Besides this: The tests in front of mkdir don't belong to this change, do they?

Hey, yes I know you can run adb over network, but that means you need to have adb somehow installed on the host - the beauty of your docker image is that you needn't do that.
Anyway I added a -p / --privileged switch for this. I must check what makes screen not working, so this is not merge-able yet.

How about calling the flag --enable-usb? As a user, I don't need to know the relation with Dockers privileged mode, so this is otherwise not self-explaining.
Regarding the screen check: How about you're just leaving the line as it was before? No matter what, it's not related to this change, so it should be move into a different PR anyway. And then, this one could be merged right away...

How about this? :)

Thank you!

Ur welcome. :)
I have a branch that fixes docker #8755, but I don't think this should be merged to master - docker or ubuntu would fix that sooner or later. For now if anybody needs it, just cherry-pick my commit 5b769a7c.

Can you please take a look at https://github.com/stucki/docker-cyanogenmod/commit/6b6aba0a9329dc3d8dbb377c4f63595ec4e44bb1 + https://github.com/stucki/docker-cyanogenmod/commit/cfd61745106734a1b82f6c145900b4d5cf99ca08
I remember that I fixed a thing like this in the past, however I thought it was fixed, couldn't reproduce this with my Ubuntu 14.04.
In any case it would be good to create a new ticket if this is still needed. Therefore, I'm closing here.


fix: hide send message/unfriend buttons on friend list + tests

And some general clean ups from hardcoded messages to constants as agreed.
Closes #667

Looking here, it seems the cache updating is throttle to only happen every seconds, so I guess it's a race condition?
As a workaround, maybe set the local storage key to a constant, and then directly remove that from local storage on logout?

The workaround of interacting with directly in logout didn't work :( I suspect this might also be a bottleneck on how quickly local storage can accept write to disk? 🤷

Really don't want to get rid of offline cache sorry :P But this worked for me

Lol didn't know why I didn't try that first. Glad it was only a race condition and not some kinda disk write bottleneck! Fixed!


Update go-sev-guest to v0.9.2

This release includes improved validation support for machine stepping validation against the VCEK certificate.

FYI, we already have https://github.com/google/go-tpm-tools/pull/377. Both of these PRs have failing tests.

FYI, we already have #377. Both of these PRs have failing tests.

Ah I didn't see that one. Well I've fixed the breakage in this one.

I'm going to fix the testing defaults so this upgrade doesn't need a change to the tests.


Properly handle missing regions in URLS

NOTE: it is important that this fix gets into 4.9.3
re: Issue https://github.com/Unidata/netcdf-c/issues/2798
Modifications

Support the following AWS environment variables in the internal S3 library (they are already supported by aws-sdk-cpp).

AWS_REGION
AWS_DEFAULT_REGION
AWS_ACCESS_KEY_ID
AWS_CONFIG_FILE
AWS_PROFILE
AWS_SECRET_ACCESS_KEY
(source https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html).

Support an empty region when specifying s3.amazonaws.com as the host.
Move some S3/AWS related functions to ds3util.c
Add a test case to test empty region and AWS_[DEFAULT]_REGION.

Reviewing to merge, and then #2847


Support for the volume capacity limitations

Hi,
I currently start using lpp for sorting out mounts in optane disks as a cache, I was wondering if capacity limitations will be implemented. Currently lack of limitations might cause a cluster crashes what would not be acceptable in my solution.
Would you be able to provide any estimated timeframe for implementing this feature?
Thanks,
Jan

You can check the example/quota to see if it fits your expectation. But it only support xfs.

ext4 since linux 5.4 supports project quotas like xfs (which appears to be how the example xfs quota support works). btrfs seems to support quotas on subvolumes (which would seem to match the behaviour that's desired). Is there any reason the xfs support didn't become the default, and is currently an example, other than other file systems didn't have support at that time?


[Help wanted] updateFieldApperances - only works if using flatten method

I am trying to update fields after filling them with a custom font.  (Needed for special characters)
The fields only set the font if I flatten them.  Otherwise they default to Helvetica.  The problem I have is when using the Flatten method, ALL fields are affected by the font change which, for some reason, messes with check box fields.  (Could be the original PDF form that is the problem.  The info on the form indicates that it was created with a very old version of iTextSharp 5.5.3)
What I would like is just to set the font and/or update field appearances on text fields only when flattening.  Is this even possible?
Or, at least applying the form.defaultUpdateAppearances(myFont) without having to flatten.
I have tried many combinations and tried to dig through the documentation to get a satisfactory solution.
My sample code:
// save
// form.updateFieldAppearances(fontTimes) <- tried moving this down after the forEach()

// seems the function below is ignored
fields.forEach(field => field.enableReadOnly())
      fields.forEach(f => {
        if (field instanceof PDFTextField) {
          field.defaultUpdateAppearances(fontTimes)
        }
       field.enableReadOnly()
      })
form.updateFieldAppearances(fontTimes)
// form.flatten() <= enabling causes the checkbox fields to render inconsistently for some reason
// disabling form.flatten() prevents the font updating. 😞

      const pdfBytes = await pdfName.save()
      this.exportPDF(pdfBytes)

When enabling flatten() the following happens with some of the checkbox fields (but not all)
Some render like this:

Others like this:

If needed I could post the entire fill form function.
This is probably due to my inexperience, but I have no problem creating text fields and manipulating the font properties there, but filling out a form has been quite a challenge for me to set font properties.
textField.updateAppearances(myFont) returns undefined
I'm trying to figure out how to manipulate the text fields.  By setting the font and it's size etc without having to run the flatten function which messes up the check boxes.  (I suppose I could just replace the fields with a drawText() but what a lot of work to get the coordinates for 90+ fields.)
https://pdf-lib.js.org/docs/api/classes/pdftextfield#setfontsize
Says this:

This method depends upon the existence of a default appearance (/DA) string. If this field does not have a default appearance string, or that string does not contain a font size (via the Tf operator), then this method will throw an error.

I cannot for the life of me figure out where or how to set the default appearance string.  This may be the solution to my problems if I can figure this out.  Sorry to be so verbose.

I ended up just replacing all the fields with drawText() and had much more control that way.  The resulting pdf is not editable  afterwards anyway, so was trying to pound a square peg into a round hole.


Update SimpleGallery.java

Try to Fix nullException

the chrash get fixed with that
the images are not show
UnsignedBuild for test

@Kronos2308 It performs very well. When I use a proxy, the installation package you upload to the mega can log in correctly and load the image correctly. It passed my test.

whass alitle hell because one of the libraries got deprected and deleted
multiline-collapsingtoolbar-release.zip

I am a web application developer, so it seems that I may not be able to fully understand and solve this problem with Zen Master; but I believe you can solve this problem, come on

done

app-debug.zip

    public static String extToString(ImageExt ext) {
        switch (ext) {
            case GIF:
                return "gif";
            case PNG:
                return "png";
            case JPG:
                return "jpg";
            case WEBP:
                return "webp";
        }
        return null;
    }

    public static char extToChar(ImageExt imageExt) {
        switch (imageExt) {
            case GIF:
                return 'g';
            case PNG:
                return 'p';
            case JPG:
                return 'j';
            case WEBP:
                return 'w';
        }
        return '\0';
    }

    public static ImageExt charToExt(int ext) {
        switch (ext) {
            case 'g':
                return ImageExt.GIF;
            case 'p':
                return ImageExt.PNG;
            case 'j':
                return ImageExt.JPG;
            case 'w':
                return ImageExt.WEBP;
        }
        return null;
    }

It is an interesting application. I only have Notepad++, so I work with that.
you just need to add one more extension WEBP("webp")
but the app is programmed to work with extensions of 3 characters jpg png gif, webp has 4 characters so I just touched the part that arbitrarily takes the final 3 characters for something more flexible and then you just have to modify the regex, with which you search the files
and the functions that converted the extension into a character and the character into an extension
simply follow the functions from the inside out

Well done, so excited.


Get-CsPhoneNumberAssignment lacking parameter for unlimited / all results

Please add a Parmeter which allows the query of all phone number assignments rather than requiring an arbitrary integer of the max lookup amount.

@sofbkeller, you can always use value = "[type]::MaxValue" in such situations.
i.e.
Get-CsPhoneNumberAssignment -Top ([int]::MaxValue)

Thanks @shivtorov for that tip