Fail to fix broken database

I have just tried to a procedure to fix a broken database.   However, the step to re-create the database schema complains as follows:
# bundle exec rake redmine:plugins:migrate RAILS_ENV=production NAME=full_text_search VERSION=0
Migrating full_text_search (Full Text Search plugin)...
==<PHONE_NUMBER>2427 AddIndexToIssueContents: reverting ==========================
-- remove_index(:issue_contents, :contents)
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

Mysql2::Error: Table 'redmine.issue_contents' doesn't exist: SHOW KEYS FROM `issue_contents`
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `_query'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `block in query'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `handle_interrupt'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `query'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `block in execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:484:in `block in log'
/var/lib/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:478:in `log'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql2_adapter.rb:217:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:324:in `execute_and_free'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:448:in `indexes'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:637:in `index_name_exists?'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:993:in `index_name_for_remove'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:593:in `remove_index'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:665:in `block in method_missing'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:634:in `block in say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:634:in `say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:654:in `method_missing'
/var/lib/redmine-3.4.10/plugins/full_text_search/db/migrate/20170810052427_add_index_to_issue_contents.rb:31:in `block (2 levels) in change'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:515:in `down'
/var/lib/redmine-3.4.10/plugins/full_text_search/db/migrate/20170810052427_add_index_to_issue_contents.rb:30:in `block in change'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:547:in `block in reversible'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:746:in `execute_block'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:499:in `block in revert'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:498:in `each'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:498:in `revert'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:606:in `exec_migration'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:592:in `block (2 levels) in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:591:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:590:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:768:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1023:in `block in execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1071:in `ddl_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1022:in `execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:984:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:980:in `each'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:980:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:830:in `down'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:805:in `migrate'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:481:in `migrate_plugin'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:453:in `migrate'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:464:in `migrate'
/var/lib/redmine-3.4.10/lib/tasks/redmine.rake:135:in `block (3 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'

Caused by:
ActiveRecord::StatementInvalid: Mysql2::Error: Table 'redmine.issue_contents' doesn't exist: SHOW KEYS FROM `issue_contents`
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `_query'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `block in query'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `handle_interrupt'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `query'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `block in execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:484:in `block in log'
/var/lib/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:478:in `log'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql2_adapter.rb:217:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:324:in `execute_and_free'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:448:in `indexes'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:637:in `index_name_exists?'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:993:in `index_name_for_remove'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:593:in `remove_index'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:665:in `block in method_missing'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:634:in `block in say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:634:in `say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:654:in `method_missing'
/var/lib/redmine-3.4.10/plugins/full_text_search/db/migrate/20170810052427_add_index_to_issue_contents.rb:31:in `block (2 levels) in change'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:515:in `down'
/var/lib/redmine-3.4.10/plugins/full_text_search/db/migrate/20170810052427_add_index_to_issue_contents.rb:30:in `block in change'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:547:in `block in reversible'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:746:in `execute_block'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:499:in `block in revert'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:498:in `each'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:498:in `revert'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:606:in `exec_migration'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:592:in `block (2 levels) in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:591:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:590:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:768:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1023:in `block in execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1071:in `ddl_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1022:in `execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:984:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:980:in `each'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:980:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:830:in `down'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:805:in `migrate'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:481:in `migrate_plugin'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:453:in `migrate'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:464:in `migrate'
/var/lib/redmine-3.4.10/lib/tasks/redmine.rake:135:in `block (3 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'

Caused by:
Mysql2::Error: Table 'redmine.issue_contents' doesn't exist
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `_query'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `block in query'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `handle_interrupt'
/var/lib/gems/2.3.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `query'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `block in execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:484:in `block in log'
/var/lib/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_adapter.rb:478:in `log'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql2_adapter.rb:217:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:324:in `execute_and_free'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:448:in `indexes'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:637:in `index_name_exists?'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:993:in `index_name_for_remove'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/schema_statements.rb:593:in `remove_index'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:665:in `block in method_missing'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:634:in `block in say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:634:in `say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:654:in `method_missing'
/var/lib/redmine-3.4.10/plugins/full_text_search/db/migrate/20170810052427_add_index_to_issue_contents.rb:31:in `block (2 levels) in change'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:515:in `down'
/var/lib/redmine-3.4.10/plugins/full_text_search/db/migrate/20170810052427_add_index_to_issue_contents.rb:30:in `block in change'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:547:in `block in reversible'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:746:in `execute_block'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:499:in `block in revert'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:498:in `each'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:498:in `revert'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:606:in `exec_migration'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:592:in `block (2 levels) in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:591:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:590:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:768:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1023:in `block in execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1071:in `ddl_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:1022:in `execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:984:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:980:in `each'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:980:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:830:in `down'
/var/lib/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:805:in `migrate'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:481:in `migrate_plugin'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:453:in `migrate'
/var/lib/redmine-3.4.10/lib/redmine/plugin.rb:464:in `migrate'
/var/lib/redmine-3.4.10/lib/tasks/redmine.rake:135:in `block (3 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
Tasks: TOP => redmine:plugins:migrate
(See full trace by running task with --trace)

What should I do?

It has been fixed on master.
You can use master when we upgrade your Redmine to 4.0.

Following your comment, I tried the master on Redmine 4.0.5.
StandardError: An error has occurred, all later migrations canceled:

Mysql2::Error: Unknown table 'redmine.issue_contents': DROP TABLE `issue_contents`
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in `_query'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in `block in query'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:130:in `handle_interrupt'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:130:in `query'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:187:in `block (2 levels) in execute'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:186:in `block in execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:581:in `block (2 levels) in log'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:580:in `block in log'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:571:in `log'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:185:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/mysql/database_statements.rb:28:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:340:in `drop_table'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:871:in `block in method_missing'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:840:in `block in say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:840:in `say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:860:in `method_missing'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:687:in `block in revert'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:686:in `each'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:686:in `revert'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:812:in `exec_migration'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:798:in `block (2 levels) in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:797:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `with_connection'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:796:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:977:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1292:in `block in execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1345:in `ddl_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1291:in `execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1263:in `block in migrate_without_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1262:in `each'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1262:in `migrate_without_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1210:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1363:in `with_advisory_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1210:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:514:in `down'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1015:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:536:in `migrate_plugin'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:477:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:488:in `migrate'
/var/lib/redmine-4.0.5/lib/tasks/redmine.rake:135:in `block (3 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-13.0.0/exe/rake:27:in `<top (required)>'

Caused by:
ActiveRecord::StatementInvalid: Mysql2::Error: Unknown table 'redmine.issue_contents': DROP TABLE `issue_contents`
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in `_query'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in `block in query'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:130:in `handle_interrupt'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:130:in `query'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:187:in `block (2 levels) in execute'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:186:in `block in execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:581:in `block (2 levels) in log'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:580:in `block in log'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:571:in `log'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:185:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/mysql/database_statements.rb:28:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:340:in `drop_table'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:871:in `block in method_missing'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:840:in `block in say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:840:in `say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:860:in `method_missing'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:687:in `block in revert'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:686:in `each'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:686:in `revert'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:812:in `exec_migration'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:798:in `block (2 levels) in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:797:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `with_connection'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:796:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:977:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1292:in `block in execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1345:in `ddl_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1291:in `execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1263:in `block in migrate_without_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1262:in `each'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1262:in `migrate_without_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1210:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1363:in `with_advisory_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1210:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:514:in `down'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1015:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:536:in `migrate_plugin'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:477:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:488:in `migrate'
/var/lib/redmine-4.0.5/lib/tasks/redmine.rake:135:in `block (3 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-13.0.0/exe/rake:27:in `<top (required)>'

Caused by:
Mysql2::Error: Unknown table 'redmine.issue_contents'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in `_query'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:131:in `block in query'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:130:in `handle_interrupt'
/var/lib/gems/2.3.0/gems/mysql2-0.5.2/lib/mysql2/client.rb:130:in `query'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:187:in `block (2 levels) in execute'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:186:in `block in execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:581:in `block (2 levels) in log'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:580:in `block in log'
/var/lib/gems/2.3.0/gems/activesupport-5.2.3/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_adapter.rb:571:in `log'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:185:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/mysql/database_statements.rb:28:in `execute'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:340:in `drop_table'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:871:in `block in method_missing'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:840:in `block in say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:840:in `say_with_time'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:860:in `method_missing'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:687:in `block in revert'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:686:in `each'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:686:in `revert'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:812:in `exec_migration'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:798:in `block (2 levels) in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:797:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `with_connection'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:796:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:977:in `migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1292:in `block in execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1345:in `ddl_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1291:in `execute_migration_in_transaction'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1263:in `block in migrate_without_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1262:in `each'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1262:in `migrate_without_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1210:in `block in migrate'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1363:in `with_advisory_lock'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1210:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:514:in `down'
/var/lib/gems/2.3.0/gems/activerecord-5.2.3/lib/active_record/migration.rb:1015:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:536:in `migrate_plugin'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:477:in `migrate'
/var/lib/redmine-4.0.5/lib/redmine/plugin.rb:488:in `migrate'
/var/lib/redmine-4.0.5/lib/tasks/redmine.rake:135:in `block (3 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-13.0.0/exe/rake:27:in `<top (required)>'
Tasks: TOP => redmine:plugins:migrate
(See full trace by running task with --trace)

I've added more checks for no table case.
Could you try again with the current master?

Thanks a lot.


vgplot('hist') does not respond to bins, shows wrong tooltip on stepfilled

fixed first one locally, need to look into second

also something with Y axis scaling  - historgams in my case are too low (perhaps because I have plenty of nans) :-/

Note that Vega-Lite 3 changes treatments on invalid values to make it better.


Bl/session refactor

Quick refactor of client/session.go, breaking it up into multiple files by type.

Coverage decreased (-0.1%) to 77.801% when pulling 9b0f0eb66b5ddd57962cb4be87784a72fdcf1ac1 on bl/session-refactor into 2a105907f8a159e94ca6ffc57f4c733a93805204 on master.


How to support both xsave and avx feature in guest cpu with haxm?

CPUID vm exit handler should set feature bits corresponding to support of these features. For example XSAVE support is returned in ecx of cpuid 1 (FEATURE(XSAVE)) and cpuid 0xd should return additional info about the area size used by XSAVE. Same for AVX. There were also settings that allow to handle XSAVE executions in the guest as vm exits.
For a complete set of requirements see Intel docs.

thx! Does haxm plan to support it in future version?

Intel's plan is to support Android emulator on windows hosts. Android emulator does not need these features, thus I dont think they will be added in the future.


#71: Add patch to fix tidy extension and PHP 5.6.

This PR:

[x] Fix #71
[x] Add a new local patch (couldn't find a better online source)

Would be nice to add it to the CI build list.


Unavailable checkout.min.js/checkout.js

Description
Can not get checkout.js:
https://www.paypalobjects.com/api/checkout.min.js and https://www.paypalobjects.com/api/checkout.js returns 404 error
Steps to reproduce
Try to get https://www.paypalobjects.com/api/checkout.min.js
It returns 404
nslookup and curl output:
host-174:~ borman$ nslookup www.paypalobjects.com
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Non-authoritative answer:
www.paypalobjects.com	canonical name = geo.paypalobjects.com.akadns.net.
geo.paypalobjects.com.akadns.net	canonical name = pprussia.www.direct.paypalobjects.com.akadns.net.
Name:	pprussia.www.direct.paypalobjects.com.akadns.net
Address: <IP_ADDRESS>

host-174:~ borman$ curl https://www.paypalobjects.com/api/checkout.min.js
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>404 Not Found</title>

Not Found

The requested URL /api/checkout.min.js was not found on this server.

Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.

Affected browsers

[+] Chrome
[+] Safari
[+] Firefox
[+] Edge
[+] IE
[+] Chrome Mobile/Tablet
[+] Safari Mobile/Tablet
[+] Web View / Safari ViewController
[+] Other

Can not get checkout.js:
https://www.paypalobjects.com/api/checkout.min.js and https://www.paypalobjects.com/api/checkout.js returns 404 error

@bormanEcwid These links open for me when typed in the address bar in the browser.

Now I can not reproduce it.
But when I posted ticket paypal returned 404
Are you sure that it will not happen again?

Please raise another issue if you see the same problem again.

Why dit it happen?
Can I be sure that it will not happen again?


v5 breaking change to init.

See the release notes for details. This PR adds the initialize() function for better control and testing.

:tada: This PR is included in version 4.7.3 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Add the posibility to build aplications for other SUBSYSTEMS

Right now bob only builds aplications for the CONSOLE subsystem, it would be nice to add a keyword to the build config file that specifies the target subsystem.
see: https://msdn.microsoft.com/en-us/library/fcc1zstk.aspx

Done in: c9eee5bd480d1b964b4b710d6766a4bc9cc8f070
Will update the wiki in a few hours.


Provide Official XML Schema for MuJoCo Files

It would be helpful for bindings developers to have an officially supported set of XML schema files to validated MuJoCo XML files. This repository has the schema through 2.x https://github.com/ronansgd/xml-schema-mjcf
It would be very helpful if these were adopted and kept up to date with any XML changes.
I am doing my best to add and correct the schema for use in the Java bindings. I will likely maintain a fork, even if it is out of date.
These schema files could be used by many different language implementations to validate a generated XML file, and used to generate marshaling and unmarshaling code for MuJoCo XML models.

Any thoughts on the preferred schema format?

duplicate of #6 (that's how long we want to do this! 🙂)
Following up on @saran-t, specifically, there are three obvious candidates, XSD, relaxNG (RNG) and relaxNG-compact (RNC). RNC is by far the most beautiful but also the least commonly supported. AFAICT, both XSD and RNG are fairly widely supported, yet RNG is far more flexible.
For this to worth our while we would need to replace the struct at the top of xml_native_reader.cc as the source of truth for the MJCF schema.
I believe the plan was to

Pick a schema format.
Look at available validating XML parsers (e.g. this one), see if any of them is significantly faster/better than tinyXML2. Note that a new, validating XML parser is not a hard requirement. We can just use tinyXML2, since we don't intend to have very much information in the schema file, there are far too many things in MJCF that are not representable by any schema language.
Rewrite xml_native_reader to use the schema file rather than the struct.

We got stuck at step 1 🙂
Closing since #6 is still open, but obviously this is not resolved.


Adding accounts by using clone function issue

I have added several accounts to launchbuddy using the clone function for faster creation by having all the settings similar (cloned) and then setting login files for each alt seperately through the "Login credentials". For each account I of course added its own appropriate login credentials after the login client opens, I enter the credentials and then it closes (as it should). But upon starting multiple alt clients all of them login to the same account that it has been cloned from.
So for example:

I create alt 1, set all settings + login credentials
I clone alt 2 from alt 1 -> change its login credentials
I clone alt 3 from alt 2 -> change its login credentials
repeat so forth

Then upon starting alt1,2,3 simultaneously they all use the credentials from alt 1. Which eventually results in a lock-out from logging in alt 1 with an {{undefined}} login-client error.

Duplicate:
https://github.com/TheCheatsrichter/Gw2_Launchbuddy/issues/235#issuecomment-988328571
Known issue. On the ToDo list for 2.4.3


Unable to sort by hybrid properties - example

reproduced the problem #36
example of @hybrid_property
unable to sort by @hybrid_property field

Coverage remained the same at 88.083% when pulling 57734d5c769bb4afc0b491712c581ac44b10be9c on ufoczek:hybrid_property into 14d058a4e613c55d8098ee93c871d54471961149 on Pegase745:master.

I think this issue was solved for > 1.0.0


Get-Accounts call fails on some Sources because the underlying API call is returning two 'immutableID' attributes with different casing

Setup: Powershell SDK connected to a tenant with Azure AD source
Steps to Reproduce:
Run small sample script that calls Get-Accounts and filters for the Azure AD source:
Get-Accounts -Filters "sourceId eq ""5d7baaaaaaaaaaaacdf6008d7d41"""
Expected Results: The cmdlet should run and return accounts from that source ID.
Actual Results: The cmdlet returns an error:

ConvertFrom-Json: ...\PowerShell\Modules\PSSailpoint\1.1.1\cc\src\PSSailpointCC\Private\CCApiClient.ps1:269
Line |
269 |          return ConvertFrom-Json $Response
|                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot convert the JSON string because it contains keys with different casing. Please use the -AsHashTable
| switch instead. The key that was attempted to be added to the existing key 'ImmutableId' was 'immutableId'.

The properties on powershell objects are case insensitive so the ConvertFrom-Json call fails because Azure AD accounts are returning two different attributes that only differ in casing: immutableId and ImmutableId.  This seems like it might be a bug in the underlying API call, I can see both immutableId and ImmutableId being returned in the bare /v3/accounts call in postman, and they both have the same value.

@bradgrutsch,
This is fixed in https://github.com/sailpoint-oss/powershell-sdk/commit/5df140c64e9dde6f6871643df67f7685f79baa99.
I updated the SDK to use the -AsHashTable switch when calling ConvertFrom-Json. This will allow both casings to be present within the PSObject.
Thank you for bringing this to our attention!


How to send array of object

Hi,  i have tried these two methods below but i still can't get it done, it always send array of object as a string instead of array of object. may i know is there any possible solution for this problem?
Method#1
  var data  = $scope.dealsData;
  Upload.upload({
                  url: '/api/postDeals',
                  fields:data,
                  data:{favour:$scope.choices},
                  file: file
              }

in my nodejs console
{ deals_name: 'ad',
  deals_price: '12.12',
  deals_amount: '12',
  deals_description: 'asd',
  deals_term_condition: 'asd',
  favour_type: 'survey',
  data: '{"favour":[{"type":"mcq","$$hashKey":"object:67","mcq_question":"asd","mcq_choice1":"asd","mcq_choice2":"asd"},{"type":"open_ended","$$hashKey":"object:68","open_ended_question":"asd"}]}' }

if i do it the usual way i don't have the $$hashkey or object:6x thingy in my json
Method#2
$scope.dealsData.favour =  angular.toJson($scope.choices);
var data  = $scope.dealsData;
  Upload.upload({
                  url: '/api/postDeals',
                  fields:data,
                  file: file
              }

in my nodejs console
{ deals_name: 'asd',
  deals_price: '12.12',
  deals_amount: '12',
  deals_description: 'asd',
  deals_term_condition: 'asd',
  favour_type: 'survey',
  favour: '[{"type":"mcq","mcq_question":"asd","mcq_choice1":"asd","mcq_choice2":"asd"},{"type":"open_ended","open_ended_question":"asd"}]' }

User fields: myData and sendFieldsAs: form.

I try this and array is sended as object:
array_name: {0: value1, 1: value2}

How can I send as array?

@rjurado01  i ended up doing this to solve this problem
in controller
  var data = {
    business_tags:angular.toJson($scope.tags)
  }

in backend node.js
  // assign jsonstring to myJSONString
  var myJSONString = data.business_tags;
  // convert it to array of object
  var myObject = JSON.parse(myJSONString);
  // assign to myOBject
  data["business_tags"] = myObject;

however i think you can do it solely in controller.
hope this help

@danialfarid This issue is still present. We have missed the condition angular.isArray() here.

@kuldeepaggarwal What is the issue?

Cases:
Case 1:
when fields are object,
var val = { "name": 'kuldeep Aggarwal' }
Upload.upload({
  fields: val
})

then the code is send correct params: {fields: {"name": "Kuldeep Aggarwal"}}
Case 2:
when fields are array:
var val = [{"name": "kuldeep Aggarwal"}]
i.e.
Upload.upload({
  fields: val
})

then the code send incorrect params => {fields: {"0": { "name": "Kuldeep Aggarwal" }}}
instead it should send params => {fields: [{"name": "Kuldeep Aggarwal"}] }
So, if you think my assumption is write then I would like to contribute and create a PR for this issue.

fields is deprecated. Use data instead.

Okay,, so data handles all the aforementioned scenarios?

Just had the same issue. As per the docs using arrayKey: '[]' solved the issue for me e.g.
Upload.upload({   data: val,   arrayKey: '[]' })

Hi,
I am also having the same issue and also try to use arrayKey:'[]' but its didn't resolved.
I am trying to upload multiple files with some body data, and the body data contains some array of objects.
But in the backed I am getting a single object in array with comma separated values.
Upload.upload({
          url:configuration.PACKAGE_URL,
	  arrayKey: '',
	 data: { data : $scope.packages, file : files}
	   })

and $scope.packages is
  {
                       "packs": [{
			"i_name": "Tax",
			"i_code": "2"
		}, {
			"i_name": "Fli",
			"i_code": "3"
		}],
		"type": "Katt",
         	"category": "Low"
}

But in request body in backend I am getting request
"packs" : [
        {
            "i_name" : "Tax,Fli",
            "i_code" : "2,3",
           "$hashKey":"object:51"

        }
    ],
     "type": "Katt",
      "category": "Low"


build(swc_core)!: bump<EMAIL_ADDRESS>

Ident was replaced with IdentName and Ident was constructed without ctxt to conform<EMAIL_ADDRESS>All tests passed (on my machine 😄).
I've tested it in our company project with<EMAIL_ADDRESS>as CONTRIBUTING guide suggests. Both build and dev seem to work without any issue.
I am not sure if I am supposed to add something to the README compatibility table. I think that it should be changed when new version is being released, right?

Thanks for the contribution. Generally, we align the plugin releases to latest stable version of nextjs. This is not ideal, but at least that make it work out of the box for people how starting the project and didn't read the instructions thoroughly.
But latest 4.0.9 already sabotaging this rule (it will work only with next@15-canary), so don't see anything against releasing this version as well.

@thekip That's actually something I kinda expected that you're doing. And honestly I don't think that there is ideal solution to that. One might be forking it and maintaining "version" that aligns with rspack while the main repo would be aligned with next. However I think that it would make very difficult to sync features very soon as swc core seems to be releasing breaking changes almost nightly. Unfortunately it even cannot be expected that rspack won't upgrade swc core as it's under experimental configuration so I think they won't mind introducing breaking changes even in non-major releases.
However I am really up to migrating to rspack so wouldn't you be accepting this PR in the end, I would be most grateful if you shared any idea how to bring rspack compatible version (fork/branch/...) alive. I got almost none XP with libs so you might know better. Thanks and thanks for maintaining this lib!

You can take a binary from the output folder and simply put it into your repository, and start using it without waiting to get this merged. The plugins compatibility is a big pain now, unfortunately. I hope they will focus on this issue some day and will find a way how to make it without breaking changes. Interestingly that so many different bundlers/tools right now use SWC under the hood, and it seems they do not actively help to developing it, unfortunately.

@thekip I don't think that it's worth creating issue, so I'll just drop it here:
There is a website that helps people select the right version of swc plugin. I haven't found if it's possible to contribute to the list however the list is pretty new as I understand, so IF they open the contrib, it might be useful. https://plugins.swc.rs/

@dominikdosoudil interesting, the lingui plugin is already in the list. SWC maintainers aware of us 👍. Thanks for the link.

it seems it's here and should pick up version automatically
https://github.com/swc-project/crawl-core-version/blob/main/pkgs/plugins/lingui-js.yml

I see, well there seems to be some issue coz I use<EMAIL_ADDRESS>which works with<EMAIL_ADDRESS>and it's not listed there if I select this version of rspack. That's why I thought that lingui is not there at all. I might look at it closer when I am back from vacation.

Where is verison 4.0.9, is it unpublished?

🤨 @czizzy indeed, it wasn't published yet.  @andrii-bodnar Could you make a release from a current main branch, please?

@timofei-iatsenko just to double-check
Currently, we have swc_core version 0.96.9 in the main branch.
On the next branch we have 0.90.35. But we used to have 0.96.9 in the next branch, then we reverted it back due to some risks (#105).
So, should we release the main branch which contains swc_core 0.96.9?

Yes, newer SWC version in the next branch blocking testing v5 features for the devs. In the v4 branch there no such problem.

Done - 4.0.9

@timofei-iatsenko The latest version of Rspack uses the new version of swc_core 0.99.5. It is not compatible with lingui/swc-plugin 4.0.9 plugin version. Will it be updated soon?

@andrii-bodnar let's now deploy another version with a swc_core from this PR.

4.1.0?

Last bump was patch so 4.0.10 seems more consistent. Even though it’s actually breaking change from my perspective.

@dominikdosoudil why is this a breaking change? Will it affect @lingui/swc-plugin users somehow?

It's a breaking in some way, but we don't follow it for SWC bumps

@andrii-bodnar imho because developer cannot blindly upgrade the plug-in without checking the compatibility table. Compilation would probably stop working. But because swc plugins are still kinda experimental and punk, it does not matter that much.

Hi, I've just updated but it doesn't seem to work with version 14.2.11 of next.


Fix by indices bug

Coverage increased (+0.1%) to 72.02% when pulling 8d38744d82b90b468f328535d05b3c33a0322ac6 on fixByIndicesBug into 4ce03d17e50e4f14e1ec751cddaa8e5ce6d91d42 on master.

Coverage increased (+0.1%) to 72.02% when pulling 8d38744d82b90b468f328535d05b3c33a0322ac6 on fixByIndicesBug into 4ce03d17e50e4f14e1ec751cddaa8e5ce6d91d42 on master.


I can deploy a DMN file directly from the Camunda Modeler

As a Camunda Modeler user
Given:
I create a DMN decision table or decision requirements graph
Then:

[ ] I can click a button in the menu bar to deploy directly the DMN file.
[ ] I can configure the process engine API url.

So That:
I don't need to write any Java code to bundle a process application.

@nikku since this is based on 730, it is rebased on it. Therefore, if this ever gets merged to master all what is needed to do is to drop the 730 commit before merging.

Closed via https://github.com/camunda/camunda-modeler/commit/b09ff8daa2ec61dc25331dedde2a4018ffcb0cd4.


How to transfer a file from the command line.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@Nathan-Abegaz, sorry, but from what I gather this isn't a native command in Mac OS. I believe this is using transfer.sh instead, so it's not a great fit for this article about simple terminal commands. I'll have to close this, but please feel free to write an article about transfer.sh with some examples instead!


ENH: update package version

Hi! This is the friendly automated conda-forge-webservice.
I've started a version update as instructed in #106.
I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!
Fixes #106

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12428835278. Examine the logs at this URL for more detail.

Superseded / replaced by https://github.com/conda-forge/mcxtrace-suite-feedstock/pull/108


run Tick later

What's the reason of running the set spawner type 5 ticks after only? why not make it 1t or 2t

I have changed it. Thanks.

Hey Cornelius, I am sorry for the long response, I completely lost this, I just tried and lgtm awesome! Good job

This has actually fixed one issue we were had and I just thought about it, players were saying that their iron golem spawners were becoming PIGS all the time, and that's actually to me what it seems to be a tick issue, where he would be able to place the spawner and break it really fast at the same time, before the spawner even got set to the mob type.
Sounds like possible? woudln't happen for high latnecy players but most of our network holds players with < 50ms


Remove-GitLabProject Support Pipeline

Remove-GitLabProject says it supports pipeline parameters but only removes the first one you give it. This has to be fixed.
https://github.com/ngetchell/PSGitLab/blame/master/PSGitLab/Public/Projects/Remove-GitLabProject.ps1#L18-L29

Should this issue have been closed by #61?

Correct. Confirmed that this is no longer working on 2.3.1.


chore(doc): change api doc directory struct

What this PR does / why we need it:
chore(doc): change api doc directory struct
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @gaocegege @simon-cj

Release note:

NONE

/lgtm


CFG and Convergence

Hi,
Thanks for your awesome work!!!
May I ask the convergence under other cfg scales? Your results demonstrate model divergence without CFG. In my experiments, I observed that even with FID margin at CFG=1.0 (which is equivalent to no guidance), the optimal performance remains relatively similar across scales.

Hi, thanks for your interest! Are you asking for FID curve with respect to training iteration with cfg?

Thanks for your quick reply!
Take the result as an example. If we were to traverse various CFG scales to identify the optimal FID, what would be the observed gap? In other words, different models trained under various settings might prefer different scales - some favoring larger scales, others smaller ones. I'm particularly interested in understanding how these training recipes affect both the optimal scale and the resulting optimal FID. And whether the FID w/o CFG can really reflect the model convergence. :-)

Thanks for the clarification. My experience is that REPA still shows considerable improvement w/ cfg (see Table 2 for an example). I have not taken analysis in how the optimal coefficient becomes different --- according to my experience it seems the optimal cfg value is quite to the original DiT/SiTs.  Also I think exploring whether the FID w/o CFG can really reflect the model convergence is an important and interesting future direction!


Create logs for installed integrations & instrumentation

We need to have a local log file of all the integrations that have been installed.I think it would just be a perpetual log file that keeps track of everything executed during the install process, meaning it wouldn't be overwritten.
If the installer is run again, we could consider putting that into another log file. In other words, each log file could be named something like NRInstallLog_timestamp and correspond to one "run" of the install.
Aha! Link: https://newrelic.aha.io/features/VIRTUOSO-92

updated with a few clarifying requirements.


[question] How to "deep" parse schema that contains JSON string?

I'm using Zod to validate HTTP request that contains JSON data. Currently, I'm using a pattern like the one that follows (simplified, for readability):
const z = require('zod')
const payloadSchema = z.object({ name: z.string(), age: z.number().min(18) })
const requestSchema = z.object({ payload: z.string() })
// ...

const req = requestSchema.parse(request)
const raw = JSON.parse(req.payload)
const payload = payloadSchema.parse(raw)

console.log(payload.name) // << this is what I'm interested into

Would there be a more strait-forward way to deep parse a shape that contains JSON string that I don't know of?
const z = require('zod')
const payloadSchema = z.object({ name: z.string(), age: z.number().min(18) })
const requestSchema = z.object({ payload: z.string().json(payloadSchema) })
// ...

const req = requestSchema.parse(request)
console.log(req.payload.name) // << this is what I'm interested into

-- this question was also posted in stackoverflow.

The recommended approach here is to use preprocess to parse the payload before validation.
const requestSchema = z.object({
  payload: z.preprocess(
    (val) => (typeof val === "string" ? JSON.parse(val) : {}),
    z.object({ name: z.string(), age: z.number().min(18) })
  ),
});

const req = requestSchema.parse({payload:"whatevs"});
req.payload.name;


Add 30 day after year end checking for wash

Washes should be checked in the next 30 days of the next year. This introduces the concept of a year into logic. Currently code is agnostic to what times it runs for. Not sure the best way to determine this, but I my first thought is to use the time stamp of the basis trades coming to determine what tax year is being processed.
If a basis trade is passed to the TradeProcessor with a timestamp between the end of the current tax year being processed and 30 days after the current tax year, check to see if it washes a loss from the current tax year and count it as a loss if it does.

When these trades are processed, they really should be stored for future consideration without counting them as basis trades. You wouldn't want to double count these wash buy backs against losses twice, but also need to consider them for losses in their respective tax year, a note would also be nice so that when examining the basis, no one thinks that the extra trades listed for next years taxes are getting added in to inflate the basis.


build deribit with FIX error

Hi,
I am trying to build deribit exchange with FIX enabled (CCAPI_ENABLE_SERVICE_FIX). The build fails in ccapi_session.h in line 230:
#ifdef CCAPI_ENABLE_EXCHANGE_DERIBIT
#include "ccapi_cpp/service/ccapi_fix_service_deribit.h"
#endif
https://github.com/crypto-chassis/ccapi/blob/develop/include/ccapi_cpp/ccapi_session.h#L230
It seems ccapi_fix_service_deribit does not exist in the code.

In Readme, the supported exchanges for FIX API are coinbase, gemini. We would welcome a PR to add deribit.


Angular Universal Does not work with some plugins

Dear Mohammad,
Thanks for this post it is really helpful, but I have a problem when I use plugins like ngx-scrollspy or ng2-scroll-to-el and run the command npm run serve:universal i got this error:
universal-cli-starter-master\node_modules\ngx-scrollspy\dist\core\service.js:1
(function (exports, require, module, __filename, __dirname) { import { Injectable, EventEmitter } from '@angular/core';
                                                              ^^^^^^
SyntaxError: Unexpected token import
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.2IYf (C:\Users\ABlaybel\Desktop\test angular 2\universal\10-2-2017\universal-cli-starter-master\dist\dist-server\main.bundle.js:1:649)

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "serve:universal"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>serve:universal: `npm run build:universal && cd dist && node server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>serve:universal script 'npm run build:universal && cd dist && node server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the universal-cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build:universal && cd dist && node server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs universal-cli
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls universal-cli
npm ERR! There is likely additional logging output above.

Hey,
You're welcome.
Unfortunately, some modules cause problems with server-side rendering!
For scroll, I use ngx-infinite-scroll which works as expected in my case.


User custom hover at iconLabel level

Fixes #106095 and https://github.com/microsoft/vscode/issues/107277

thousands of elements

It's more like tens of elements, since only the ones inside the viewport are rendered. At most, double of that since the user can be really fast at scrolling.

To give an example where I try to reduce listeners for large sets of items: ResourceLabels is a way to have only 1 listener for a large group of labels instead of having 1 per label

I was never convinced that ResourceLabels was actually better. And now that I think about it, I can only conclude that it is useful only for avoiding the event listener leak warning and saving a bit of memory in creating callback functions. Note:

Normal: Each label adds a callback to the event callback list. When the event fires, it loops over the list and calls the callbacks. In summary, there are N callbacks created and there are N callbacks invoked. Instead of using () => this.method() when attaching to the event, we can also use this.method.bind(this) instead, saving that extra callback. So given that, there are zero callbacks created and N methods invoked.
With ResourceLabels: Each label adds itself to the ResourceLabels list. When the event fires, it calls the ResourceLabels callback, which loops over the list and calls a method on each label. In summary, there are zero callbacks created and there are N methods invoked.

I might be overlooking something here, let me know.

@bpasero I think I have addressed all your comments.

we can also use this.method.bind(this) instead, saving that extra callback

@joaomoreno re https://github.com/microsoft/vscode/pull/108403#issuecomment-707502276
and  fyi that bind does create a new function. So, yes one less invocation but not one less function. IMO the best is to use Function#apply

And now that I think about it, I can only conclude that it is useful only for avoiding the event listener leak warning and saving a bit of memory in creating callback functions

Some history/background: We obviously did not do that to prevent a listener leak warning or for saving callback functions. The rational was that there where many, many listeners doing exactly the same thing - needed or not. For instance, all label instances would listen to theme changes, no matter if they are visible on screen or not. Or all listeners would have the same if-if-if-then-sequences to know that something needs to be redrawn. Executing if-if-if-then 500 times or once is a difference. Finally, it also matters how many listeners you attach/detach to the DOM but what matters more if all listeners are doing the same thing at the same event/time or not.

IMO the best is to use Function#apply

I'm not sure how to do this. I don't have all the arguments for the function at the time that I call apply because the MouseEvent comes from a dom event. @bpasero or @jrieken can you show me what I'm missing?

Created https://github.com/microsoft/vscode/issues/109231 and https://github.com/microsoft/vscode/issues/109233 so we don't lose the follow ups.


WoW ! Thank you . this is just what i was looking for

Great work .
I'll kick the tires on it  a little to test it.
I'm really looking forward to collaborate on this
⭐

I'd loved to help write up the installation guide.
I would assume i just drop it in to the components folder just like VC_Framework ?

all plugins are installed in the same manner.
https://doc.4d.com/4Dv17R4/4D/17-R4/Installing-plugins-or-components.300-4085753.en.html
quite similar to components:
https://doc.4d.com/4Dv17R4/4D/17-R4/Overview.300-4085682.en.html
the main difference is the language used (C or 4D)

Awesome,  I'll take it for a spin tomorrow, we're running on v16.

Neat.
I was able to sign a token and verify it on jwt.io
but not  the othe way around. I created the token on the jwt.io and paste it in 4d along with the secret.
I think I'm doing it right,
did I mess up ?

$token:="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoiMTUxNjIzOTAyMiJ9.NTghxvd6D0DCZNZxlLf9U1wSJHxsA-m17OAOwcKKgzA"

$result:=JWT Verify ($token;"your-256-bit-secret")  // => 0

honestly I haven't thoroughly tested the "verify" command since we didn't need it for our project.
you can find my messy code in
https://github.com/miyako/4d-plugin-jwt/blob/master/4DPlugin.cpp


##Change order.jsp.##

To implement Dao in this project we first need to change order.jsp. This should be done as per the given conditions in #6.

Drop Down
File Name

Beverages
Beverages.jsp

Snacks
Snacks.jsp

Starters
Starters.jsp

Main menu
Main_Menu.jsp

Rice
Rice.jsp

Desserts
Desserts.jsp

Create separate Tables for a particular menu dropdown and paste the same

this fixes #15


Sporadic visual issues with NVidia GeForce RTX graphics cards

A user reported a random visual glitch in the middle of playing. They tabbed out to look for a screen shot, and went back and it looked like this.
The user has a NVIDIA GeForce RTX 2070.
Additional logs:
Scene changing; unassigning CurrentLevel.puzzle.
Finished unassigning CurrentLevel.puzzle.
Changing scene to [PackedScene:40016] (res://src/main/career/ui/CareerRegionSelectMenu.tscn) valid=True
tree.change_scene_to returned 0
ERROR: GL ERROR: Source: OpenGL Type: Error     ID: 1282        Severity: High  Message: GL_INVALID_OPERATION error generated. Texture name does not refer to a texture object generated by OpenGL.
   at: _gl_debug_print (drivers\gles3\rasterizer_gles3.cpp:124)
ERROR: GL ERROR: Source: OpenGL Type: Error     ID: 1282        Severity: High  Message: GL_INVALID_OPERATION error generated. Texture name does not refer to a texture object generated by OpenGL.
   at: _gl_debug_print (drivers\gles3\rasterizer_gles3.cpp:124)
Scene changing; unassigning CurrentLevel.puzzle.
Finished unassigning CurrentLevel.puzzle.

Even if we can't fix the crashes, we can probably do something about the glitchy wallpaper appearance. The wallpaper shouldn't really require shaders or anything that clever. We implemented it 4 years ago, and it's possible if we try again we can think of a simpler or more clever way to implement it.


no such package '@build_bazel_rules_typescript_tsc_wrapped_deps//':

I have set up a repository to test the typescript rules here: https://github.com/acehko/bazel_typescript_test.
When I try to build I get this error.
Install node modules:
bazel run @yarn//:yarn
INFO: Analysed target @yarn//:yarn (0 packages loaded).
INFO: Found 1 target...
Target @yarn//:yarn up-to-date:
  bazel-bin/external/yarn/yarn
INFO: Elapsed time: 0.105s, Critical Path: 0.01s
INFO: Build completed successfully, 1 total action

INFO: Running command line: bazel-bin/external/yarn/yarn
yarn install v1.3.2
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 0.12s.

Build:
bazel build //:lib                                                                                ~/code/typescript/bazel_typescript_test
ERROR: /home/andrija/code/typescript/bazel_typescript_test/BUILD.bazel:10:1: every rule of type ts_library implicitly depends upon the target '@build_bazel_rules_typescript_tsc_wrapped_deps//:node_modules', but this target could not be found because of: no such package '@build_bazel_rules_typescript_tsc_wrapped_deps//': npm_install failed:  (Process terminated by signal 6)
ERROR: Analysis of target '//:lib' failed; build aborted: no such package '@build_bazel_rules_typescript_tsc_wrapped_deps//': npm_install failed:  (Process terminated by signal 6)
INFO: Elapsed time: 2.431s
FAILED: Build did NOT complete successfully (1 packages loaded)

You need to call ts_setup_workspace from your WORKSPACE file, see the readme.

It is called here: https://github.com/acehko/bazel_typescript_test/blob/master/WORKSPACE#L19.
I copied the example from here. Since the readme is out od date.

Oh, okay then, maybe it's a bug. Perhaps https://github.com/bazelbuild/rules_nodejs/issues/101 is related?
I cloned the example repo and it builds fine for me.
Platform, OS version, bazel version?
You could add debugging in https://github.com/bazelbuild/rules_nodejs/blob/master/internal/npm_install.bzl#L19 to confirm that we actually do run the npm install.

Yes, I think it's related.
I had node version 9.5.0 installed on my system.
When I switched to version 8.9.4 it the build works.
I think it might be related to this isssue: bazelbuild/rules_nodejs#77

Yes, thanks, that explains the problem.
On Fri, Feb 2, 2018 at 12:42 AM Andrija Čehko<EMAIL_ADDRESS>wrote:

Yes, I think it's related.
I had node version 9.5.0 installed on my system.
When I switched to version 8.9.4 it the build works.
I think it might be related to this isssue: bazelbuild/rules_nodejs#77
https://github.com/bazelbuild/rules_nodejs/issues/77
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_typescript/issues/142#issuecomment-362522141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC5I4k8lUaxDSYm-UCViZdHEhgjCJJFks5tQsqQgaJpZM4R0e2j
.


Sherpa Romeo new name and translations

Describe the bug
Sherpa Romeo changed it's name. According to: https://www.sherpa.ac.uk/romeo/
«Sherpa services is now Jisc's open policy finder»
Expected behavior
For better coherence, translations should be changed from Sherpa Romeo to Open Policy Finder.

Good afternoon @paulo-graca! as per your request, I have made available a PR where the name “Sherpa Romeo” has been changed to “Open Policy Finder”. But there is another key that contains the word “Romeo” and I was wondering if you had any suggestions for it.
"submission.sections.sherpa.publication.information.romeoPub": "Romeo Pub",


ci: Actions are outdated/deprecated

Hi folke,
just a heads-up, that all of your used GitHub actions are outdated/deprecated.
https://github.com/folke/lazy.nvim/blob/fafe1f7c640aed75e70a10e6649612cd96f39149/.github/workflows/ci.yml#L57
for example is deprecated and replaced by https://github.com/googleapis/release-please-action. Furthermore, there were breaking changes with v4.
The outdated ones still use Node 16, which will stop working after spring 2024.

Thank you for reporting!
I also enabled dependabot so I can easily see this in the future

Dependabot is a very good idea. I was about to suggest it, too 😉


Add methods to serialize classes that require factory method to instantiate.

Some classes, such as QROM, require a "build" factory method in order to create an instance of the class.  For these methods, the arguments needed to instantiate the class (which are constructed by the "build" method) cannot be serialized.  Here, we add methods to serialize and deserialize the args for the build method.
Additionally, some fixes have been added to allow serialization of common sub-bloqs such as CNOT and AND.  Unit tests have been provided for QROM, CNOT, and AND.

Usually these build methods are provided for convenience when calling them in your own code. Why would we need to go via the build methods rather than the constructor for serialization?

Didn't mean to submit this last change.  Still working on addressing comments.

What's the status of this? I see the referenced other PR has been closed

What's the status of this? I see the referenced other PR has been closed

The other PR solves the same issue as this one.  I will go ahead and close this PR.


Fork, Commit, Merge - Easy Issue (HTML)

Fork, Commit, Merge - Easy Issue (HTML)
Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!
Open the tasks/html/easy directory from the root of your project.
Your task is to insert an h1 tag with the name John Doe above the h2 tag in the index.html file.
Note: Only the index.html file needs modification for this task.

Check out README.md for more instructions and how to make a pull request.
Feel free to ask any questions here if you have some problems!
Also, kindly give this project a star to enhance its visibility for new developers!

hey admin i am very new to to opensource,i am not able see if u have merged my pull request or not how cwn i see it i have commited the mentioned change which was asked in the issue no #236

hey admin i am very new to to opensource,i am not able see if u have merged my pull request or not how cwn i see it i have commited the mentioned change which was asked in the issue no #236

Hi!
Yes your pull request was good and it's merged. You should always get emails from Github about all the changes and comments in pull requests and issues. Check your spam folder too if you don't see the Github emails. You can also always check from the repository Pull request section if the request is still active or if it is in closed pull requests, which usually means it is accepted and merged.
Here you can see all of the Fork, Commit, Merge repo closed pull requests: https://github.com/nikohoffren/fork-commit-merge/pulls?q=is%3Apr+is%3Aclosed which shows that your request was closed and merged.

Hi @nikohoffren , I raised a pull request in order to resolve this issue, so please take a look at my changes and merge my changes into the main branch.


Haskell: add Servant, Aeson-pretty, Uuid

My team went full-tilt with the HTTP API implementation, so please add a few more libraries to Haskell's base image. Thanks!

Any ETA on when these changes will become available in CI? I just submitted code that uses Servant, and the build system tried to download it from the Internet, which indicates that CI is still using an old Docker image.

@beevee

Sorry @beevee, it looks like Docker image is still missing some Servant dependencies. We have no idea how that's possible, and we aren't really inclined to investigate right now, so we're abandoning Servant for now. Sorry about the bother.


lib/zstd_static and programs/fileio.h have different line ending

It seems that these files in all branches have CRLF line endings instead of LF.

Mmmh, this is possible, since the development is done in both Windows and Linux/BSD configurations.
However, that's exactly the reason why there is a .gitattributes file : it's supposed to check for line ending on all files, and even correct them on the fly.
Now, I wonder if a .gitattributes scope is limited to its current directory. Maybe sub-directories remain unaffected...

As far as I know, usual glob filenames in .gitattributes are recognized as file mask for all subdirectories as you expected.
Perhaps, "Refreshing a repository after changing line endings" section in GitHub's guide "Dealing with line endings" helps you. Since these files have not changed from initial commit, just "refreshing" may resolve this problem.

OK, thanks
The procedure is clear to follow.
Line endings are now fixed in both branches.


updates based on feedback received during WG-MIE meeting.

@efucile, @tomkralidis - don't know if we want to merge this just now? not sure where we are in the process of packaging docs for INFCOM3.

I'm fine to merge, and what would have gone for INFCOM-3 was tagged with 2024-02-07.


Remove commit status, just use statusCheckRollup

Fixes: https://app.asana.com/0/1149418478823393/1203565858490862/f
This is happening because there are two types of "status". One is a "commit status" (status classic), the other is a check run. If we were only relying on the status and falling back to statusCheckRollup, we were incorrectly assuming the PR was in a "success" state when certain types of checks runs (like we use for Testville) would be ignored in this logic.
This blog post helped me understand the difference, and how we were mis-using status
Pull Request synchronized with Asana task

Yeah - statusCheckRollup reports on both commit status and check runs (this is where the "rollup" part comes in). See: https://docs.github.com/en/graphql/reference/objects#statuscheckrollup

Test


Embed button no longer shows in HUD after upgrading to 2.3

Description
Hi! We recently upgraded to 3.5 beta and the embed button no longer shows in the HUD. It still exists in the main assets view so we can work around this, but it would be nice to have it back in the HUD. Thanks for making such a great plugin!
Steps to reproduce

Upgrade to 3.5
Upload an asset from an assets field
Notice the missing Embed button

Other information

Embedded Assets version: 2.3.0
Craft CMS version: 3.5.0-beta.3
PHP version: 7.4.7

Hello ! I get the same issue... It would be great to get this button back.

Craft CMS : <IP_ADDRESS>
Embedded Assets : 2.3.0

The button should definitely still be there; with the 2.3.0 update the button was only removed from the Redactor field's 'add image' modal, where it didn't belong anyway.  Are there any JavaScript errors when it doesn't appear?

Same issue here. Updated to 2.3.0, embed button disappeared.

Downgraded to 2.2.7, button is back.

No JS error.
Craft CMS <IP_ADDRESS>

I fixed the title of the issue. Sorry about that.

The button should now be showing again with Embedded Assets 2.3.1 for asset fields with no restriction on allowed file types.


Replaced return keyword with pure.

Issue #71 mentions that the return keyword has been removed, and pure should be used instead. This PR updates chapter 8 to replace the call to return with a call to pure.

Fixed on the 0.11.3 branch now, thanks!


Update issue templates

We should consider adding 2 separate templates for bug and feature to further guide people when they visit with their ideas/problems. imo the more guidance the better.

Thanks @jwinn !

Coverage remained the same at 100.0% when pulling c236d01eba4e778dc048f6ce16e3cb5e65ea0fc2 on update-templates into 435e07b10b769da07c912ffb439dcd233fd3dbbb on master.

Coverage remained the same at 100.0% when pulling c236d01eba4e778dc048f6ce16e3cb5e65ea0fc2 on update-templates into 435e07b10b769da07c912ffb439dcd233fd3dbbb on master.


Add ability to Merge/Stack Telegraf configurations in UI

Use case
Installing multiple templates from which each Telegraf configuration is needed in the same data source.
Example:
User has a K8s-centric infrastructure.  They want to run Telegraf as a daemonset and want to use Templates to get started.  They use Redis, Nginx, HAproxy, Kafka, MySQL, etc., and want to take advantage of the templated Telegraf configurations that exist for each of these services.
Problem:
Complete Telegraf configurations are in each Template.  User's ability to combine these configurations is hindered.
Their options become:

Running Telegraf with multiple local configurations

telegraf.d/ currently only works with local configs and the idea behind the Telegraf/2.0 duality is managing and obtaining configuration from a central InfluxDB repository.  Even locally, this method shares the other issues.

Running multiple Telegrafs on the same data source

IMO, this is clunky and will be an oft-rejected pattern for users

Copy/pasting relevant diffs of multiple configs into on

Too manual and degrades the overall InfluxDB Templates messaging of time-to-awesome and one-command utility

Copy/paste parts of multiple config files into one

Separate problem (addressed in proposed solution):
The most part of authoring a template is including even one Telegraf configuration.  It requires manually entering boilerplate YAML and pasting your TOML into that section.  From there, the author must make sure all lines are properly indented.  I think it's safe to this isn't the experience we want for users of any piece of InfluxData software.
Proposal
Editable configurations in UI.  Ultimately, the envisioned UX of this to have some kind of UI for moving configuration blocks between configuration files.  This would mean the UI understands the components of the config files and exposes them as objects that can be moved, copied, picked from a dropdown or checked/selected in a list, etc.
The idea here is to benefit both the Template author and consumer personas.  If the Template author can create and edit configuration in the UI, they can export (generate this portion of the template) right from their workspace.
Some possible additions to this (needs more discussion and validation)

Templates repo enforces a lack of agent and output configuration.  The UI would supply a default Agent for all configurations to share.  This could be copied and then edited for custom Agent configurations( adding jitter, changing intervals and batching, enabling debug, etc.).  The output plugin would also be provided/generated.  We would then leave the option of using non-InfuxDB outputs to the template user if needed (outside of template).

Workflow change for author:

Author can now create and modify configuration from the UI and export from there which skips a couple steps!
Author is now encouraged to include a namepass field in any Processor/Aggregator plugins they use.  This is because they will only expect the input data from the Template for which they were written.  When combined with inputs from other Templates, we'd like to avoid the necessary overhead of each of those plugins dealing with more data than they need to.
(only if Agent/Output exclusion is enforced) Do not include Agent or Output configurations

Workflow change for consumer:

Instead of copy/pasting piecemealed configuration and

Alternatives proposed

Telegraf would support intelligently merging configurations based on diffs.  There is an assumption that the Agent configuration blocks are

Deemed out of scope

Telegraf would support running with multiple remote configurations (like telegraf.d/ but for centrally hosted configs in, say Influx2)

Could have added a flag like --config-url to pull multiple configs.
This does not fully eliminate challenges with config overlap, conflicts, etc.

I would love to see this happening. The most important thing in my opinion is that the configurations must be editable from the UI.

I would love to see this happening. The most important thing in my opinion is that the configurations must be editable from the UI.

In the meantime I found out that it is possible to create/update telegraf configurations via CLI.

In the meantime I found out that it is possible to create/update telegraf configurations via CLI.

@wd3mo good news is I believe you can now edit and save the config in the UI.

@wd3mo good news is I believe you can now edit and save the config in the UI.

@wd3mo Check this portion of the video of editing the Telegraf config that's already in the UI https://youtu.be/f7ws9pfLmJc?t=96

@wd3mo Check this portion of the video of editing the Telegraf config that's already in the UI https://youtu.be/f7ws9pfLmJc?t=96


Adds CI via GitHub Actions

hmm. somehow rebase didn't work as planned :/

Replace with new PR since this is messed up somehow


session handling

I want the repo to default to CWBI-prod.  Outside users would not have to set api_session.  They would be able to retrieve data by simply doing the following
from CWMS import CwmsTs
ts_data = CwmsTs.retrieve_ts_json(tsid, 'MVP')
or
import CWMS
ts_data = CWMS.CwmsTs.retrieve_ts_json(tsid,'MVP')
Then have the ability to change api_session if connecting to a different URL. would like to only have to update api_session and then it transfers to all classes instead of having to run
cwsm_ts = CwmsTs(api_session)
cwms_loc = CwmsLoc(api_session)
for each class, but I don't know if that is possible.

I don't like the idea of hiding the URL from the user so I think parameterizing the API constructors is still a good idea. To avoid needing the user to type out the URL, factory methods can help:
import cwms

cwms_prod_session = cwms.cwbi_prod_session() #optional apikey
prod_ts = cwms.TimeSeries(cwms_prod_session)

cwms_test_session = cwms.cwbi_test_session() #optional apikey
test_ts = cwms.TimeSeries(cwms_test_session)

district_session = cwms.district_session("https://spk.district.url/spk-data/") #optional apikey
district_ts = cwms.TimeSeries(district_session)

I am thinking about the case of the public (i.e. other government agencies, researchers, consultants) who want to use cwms-python to access our data.  they shouldn't have to know what cwbi-production is or what url to use.  They just need to know they are collection data from USACE.  In a couple years we will just have cwbi-prod and cwbi-test maybe a cwbi-dev.  most users both internal and external will only be connecting to cwbi-prod.  The other 2 will only be used for development.  The ability to connect to district servers is only short term.  I feel the public should be able in one line of code to access time series data.  I would like the same usability for the public as the USGS dataretrieval-python.

What do you think about adding factory methods for the default URL in the init?
Example: https://github.com/HydrologicEngineeringCenter/cwms-python/pull/14


Productize sigma.js/node-rapids extra-large-graphs to sigma.js quality and satisfaction.

Complete PR and all review items.
I've produced https://www.github.com/jacomyal/sigma.js/pull/1252. Today I'm starting to revise it until there's nothing extra or unnecessary. The original PR was based on an experimental research branch that produced the fruit I was looking for. Now I want that PR to meet all of your expectations. I'm going to keep a checklist here for now, tracking my progress as I update the PR.

[x]  Get rid of the .glsl shaders in the demo.

I moved these shaders from the sigma.js hierarchy because I was having trouble importing them. I'll spend time making that work as expected.

[x]  Remove generate-graph.ts

Just gonna go with .js on this one.

[x]  Add arguments and messaging to generate-graph.js

[x]  Modify index.html to display graph parameters instead of take them.

[x]  Consider a button to switch between GPU and CPU data ETL with benchmark.

The above is not going to happen in this PR, it'll take another PR if we get there. I'll definitely be looking at more benchmarks if there's interest.

[x]  Clean up index.ts

[x]  Document the hacks in rapids-graph.ts and the engine improvements they imply.

[x]  Modify package.json to handle launching on a different port specifically for extra-large-graphs

[x] Reset and minimize changes outside of extra-large-graphs.

[x] Make a sweet README.md about what is going on here.

Depends on #1252

It's done. Please take a look at https://www.github.com/jacomyal/sigma.js/pull/1252 and let me know what you think!

Thanks @thomcom, see my remarks on the PR. I will close this for now since the result is on the PR.


Text goes outside parent widget

What
When using Slidable widget the text goes beyond the Card widget
Where
Inside user_keys.dart file
Screenshot

#29


change label name

change some translations
move dvr_need define before dvr_case
Conflicts:
languages/tr.py
modules/s3db/dvr.py

For some reason your multi-commit PRs always send up with just the commit message of the last one which is not ideal
This commit says "changed label" which isn't what it does at all (that was just an interim step).
The actual change is "Add site to dvr_case"


Russian localization of messages.

Hello!
I add russian localization of messages.

Thank you.  Merged now.


Doesn't support TIFF sourcefiles

Here's my error:
Error: Command failed: identify: no decode delegate for this image format
`node-deepzoomtools/originals/bees for seadragon.tiff' @ error/constitute.c/ReadImage/501.

  <<< async stack >>>
  at exports_convert__2 (node-deepzoomtools/lib/imagemagick.js:45:18)
  at DeepZoomImage_create__1 (node-deepzoomtools/lib/index.js:44:16)
  <<< raw stack >>>
    at ChildProcess._spawn.proc.on.onExit (node-deepzoomtools/node_modules/gm/lib/command.js:279:17)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at maybeClose (child_process.js:743:16)
    at Socket.<anonymous> (child_process.js:956:11)
    at Socket.EventEmitter.emit (events.js:95:17)
    at Pipe.close (net.js:465:12)

It might be that your GraphicsMagick wasn’t compiled with TIFF support:

GraphicsMagick requires Sam Leffler's TIFF software available via anonymous FTP at
ftp://ftp.remotesensing.org/libtiff/
or via HTTP at
http://www.remotesensing.org/libtiff/
to read the TIFF image format. It in turn optionally requires the JPEG and ZLIB libraries. Libtiff 3.8.2 or later is recommended.

– Source: http://www.graphicsmagick.org/README.html
You can confirm by running identify -list format.

identify -list format Does show I don't have TIFF. Sounds like it's not a default option. I suppose we could have a little documentation for people who need it? Anyway, it's not a big deal for me; I've worked around it. Just thought I would let you know.


Allow healthchecks to be performed on another port

Please find a pull request to allow one to configure a specific port for the health checks.
fixes https://github.com/lyft/envoy/issues/439

We use this PR in production to perform healthchecks against http services, alongside grpc services on the same upstream.

Hi,
Thanks a lot for working on this. I linked in the tracking issue for this feature. I would like to propose a different set of interfaces for implementing this. I'm hoping it won't be too much work to implement the proposal. My main issue with this approach is that it puts port into a whole lot of places which might not have any port (for example pipe/uds).
Here is what I would do:

Add a new function, createHealthCheckConnection(...), similar to: https://github.com/lyft/envoy/blob/master/include/envoy/upstream/upstream.h#L42
Add the ability for a host to have an alternate HC address. I would have this be full URL syntax such as "tcp://<IP_ADDRESS>:81". The reason I would do this is that it will actually set us up later to easily get HC status from a centralized HC if we want.

How we actually get the alternate host address for HC port now becomes cluster specific (DNS, static, SDS, etc.). We don't necessarily have to implement them all at the same time. What cluster types are you using?
Thanks,
Matt

I'll let @jbdalido answer to the question on the type of cluster.
Thanks a lot for your suggestion!
It does sound better indeed, we aimed for the simplest as we needed it to work. I'll get back on it ASAP, probably not before monday however.
Cheers

Add the ability for a host to have an alternate HC address. I would have this be full URL syntax such as "tcp://<IP_ADDRESS>:81". The reason I would do this is that it will actually set us up later to easily get HC status from a centralized HC if we want.

Actually I was thinking of this, in case of a dns entry resolving to several host it leads to an ambiguity. Let's take for instance a domain name services and with several IPs behind ip1, ip2 and ip3.
If I understood you correctly I would setup the cluster with for instance:
url: tcp://services:1234 and hc_url: tcp://services:1235, however I'll need to sync the dns resolution to get the proper ip for each entry and avoid ip1 being checked on ip2.
What is your take on this ?

I think there are a few options here depending on the cluster type that you need this to work for:

Just ignore DNS clusters for now, and don't support a separate HC port. (I think most people that want this feature are probably going to use SDS or static clusters, but I'm not sure).
For DNS, if we want this, either have a separate cluster option such as "alt_hc_port", which is then used to populate the HC address when the DNS response is received. Another option would be to expand the "URL" syntax in some way which we document. For example, "tcp://<IP_ADDRESS>:80:81" means primary port is 80, HC is 81. We have already discussed doing something like this for SRV such as "tcp://<IP_ADDRESS>:srv".

Hi,
sorry for the delay, so we do use Strict DNS cluster type so we do need to keep it that way for now. We use this type of cluster because it makes scaling and HA basically free and makes envoy really fast at detecting problems. We can't just have a tcp health check because the fact that the port is bound does not necessarily means the application is in good health.
From all your suggestion, the alt_hc_port option in the cluster section would probably the easiest and clearer one. I'll try to get back on this asap.
Cheers

@daedric OK, I'm still not 100% crazy about the "alt_hc_port" option in the sense that we don't need it for static or SDS clusters (it can be a property of the returned host). I'm really leaning towards having it be part of the "URL" somehow.
@lyft/network-team @rshriram @htuch opinions on the config for ^?

It might be nice if we can keep URLs as valid URIs, to allow using standard parsing functions and interoperate with libraries that generate them in config pipelines. It's probably not a strong requirement though and might make it more concise in this case (and with srv).
I don't see the issue with alt_hc_port though if it's optional - it's the same as just omitting the second : fragment from the URL.

OK if we go with alt_hc_port though we will have to reconcile w/ SDS and static where you might not want the port to be the same for each host. In that case we almost definitely want it to be part of each host definition, so I guess we can only look at it in DNS cases. I don't feel that strongly, so I'm fine either way.

I agree with @htuch that it would be better to keep the URL as a valid URI. Makes it much easier for all the config gens to generate envoy config. Besides, tcp://<IP_ADDRESS>:80:81 is kind of confusing [while it saves another config option, it kills readability].
Here is a random thought: why not use a URI in the health check as well, instead of having a separate port field? [May be it has already been discussed in this thread]. For example, user could specify either a PATH or a URI field for the health check (not both). For SDS/static, there would be no change. For strict_dns/logical_dns, when a separate port is desired, people could specify it as a complete URL (there will be duplication of hostname, but thats better than a port number that stands out in the config).
It won't pollute the config with a separate port that needs to be kept track of. As a nice side effect, we could even do health check with a different host. E.g., strict/logical dns points to foo.bar.com external service, while the health check service goes to uptime.com:1234/check/foo.bar.com.
In future, if we move to subsets or global health check service, we could reuse the same machinery [I am just thinking out aloud here, havent thought through fully yet].

Going to close this for now. Please reopen if/when you are ready to clean this up. I also noted that this PR is ongoing in the primary issue.

Following up on this from the original issue, having a full URL doesn't make much sense in the usual case, which is you want "the same one as the connection is going to" with perhaps different protocol and port. How would that be expressed this this proposed reworking?

@1mentat if possible can we discuss design in https://github.com/lyft/envoy/issues/439 so it doesn't get lost. Feel free to repost there and we can discuss.


Export has duplicates

Export yields unexpected results. We see multiple duplicates in the exported excel file.
The problem stems from this line:
https://github.com/yajra/laravel-datatables-export/blob/4e7cbcb2029fd52f9ff6a7ae5313a42f6ff0b379/src/Jobs/DataTableExportJob.php#L122
Notice that if the filtered query is not ordered by id (or any unique column), the order of the rows might differ between the calls.
I would suggest using lazyById, but then we would have to pass the name of the column we want to use for lazyById.

Maybe we can use the value set in the ->setRowId() call?
However, I think doing so will be a change in behavior. Some of our users expect what they see on the screen would be in the same order when it was exported.
I am in favor of using lazyById but it should not be the default behavior. We can put it config I guess?

I was actually thinking the opposite...
When using chunking or lazy, you have to guarantee the order of rows by an unique column. If not, you take a risk of getting different order of results between the execution of the query, and therefore missing some rows and duplicating some.
In fact, getFilteredQuery() could be ordered by any column chosen by the user. I was going to suggest the following solution:
$query = $dataTable->getFilteredQuery()->reorder();
$query = $query->orderBy($someUniqueColumn)->lazy($chunkSize);
The $someUniqueColumn can come from the $dataTable object, or passed down from the job.
I understand that users expect order to be preserved when exporting, but I think accurate result takes precedence. Unless someone can come up with a better solution, I don't see how you can offer both.

Can you provide snippets to reproduce the duplicates? I asked around my users and they haven't encountered any duplicates yet. Largest export so far is ~200k.

I'm not allowed to share any code snippets, but I've created a demo:
https://github.com/uchajk/duplicates
if you try to export users, you will actually see the duplicates in the excel spreadsheet. Obviously, if you lower chunk size, you will see more duplicates.
We are using pgsql and in the datatables class we are using Yajra\DataTables\QueryDataTable and Illuminate\Database\Query\Builder

I tested your demo app using SQLite. I was able to filter 28 records and export yields to the same result. Filtered 1 and all 1k records, and got the expected results.
Might be pgsql specific issue? Will try to set up a pgsql later.

@yajra $chunkSize has to be smaller than total number of records in filteredQuery.
It's the different order between the calls of the query that results in duplicates.
If chunk size is 1k, exporting 1k entries will only execute the query 1 time and there is no possibility of duplicates at all.
If you were trying to export 6,752 entries with $chunkSize 1k, the query will get executed 7 times, each of the execution possibly having different order. Therefore, the entries that you processed in the first execution (0 to 999) might appear in the second execution (1000 to 1999) and you would be exporting these entries second time.
Again, this could only happen if the filteredQuery is not ordered by an unique column (e.g. Updated At).

The seeder does not work on SQLite and always hits a unique constraint issue.
I tried to export 7275 records and got the expected output.
    public function query(): Builder
    {
        return DB::table('users')
                 ->where('name', 'like', '%a%');
    }

UI

Excel

https://www.youtube.com/watch?v=li5RVhoRiMQ

@uchajk maybe orderFixed option would help in this case? Not tested but maybe you can add a post order defaulted to ID.

@uchajk maybe orderFixed option would help in this case? Not tested but maybe you can add a post order defaulted to ID.

Yeah sounds like it might. I'll need to find some time to test this.