部署方式 | How to Deploy
使用一键部署脚本 | Using zealot-docker on-click install (Default)
部署版本 | Version
nightly (Default)
反代服务 | Reverse Proxy
nginx
HTTPS 证书类型 | HTTPS(SSL)
可受信任的证书 Verified SSL
已阅读文档 | Read the document

[X] 已阅读 | Yes

描述 | Description
报错如下：
Error uploading to Zealot [422]: {"error"=>"参数错误，请检查请求的参数是否正确", "entry"=>{"devices"=>["是无效的"]}}
而且控制台的错误都是循环同样的日志
问题日志 | Relevant log output
2023-07-28 12:03:45 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in `require'
2023-07-28 12:03:45 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in `boot_application'
2023-07-28 12:03:45 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:42:in `run'
2023-07-28 12:03:45 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/bin/sidekiq:31:in `<top (required)>'
2023-07-28 12:03:45 zealot-zealot-1    | ./bin/sidekiq:29:in `load'
2023-07-28 12:03:45 zealot-zealot-1    | ./bin/sidekiq:29:in `<main>'
2023-07-28 12:03:45 zealot-zealot-1    | Starting Zealot Worker
2023-07-28 12:03:46 zealot-zealot-1    | 2023-07-28T04:03:46.807Z pid=6671 tid=2on INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://redis:6379/0", :username=>nil, :password=>nil, :network_timeout=>5}
2023-07-28 12:03:46 zealot-zealot-1    | redis-client requires Redis 6+ with HELLO command available (redis://redis:6379/0)
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:706:in `rescue in connect'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:662:in `connect'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:657:in `raw_connection'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:624:in `ensure_connected'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:209:in `call'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/redis_client_adapter.rb:30:in `method_missing'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in `block in hdel'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:164:in `block in redis'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:110:in `block (2 levels) in with'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in `handle_interrupt'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in `block in with'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in `handle_interrupt'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in `with'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:161:in `redis'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq.rb:73:in `redis'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in `hdel'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:78:in `remove_job_schedule'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/schedule.rb:115:in `remove_schedule'
2023-07-28 12:03:46 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:5:in `add_or_delete_schedule'
2023-07-28 12:03:46 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:38:in `block in <main>'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in `instance_exec'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in `block in make_lambda'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:199:in `block (2 levels) in halting'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:687:in `block (2 levels) in default_terminator'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in `catch'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in `block in default_terminator'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:200:in `block in halting'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in `block in invoke_before'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in `each'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in `invoke_before'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:106:in `run_callbacks'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/reloader.rb:88:in `prepare!'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application/finisher.rb:68:in `block in <module:Finisher>'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in `instance_exec'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in `run'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:61:in `block in run_initializers'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:349:in `block in each_strongly_connected_component'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in `each'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in `call'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
2023-07-28 12:03:46 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:60:in `run_initializers'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application.rb:372:in `initialize!'
2023-07-28 12:03:46 zealot-zealot-1    | /app/config/environment.rb:7:in `<top (required)>'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in `require'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in `boot_application'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:42:in `run'
2023-07-28 12:03:46 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/bin/sidekiq:31:in `<top (required)>'
2023-07-28 12:03:46 zealot-zealot-1    | ./bin/sidekiq:29:in `load'
2023-07-28 12:03:46 zealot-zealot-1    | ./bin/sidekiq:29:in `<main>'
2023-07-28 12:03:46 zealot-zealot-1    | Starting Zealot Worker

2023-07-29 09:34:56 zealot-zealot-1    | method=POST path=/api/apps/upload format=/ controller=Api::Apps::UploadController action=create status=422 duration=9202.87 view=3.26 db=37.59 time=2023-07-29 09:34:56 +0800 ip=<IP_ADDRESS> token=320bacf980e20e7b058be2d77154dc53 channel_key=6ea30eb2296d5cfd556922ae8ce5e6a0
2023-07-29 09:34:57 zealot-zealot-1    | 2023-07-29T01:34:57.007Z pid=4924 tid=x0 INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://redis:6379/0", :username=>nil, :password=>nil, :network_timeout=>5}
2023-07-29 09:34:57 zealot-zealot-1    | redis-client requires Redis 6+ with HELLO command available (redis://redis:6379/0)
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:706:in rescue in connect' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:662:in connect'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:657:in raw_connection' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:624:in ensure_connected'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:209:in call' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/redis_client_adapter.rb:30:in method_missing'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in block in hdel' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:164:in block in redis'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:110:in block (2 levels) in with' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in handle_interrupt'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in block in with' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in handle_interrupt'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in with' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:161:in redis'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq.rb:73:in redis' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in hdel'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:78:in remove_job_schedule' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/schedule.rb:115:in remove_schedule'
2023-07-29 09:34:57 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:5:in add_or_delete_schedule' 2023-07-29 09:34:57 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:38:in block in '
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in instance_exec' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in block in make_lambda'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:199:in block (2 levels) in halting' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:687:in block (2 levels) in default_terminator'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in catch' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in block in default_terminator'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:200:in block in halting' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in block in invoke_before'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in each' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in invoke_before'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:106:in run_callbacks' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/reloader.rb:88:in prepare!'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application/finisher.rb:68:in block in <module:Finisher>' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in instance_exec'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in run' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:61:in block in run_initializers'
2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:228:in block in tsort_each' 2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:350:in block (2 levels) in each_strongly_connected_component'
2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:431:in each_strongly_connected_component_from' 2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:349:in block in each_strongly_connected_component'
2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in each' 2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in call'
2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in each_strongly_connected_component' 2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:226:in tsort_each'
2023-07-29 09:34:57 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:205:in tsort_each' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:60:in run_initializers'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application.rb:372:in initialize!' 2023-07-29 09:34:57 zealot-zealot-1    | /app/config/environment.rb:7:in <top (required)>'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in require' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in boot_application'
2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:42:in run' 2023-07-29 09:34:57 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/bin/sidekiq:31:in <top (required)>'
2023-07-29 09:34:57 zealot-zealot-1    | ./bin/sidekiq:29:in load' 2023-07-29 09:34:57 zealot-zealot-1    | ./bin/sidekiq:29:in '
2023-07-29 09:34:57 zealot-zealot-1    | Starting Zealot Worker
2023-07-29 09:34:58 zealot-zealot-1    | 2023-07-29T01:34:58.087Z pid=4930 tid=yi INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://redis:6379/0", :username=>nil, :password=>nil, :network_timeout=>5}
2023-07-29 09:34:58 zealot-zealot-1    | redis-client requires Redis 6+ with HELLO command available (redis://redis:6379/0)
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:706:in rescue in connect' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:662:in connect'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:657:in raw_connection' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:624:in ensure_connected'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:209:in call' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/redis_client_adapter.rb:30:in method_missing'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in block in hdel' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:164:in block in redis'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:110:in block (2 levels) in with' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in handle_interrupt'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in block in with' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in handle_interrupt'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in with' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:161:in redis'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq.rb:73:in redis' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in hdel'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:78:in remove_job_schedule' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/schedule.rb:115:in remove_schedule'
2023-07-29 09:34:58 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:5:in add_or_delete_schedule' 2023-07-29 09:34:58 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:38:in block in '
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in instance_exec' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in block in make_lambda'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:199:in block (2 levels) in halting' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:687:in block (2 levels) in default_terminator'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in catch' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in block in default_terminator'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:200:in block in halting' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in block in invoke_before'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in each' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in invoke_before'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:106:in run_callbacks' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/reloader.rb:88:in prepare!'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application/finisher.rb:68:in block in <module:Finisher>' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in instance_exec'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in run' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:61:in block in run_initializers'
2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:228:in block in tsort_each' 2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:350:in block (2 levels) in each_strongly_connected_component'
2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:431:in each_strongly_connected_component_from' 2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:349:in block in each_strongly_connected_component'
2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in each' 2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in call'
2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in each_strongly_connected_component' 2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:226:in tsort_each'
2023-07-29 09:34:58 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:205:in tsort_each' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:60:in run_initializers'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application.rb:372:in initialize!' 2023-07-29 09:34:58 zealot-zealot-1    | /app/config/environment.rb:7:in <top (required)>'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in require' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:303:in boot_application'
2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/cli.rb:42:in run' 2023-07-29 09:34:58 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/bin/sidekiq:31:in <top (required)>'
2023-07-29 09:34:58 zealot-zealot-1    | ./bin/sidekiq:29:in load' 2023-07-29 09:34:58 zealot-zealot-1    | ./bin/sidekiq:29:in '
2023-07-29 09:34:58 zealot-zealot-1    | Starting Zealot Worker
2023-07-29 09:34:59 zealot-zealot-1    | 2023-07-29T01:34:59.178Z pid=4936 tid=y8 INFO: Sidekiq 7.1.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://redis:6379/0", :username=>nil, :password=>nil, :network_timeout=>5}
2023-07-29 09:34:59 zealot-zealot-1    | redis-client requires Redis 6+ with HELLO command available (redis://redis:6379/0)
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:706:in rescue in connect' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:662:in connect'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:657:in raw_connection' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:624:in ensure_connected'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/redis-client-0.14.1/lib/redis_client.rb:209:in call' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/redis_client_adapter.rb:30:in method_missing'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in block in hdel' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:164:in block in redis'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:110:in block (2 levels) in with' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in handle_interrupt'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109:in block in with' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in handle_interrupt'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106:in with' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq/config.rb:161:in redis'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-7.1.2/lib/sidekiq.rb:73:in redis' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:238:in hdel'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/redis_manager.rb:78:in remove_job_schedule' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/sidekiq-scheduler-5.0.3/lib/sidekiq-scheduler/schedule.rb:115:in remove_schedule'
2023-07-29 09:34:59 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:5:in add_or_delete_schedule' 2023-07-29 09:34:59 zealot-zealot-1    | /app/config/initializers/sidekiq_scheduled.rb:38:in block in '
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in instance_exec' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:445:in block in make_lambda'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:199:in block (2 levels) in halting' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:687:in block (2 levels) in default_terminator'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in catch' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:686:in block in default_terminator'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:200:in block in halting' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in block in invoke_before'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in each' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:595:in invoke_before'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/callbacks.rb:106:in run_callbacks' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/reloader.rb:88:in prepare!'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/application/finisher.rb:68:in block in <module:Finisher>' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in instance_exec'
2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:32:in run' 2023-07-29 09:34:59 zealot-zealot-1    | /app/vendor/bundle/ruby/3.0.0/gems/railties-7.0.6/lib/rails/initializable.rb:61:in block in run_initializers'
2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:228:in block in tsort_each' 2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:350:in block (2 levels) in each_strongly_connected_component'
2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:431:in each_strongly_connected_component_from' 2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:349:in block in each_strongly_connected_component'
2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in each' 2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in call'
2023-07-29 09:34:59 zealot-zealot-1    | /usr/local/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'

确实是的，下面跟上传都没有关系。麻烦你能进系统的管理面部，查看下后台任务页面里"失败“或”重试“下面有没有报错的列表，有的话可以点进去一个，能看到具体的错误信息。

这个界面是怎么进入的？😂

使用管理员权限的账号登录在左侧菜单就能看到管理面板区域

任务是空的

话说你的 redis 是什么版本？最新 zealot 已经 redis 最低版本从 5 变更为了 6.2 以上，建议直接用 7

zealot 我已经通过upgrade都升级了，为啥redis还是5？ 如何升级到7？

如果你是用 docker-compose.yml 部署的，修改里面的 redis 部分的版本号
services:
  redis:
    <<: *restart_policy
-   image: redis:5-alpine
+   image: redis:7-alpine
    command: redis-server
    volumes:

一顿操作，升级了redis，数据库的警告也修复了。
之前sidekiq不停的刷错误log现在也好了。
但是结果还是一样。
fastlane插件上传后，还是报这个错。
ZEAALOT_ERROR_MESSAGE | Error uploading to Zealot [422]: {"error"=>"参数错误，请检查请求的参数是否正确", "entry"=>{"devices"=>["是无效的"]}}
你现在可以看下日志，跟之前有些区别，你再帮忙看看。
2023-08-04 10:12:03 zealot-zealot-1    | method=POST path=/api/apps/upload format=/ controller=Api::Apps::UploadController action=create status=422 allocations=2025836 duration=6822.96 view=3.19 db=16.01 time=2023-08-04 10:12:03 +0800 ip=<IP_ADDRESS> token=320bacf980e20e7b058be2d77154dc53 channel_key=6ea30eb2296d5cfd556922ae8ce5e6a0
2023-08-04 10:14:07 zealot-zealot-1    | method=GET path=/admin/background_jobs format=html controller=Admin::BackgroundJobsController action=index status=200 allocations=4086 duration=21.99 view=19.02 db=0.00 time=2023-08-04 10:14:07 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 10:14:10 zealot-zealot-1    | method=GET path=/admin/logs format=html controller=Admin::LogsController action=index status=200 allocations=3902 duration=10.79 view=9.16 db=0.00 time=2023-08-04 10:14:10 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 10:14:30 zealot-zealot-1    | method=GET path=/admin/system_info format=html controller=Admin::SystemInfoController action=index status=200 allocations=72671 duration=56.10 view=34.51 db=2.19 time=2023-08-04 10:14:30 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 10:14:35 zealot-zealot-1    | method=GET path=/admin/system_info format=html controller=Admin::SystemInfoController action=index status=200 allocations=15546 duration=19.16 view=6.75 db=1.08 time=2023-08-04 10:14:35 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 10:14:36 zealot-zealot-1    | method=GET path=/admin/system_info format=html controller=Admin::SystemInfoController action=index status=200 allocations=15224 duration=21.83 view=9.57 db=1.52 time=2023-08-04 10:14:36 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 10:14:37 zealot-zealot-1    | method=GET path=/admin/logs format=html controller=Admin::LogsController action=index status=200 allocations=3900 duration=10.63 view=9.05 db=0.00 time=2023-08-04 10:14:37 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 10:23:48 zealot-zealot-1    | method=POST path=/api/apps/upload format=/ controller=Api::Apps::UploadController action=create status=422 allocations=2041823 duration=6814.42 view=1.70 db=20.60 time=2023-08-04 10:23:48 +0800 ip=<IP_ADDRESS> token=320bacf980e20e7b058be2d77154dc53 channel_key=6ea30eb2296d5cfd556922ae8ce5e6a0
2023-08-04 10:24:13 zealot-zealot-1    | method=GET path=/admin/logs format=html controller=Admin::LogsController action=index status=200 allocations=3892 duration=17.33 view=15.13 db=0.00 time=2023-08-04 10:24:13 +0800 ip=<IP_ADDRESS> username=管理员
2023-08-04 08:59:33 zealot-postgres-1  |
2023-08-04 08:59:33 zealot-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-08-04 08:59:33 zealot-postgres-1  |
2023-08-04 08:59:33 zealot-postgres-1  | 2023-08-04 00:59:33.198 UTC [1] LOG:  starting PostgreSQL 12.15 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-08-04 08:59:33 zealot-postgres-1  | 2023-08-04 00:59:33.198 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-08-04 08:59:33 zealot-postgres-1  | 2023-08-04 00:59:33.198 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-08-04 08:59:33 zealot-postgres-1  | 2023-08-04 00:59:33.202 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-04 08:59:33 zealot-postgres-1  | 2023-08-04 00:59:33.212 UTC [21] LOG:  database system was shut down at 2023-08-04 00:58:57 UTC
2023-08-04 08:59:33 zealot-postgres-1  | 2023-08-04 00:59:33.216 UTC [1] LOG:  database system is ready to accept connections
2023-08-04 09:02:25 zealot-postgres-1  | 2023-08-04 01:02:25.312 UTC [1] LOG:  received fast shutdown request
2023-08-04 09:02:25 zealot-postgres-1  | 2023-08-04 01:02:25.313 UTC [1] LOG:  aborting any active transactions
2023-08-04 09:02:25 zealot-postgres-1  | 2023-08-04 01:02:25.315 UTC [1] LOG:  background worker "logical replication launcher" (PID 27) exited with exit code 1
2023-08-04 09:02:25 zealot-postgres-1  | 2023-08-04 01:02:25.318 UTC [22] LOG:  shutting down
2023-08-04 09:02:25 zealot-postgres-1  | 2023-08-04 01:02:25.331 UTC [1] LOG:  database system is shut down
2023-08-04 09:02:48 zealot-postgres-1  |
2023-08-04 09:02:48 zealot-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-08-04 09:02:48 zealot-postgres-1  |
2023-08-04 09:02:48 zealot-postgres-1  | 2023-08-04 01:02:48.576 UTC [1] LOG:  starting PostgreSQL 12.15 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-08-04 09:02:48 zealot-postgres-1  | 2023-08-04 01:02:48.576 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-08-04 09:02:48 zealot-postgres-1  | 2023-08-04 01:02:48.576 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-08-04 09:02:48 zealot-postgres-1  | 2023-08-04 01:02:48.578 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-04 09:02:48 zealot-postgres-1  | 2023-08-04 01:02:48.591 UTC [22] LOG:  database system was shut down at 2023-08-04 01:02:25 UTC
2023-08-04 09:02:48 zealot-postgres-1  | 2023-08-04 01:02:48.594 UTC [1] LOG:  database system is ready to accept connections
2023-08-04 09:31:35 zealot-postgres-1  | 2023-08-04 01:31:35.173 UTC [498] ERROR:  relation "pg_stat_statements" does not exist at character 15
2023-08-04 09:31:35 zealot-postgres-1  | 2023-08-04 01:31:35.173 UTC [498] STATEMENT:  SELECT * FROM pg_stat_statements LIMIT 1 /pghero/
2023-08-04 09:38:02 zealot-postgres-1  | 2023-08-04 01:38:02.232 UTC [1] LOG:  received fast shutdown request
2023-08-04 09:38:02 zealot-postgres-1  | 2023-08-04 01:38:02.233 UTC [1] LOG:  aborting any active transactions
2023-08-04 09:38:02 zealot-postgres-1  | 2023-08-04 01:38:02.235 UTC [1] LOG:  background worker "logical replication launcher" (PID 28) exited with exit code 1
2023-08-04 09:38:02 zealot-postgres-1  | 2023-08-04 01:38:02.237 UTC [23] LOG:  shutting down
2023-08-04 09:38:02 zealot-postgres-1  | 2023-08-04 01:38:02.248 UTC [1] LOG:  database system is shut down
2023-08-04 09:38:06 zealot-postgres-1  |
2023-08-04 09:38:06 zealot-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-08-04 09:38:06 zealot-postgres-1  |
2023-08-04 09:38:06 zealot-postgres-1  | 2023-08-04 01:38:06.950 UTC [1] LOG:  starting PostgreSQL 12.15 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-08-04 09:38:06 zealot-postgres-1  | 2023-08-04 01:38:06.950 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-08-04 09:38:06 zealot-postgres-1  | 2023-08-04 01:38:06.950 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-08-04 09:38:06 zealot-postgres-1  | 2023-08-04 01:38:06.952 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-04 09:38:06 zealot-postgres-1  | 2023-08-04 01:38:06.962 UTC [22] LOG:  database system was shut down at 2023-08-04 01:38:02 UTC
2023-08-04 09:38:06 zealot-postgres-1  | 2023-08-04 01:38:06.966 UTC [1] LOG:  database system is ready to accept connections
2023-08-04 09:39:00 zealot-postgres-1  | 2023-08-04 01:39:00.478 UTC [45] ERROR:  relation "pg_stat_statements" does not exist at character 15
2023-08-04 09:39:00 zealot-postgres-1  | 2023-08-04 01:39:00.478 UTC [45] STATEMENT:  SELECT * FROM pg_stat_statements LIMIT 1 /pghero/
2023-08-04 09:39:00 zealot-postgres-1  | 2023-08-04 01:39:00.526 UTC [46] ERROR:  relation "pg_stat_statements" does not exist at character 15
2023-08-04 09:39:00 zealot-postgres-1  | 2023-08-04 01:39:00.526 UTC [46] STATEMENT:  SELECT * FROM pg_stat_statements LIMIT 1 /pghero/
2023-08-04 09:39:06 zealot-postgres-1  | 2023-08-04 01:39:06.506 UTC [46] ERROR:  relation "pg_stat_statements" does not exist at character 15
2023-08-04 09:39:06 zealot-postgres-1  | 2023-08-04 01:39:06.506 UTC [46] STATEMENT:  SELECT * FROM pg_stat_statements LIMIT 1 /pghero/
2023-08-04 09:39:06 zealot-postgres-1  | 2023-08-04 01:39:06.573 UTC [46] ERROR:  pg_stat_statements must be loaded via shared_preload_libraries
2023-08-04 09:39:06 zealot-postgres-1  | 2023-08-04 01:39:06.573 UTC [46] STATEMENT:  SELECT * FROM pg_stat_statements LIMIT 1 /pghero/
2023-08-04 09:45:37 zealot-postgres-1  | 2023-08-04 01:45:37.731 UTC [1] LOG:  received fast shutdown request
2023-08-04 08:59:33 zealot-redis-1     | 1:C 04 Aug 2023 00:59:33.176 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-08-04 08:59:33 zealot-redis-1     | 1:C 04 Aug 2023 00:59:33.176 # Redis version=7.0.12, bits=64, commit=00000000, modified=0, pid=1, just started
2023-08-04 08:59:33 zealot-redis-1     | 1:C 04 Aug 2023 00:59:33.176 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2023-08-04 08:59:33 zealot-redis-1     | 1:M 04 Aug 2023 00:59:33.177 * monotonic clock: POSIX clock_gettime
2023-08-04 08:59:33 zealot-redis-1     | 1:M 04 Aug 2023 00:59:33.177 * Running mode=standalone, port=6379.
2023-08-04 08:59:33 zealot-redis-1     | 1:M 04 Aug 2023 00:59:33.177 # Server initialized
2023-08-04 08:59:33 zealot-redis-1     | 1:M 04 Aug 2023 00:59:33.180 * Ready to accept connections
2023-08-04 09:02:25 zealot-redis-1     | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
2023-08-04 09:02:25 zealot-redis-1     | 1:M 04 Aug 2023 01:02:25.405 # User requested shutdown...
2023-08-04 09:02:25 zealot-redis-1     | 1:M 04 Aug 2023 01:02:25.405 * Saving the final RDB snapshot before exiting.
2023-08-04 09:02:25 zealot-redis-1     | 1:M 04 Aug 2023 01:02:25.408 * DB saved on disk
2023-08-04 09:02:25 zealot-redis-1     | 1:M 04 Aug 2023 01:02:25.408 # Redis is now ready to exit, bye bye...
2023-08-04 09:02:48 zealot-redis-1     | 1:C 04 Aug 2023 01:02:48.485 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-08-04 09:02:48 zealot-redis-1     | 1:C 04 Aug 2023 01:02:48.485 # Redis version=7.0.12, bits=64, commit=00000000, modified=0, pid=1, just started
2023-08-04 09:02:48 zealot-redis-1     | 1:C 04 Aug 2023 01:02:48.485 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.485 * monotonic clock: POSIX clock_gettime
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.485 * Running mode=standalone, port=6379.
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.485 # Server initialized
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.487 * Loading RDB produced by version 7.0.12
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.487 * RDB age 23 seconds
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.487 * RDB memory usage when created 1.49 Mb
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.487 * Done loading RDB, keys loaded: 7, keys expired: 0.
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.487 * DB loaded from disk: 0.000 seconds
2023-08-04 09:02:48 zealot-redis-1     | 1:M 04 Aug 2023 01:02:48.487 * Ready to accept connections
2023-08-04 09:07:49 zealot-redis-1     | 1:M 04 Aug 2023 01:07:49.082 * 100 changes in 300 seconds. Saving...
2023-08-04 09:07:49 zealot-redis-1     | 1:M 04 Aug 2023 01:07:49.083 * Background saving started by pid 71
2023-08-04 09:07:49 zealot-redis-1     | 71:C 04 Aug 2023 01:07:49.108 * DB saved on disk
2023-08-04 09:07:49 zealot-redis-1     | 71:C 04 Aug 2023 01:07:49.109 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:07:49 zealot-redis-1     | 1:M 04 Aug 2023 01:07:49.184 * Background saving terminated with success
2023-08-04 09:12:50 zealot-redis-1     | 1:M 04 Aug 2023 01:12:50.042 * 100 changes in 300 seconds. Saving...
2023-08-04 09:12:50 zealot-redis-1     | 1:M 04 Aug 2023 01:12:50.043 * Background saving started by pid 140
2023-08-04 09:12:50 zealot-redis-1     | 140:C 04 Aug 2023 01:12:50.052 * DB saved on disk
2023-08-04 09:12:50 zealot-redis-1     | 140:C 04 Aug 2023 01:12:50.053 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:12:50 zealot-redis-1     | 1:M 04 Aug 2023 01:12:50.147 * Background saving terminated with success
2023-08-04 09:17:51 zealot-redis-1     | 1:M 04 Aug 2023 01:17:51.003 * 100 changes in 300 seconds. Saving...
2023-08-04 09:17:51 zealot-redis-1     | 1:M 04 Aug 2023 01:17:51.004 * Background saving started by pid 198
2023-08-04 09:17:51 zealot-redis-1     | 198:C 04 Aug 2023 01:17:51.009 * DB saved on disk
2023-08-04 09:17:51 zealot-redis-1     | 198:C 04 Aug 2023 01:17:51.010 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:17:51 zealot-redis-1     | 1:M 04 Aug 2023 01:17:51.109 * Background saving terminated with success
2023-08-04 09:22:52 zealot-redis-1     | 1:M 04 Aug 2023 01:22:52.093 * 100 changes in 300 seconds. Saving...
2023-08-04 09:22:52 zealot-redis-1     | 1:M 04 Aug 2023 01:22:52.096 * Background saving started by pid 262
2023-08-04 09:22:52 zealot-redis-1     | 262:C 04 Aug 2023 01:22:52.104 * DB saved on disk
2023-08-04 09:22:52 zealot-redis-1     | 262:C 04 Aug 2023 01:22:52.105 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:22:52 zealot-redis-1     | 1:M 04 Aug 2023 01:22:52.198 * Background saving terminated with success
2023-08-04 09:27:53 zealot-redis-1     | 1:M 04 Aug 2023 01:27:53.040 * 100 changes in 300 seconds. Saving...
2023-08-04 09:27:53 zealot-redis-1     | 1:M 04 Aug 2023 01:27:53.045 * Background saving started by pid 322
2023-08-04 09:27:53 zealot-redis-1     | 322:C 04 Aug 2023 01:27:53.054 * DB saved on disk
2023-08-04 09:27:53 zealot-redis-1     | 322:C 04 Aug 2023 01:27:53.054 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:27:53 zealot-redis-1     | 1:M 04 Aug 2023 01:27:53.146 * Background saving terminated with success
2023-08-04 09:32:54 zealot-redis-1     | 1:M 04 Aug 2023 01:32:54.099 * 100 changes in 300 seconds. Saving...
2023-08-04 09:32:54 zealot-redis-1     | 1:M 04 Aug 2023 01:32:54.101 * Background saving started by pid 381
2023-08-04 09:32:54 zealot-redis-1     | 381:C 04 Aug 2023 01:32:54.109 * DB saved on disk
2023-08-04 09:32:54 zealot-redis-1     | 381:C 04 Aug 2023 01:32:54.109 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:32:54 zealot-redis-1     | 1:M 04 Aug 2023 01:32:54.204 * Background saving terminated with success
2023-08-04 09:37:55 zealot-redis-1     | 1:M 04 Aug 2023 01:37:55.079 * 100 changes in 300 seconds. Saving...
2023-08-04 09:37:55 zealot-redis-1     | 1:M 04 Aug 2023 01:37:55.080 * Background saving started by pid 440
2023-08-04 09:37:55 zealot-redis-1     | 440:C 04 Aug 2023 01:37:55.089 * DB saved on disk
2023-08-04 09:37:55 zealot-redis-1     | 440:C 04 Aug 2023 01:37:55.090 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:37:55 zealot-redis-1     | 1:M 04 Aug 2023 01:37:55.185 * Background saving terminated with success
2023-08-04 09:38:02 zealot-redis-1     | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
2023-08-04 09:38:02 zealot-redis-1     | 1:M 04 Aug 2023 01:38:02.242 # User requested shutdown...
2023-08-04 09:38:02 zealot-redis-1     | 1:M 04 Aug 2023 01:38:02.242 * Saving the final RDB snapshot before exiting.
2023-08-04 09:38:02 zealot-redis-1     | 1:M 04 Aug 2023 01:38:02.244 * DB saved on disk
2023-08-04 09:38:02 zealot-redis-1     | 1:M 04 Aug 2023 01:38:02.244 # Redis is now ready to exit, bye bye...
2023-08-04 09:38:06 zealot-redis-1     | 1:C 04 Aug 2023 01:38:06.920 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-08-04 09:38:06 zealot-redis-1     | 1:C 04 Aug 2023 01:38:06.920 # Redis version=7.0.12, bits=64, commit=00000000, modified=0, pid=1, just started
2023-08-04 09:38:06 zealot-redis-1     | 1:C 04 Aug 2023 01:38:06.920 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.921 * monotonic clock: POSIX clock_gettime
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.921 * Running mode=standalone, port=6379.
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.921 # Server initialized
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.923 * Loading RDB produced by version 7.0.12
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.923 * RDB age 4 seconds
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.923 * RDB memory usage when created 1.54 Mb
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.923 * Done loading RDB, keys loaded: 10, keys expired: 0.
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.923 * DB loaded from disk: 0.000 seconds
2023-08-04 09:38:06 zealot-redis-1     | 1:M 04 Aug 2023 01:38:06.923 * Ready to accept connections
2023-08-04 09:43:07 zealot-redis-1     | 1:M 04 Aug 2023 01:43:07.063 * 100 changes in 300 seconds. Saving...
2023-08-04 09:43:07 zealot-redis-1     | 1:M 04 Aug 2023 01:43:07.064 * Background saving started by pid 69
2023-08-04 09:43:07 zealot-redis-1     | 69:C 04 Aug 2023 01:43:07.074 * DB saved on disk
2023-08-04 09:43:07 zealot-redis-1     | 69:C 04 Aug 2023 01:43:07.075 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:43:07 zealot-redis-1     | 1:M 04 Aug 2023 01:43:07.167 * Background saving terminated with success
2023-08-04 09:45:37 zealot-redis-1     | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
2023-08-04 09:45:37 zealot-redis-1     | 1:M 04 Aug 2023 01:45:37.781 # User requested shutdown...
2023-08-04 09:45:37 zealot-redis-1     | 1:M 04 Aug 2023 01:45:37.781 * Saving the final RDB snapshot before exiting.
2023-08-04 09:45:37 zealot-redis-1     | 1:M 04 Aug 2023 01:45:37.784 * DB saved on disk
2023-08-04 09:45:37 zealot-redis-1     | 1:M 04 Aug 2023 01:45:37.784 # Redis is now ready to exit, bye bye...
2023-08-04 09:45:41 zealot-redis-1     | 1:C 04 Aug 2023 01:45:41.450 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-08-04 09:45:41 zealot-redis-1     | 1:C 04 Aug 2023 01:45:41.450 # Redis version=7.0.12, bits=64, commit=00000000, modified=0, pid=1, just started
2023-08-04 09:45:41 zealot-redis-1     | 1:C 04 Aug 2023 01:45:41.450 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.451 * monotonic clock: POSIX clock_gettime
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.451 * Running mode=standalone, port=6379.
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.451 # Server initialized
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.453 * Loading RDB produced by version 7.0.12
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.453 * RDB age 4 seconds
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.453 * RDB memory usage when created 1.54 Mb
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.453 * Done loading RDB, keys loaded: 10, keys expired: 0.
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.453 * DB loaded from disk: 0.000 seconds
2023-08-04 09:45:41 zealot-redis-1     | 1:M 04 Aug 2023 01:45:41.453 * Ready to accept connections
2023-08-04 09:50:42 zealot-redis-1     | 1:M 04 Aug 2023 01:50:42.017 * 100 changes in 300 seconds. Saving...
2023-08-04 09:50:42 zealot-redis-1     | 1:M 04 Aug 2023 01:50:42.018 * Background saving started by pid 78
2023-08-04 09:50:42 zealot-redis-1     | 78:C 04 Aug 2023 01:50:42.022 * DB saved on disk
2023-08-04 09:50:42 zealot-redis-1     | 78:C 04 Aug 2023 01:50:42.022 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:50:42 zealot-redis-1     | 1:M 04 Aug 2023 01:50:42.118 * Background saving terminated with success
2023-08-04 09:55:43 zealot-redis-1     | 1:M 04 Aug 2023 01:55:43.081 * 100 changes in 300 seconds. Saving...
2023-08-04 09:55:43 zealot-redis-1     | 1:M 04 Aug 2023 01:55:43.084 * Background saving started by pid 138
2023-08-04 09:55:43 zealot-redis-1     | 138:C 04 Aug 2023 01:55:43.091 * DB saved on disk
2023-08-04 09:55:43 zealot-redis-1     | 138:C 04 Aug 2023 01:55:43.091 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 09:55:43 zealot-redis-1     | 1:M 04 Aug 2023 01:55:43.187 * Background saving terminated with success
2023-08-04 10:00:44 zealot-redis-1     | 1:M 04 Aug 2023 02:00:44.010 * 100 changes in 300 seconds. Saving...
2023-08-04 10:00:44 zealot-redis-1     | 1:M 04 Aug 2023 02:00:44.011 * Background saving started by pid 202
2023-08-04 10:00:44 zealot-redis-1     | 202:C 04 Aug 2023 02:00:44.018 * DB saved on disk
2023-08-04 10:00:44 zealot-redis-1     | 202:C 04 Aug 2023 02:00:44.018 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 10:00:44 zealot-redis-1     | 1:M 04 Aug 2023 02:00:44.117 * Background saving terminated with success
2023-08-04 10:05:45 zealot-redis-1     | 1:M 04 Aug 2023 02:05:45.055 * 100 changes in 300 seconds. Saving...
2023-08-04 10:05:45 zealot-redis-1     | 1:M 04 Aug 2023 02:05:45.057 * Background saving started by pid 263
2023-08-04 10:05:45 zealot-redis-1     | 263:C 04 Aug 2023 02:05:45.062 * DB saved on disk
2023-08-04 10:05:45 zealot-redis-1     | 263:C 04 Aug 2023 02:05:45.062 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 10:05:45 zealot-redis-1     | 1:M 04 Aug 2023 02:05:45.166 * Background saving terminated with success
2023-08-04 10:10:46 zealot-redis-1     | 1:M 04 Aug 2023 02:10:46.043 * 100 changes in 300 seconds. Saving...
2023-08-04 10:10:46 zealot-redis-1     | 1:M 04 Aug 2023 02:10:46.046 * Background saving started by pid 324
2023-08-04 10:10:46 zealot-redis-1     | 324:C 04 Aug 2023 02:10:46.056 * DB saved on disk
2023-08-04 10:10:46 zealot-redis-1     | 324:C 04 Aug 2023 02:10:46.056 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 10:10:46 zealot-redis-1     | 1:M 04 Aug 2023 02:10:46.154 * Background saving terminated with success
2023-08-04 10:15:47 zealot-redis-1     | 1:M 04 Aug 2023 02:15:47.079 * 100 changes in 300 seconds. Saving...
2023-08-04 10:15:47 zealot-redis-1     | 1:M 04 Aug 2023 02:15:47.081 * Background saving started by pid 383
2023-08-04 10:15:47 zealot-redis-1     | 383:C 04 Aug 2023 02:15:47.090 * DB saved on disk
2023-08-04 10:15:47 zealot-redis-1     | 383:C 04 Aug 2023 02:15:47.090 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 10:15:47 zealot-redis-1     | 1:M 04 Aug 2023 02:15:47.189 * Background saving terminated with success
2023-08-04 10:20:48 zealot-redis-1     | 1:M 04 Aug 2023 02:20:48.054 * 100 changes in 300 seconds. Saving...
2023-08-04 10:20:48 zealot-redis-1     | 1:M 04 Aug 2023 02:20:48.058 * Background saving started by pid 442
2023-08-04 10:20:48 zealot-redis-1     | 442:C 04 Aug 2023 02:20:48.066 * DB saved on disk
2023-08-04 10:20:48 zealot-redis-1     | 442:C 04 Aug 2023 02:20:48.066 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 10:20:48 zealot-redis-1     | 1:M 04 Aug 2023 02:20:48.165 * Background saving terminated with success
2023-08-04 09:45:37 zealot-postgres-1  | 2023-08-04 01:45:37.735 UTC [1] LOG:  aborting any active transactions
2023-08-04 09:45:37 zealot-postgres-1  | 2023-08-04 01:45:37.739 UTC [1] LOG:  background worker "logical replication launcher" (PID 28) exited with exit code 1
2023-08-04 09:45:37 zealot-postgres-1  | 2023-08-04 01:45:37.740 UTC [23] LOG:  shutting down
2023-08-04 09:45:37 zealot-postgres-1  | 2023-08-04 01:45:37.753 UTC [1] LOG:  database system is shut down
2023-08-04 09:45:41 zealot-postgres-1  |
2023-08-04 09:45:41 zealot-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-08-04 09:45:41 zealot-postgres-1  |
2023-08-04 09:45:41 zealot-postgres-1  | 2023-08-04 01:45:41.478 UTC [1] LOG:  starting PostgreSQL 12.15 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-08-04 09:45:41 zealot-postgres-1  | 2023-08-04 01:45:41.478 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-08-04 09:45:41 zealot-postgres-1  | 2023-08-04 01:45:41.478 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-08-04 09:45:41 zealot-postgres-1  | 2023-08-04 01:45:41.479 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-04 09:45:41 zealot-postgres-1  | 2023-08-04 01:45:41.490 UTC [22] LOG:  database system was shut down at 2023-08-04 01:45:37 UTC
2023-08-04 09:45:41 zealot-postgres-1  | 2023-08-04 01:45:41.493 UTC [1] LOG:  database system is ready to accept connections
2023-08-04 10:25:49 zealot-redis-1     | 1:M 04 Aug 2023 02:25:49.048 * 100 changes in 300 seconds. Saving...
2023-08-04 10:25:49 zealot-redis-1     | 1:M 04 Aug 2023 02:25:49.050 * Background saving started by pid 502
2023-08-04 10:25:49 zealot-redis-1     | 502:C 04 Aug 2023 02:25:49.056 * DB saved on disk
2023-08-04 10:25:49 zealot-redis-1     | 502:C 04 Aug 2023 02:25:49.056 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
2023-08-04 10:25:49 zealot-redis-1     | 1:M 04 Aug 2023 02:25:49.155 * Background saving terminated with success

重新拉取下最新的 nightly tag 版本，最近做了一点修改，上面的没什么眉目，如果最新的测试版还是有问题，如果要解决这个问题只能麻烦把上传的 ipa 发我一份了，大概方法：

确认 docker-compose.yml 是不是 tryzealot/zealot:nightly 如果不是更换成
重新拉取 docker-compose pull
重启 zealot

这是我当前的版本

哥，日志没有地方显示哪里有问题啊...

你好，我昨天刚更新的，也遇到了同样的错误，出现好几次了，日志里也同样没有显示问题

可否把 ipa 单独发我一份 https://cowtransfer.com/

问题长时间无回应暂时关闭

现在重新安装后，已经好了，可以关闭了。谢谢耐心等待和回复。🫣


feat(accordion): replace chevron svg with css

affects: @fremtind/jkl-accordion-react, @fremtind/jkl-accordion
📥 Proposed changes
Replace the chevron svg in the accordion component with a styled DOM element
☑ Submission checklist

[x] I have read the CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[x] yarn build works locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

💬 Further comments
This fixes an issue with CI

@all-contributors please add @gbrownlee for projectManagement

@all-contributors please add @piofinn  for review

@all-contributors please add @gbrownlee for eventOrganizing


TypeError: _this.io.of(...).in(...).clients is not a function

fixed-laravel-echo-server start

  ╔═══╗            ╔╗     ╔╗                        ╔╗      ╔═══╗    ╔╗           ╔═══╗
  ║╔══╝            ║║     ║║                        ║║      ║╔══╝    ║║           ║╔═╗║
  ║╚══╗╔╗╔╗╔╗╔══╗╔═╝║     ║║   ╔══╗ ╔═╗╔══╗ ╔╗╔╗╔══╗║║      ║╚══╗╔══╗║╚═╗╔══╗     ║╚══╗╔══╗╔═╗╔╗╔╗╔══╗╔═╗
  ║╔══╝╠╣╚╬╬╝║╔╗║║╔╗║╔═══╗║║ ╔╗╚ ╗║ ║╔╝╚ ╗║ ║╚╝║║╔╗║║║ ╔═══╗║╔══╝║╔═╝║╔╗║║╔╗║╔═══╗╚══╗║║╔╗║║╔╝║╚╝║║╔╗║║╔╝
 ╔╝╚╗  ║║╔╬╬╗║║═╣║╚╝║╚═══╝║╚═╝║║╚╝╚╗║║ ║╚╝╚╗╚╗╔╝║║═╣║╚╗╚═══╝║╚══╗║╚═╗║║║║║╚╝║╚═══╝║╚═╝║║║═╣║║ ╚╗╔╝║║═╣║║
 ╚══╝  ╚╝╚╝╚╝╚══╝╚══╝     ╚═══╝╚═══╝╚╝ ╚═══╝ ╚╝ ╚══╝╚═╝     ╚═══╝╚══╝╚╝╚╝╚══╝     ╚═══╝╚══╝╚╝  ╚╝ ╚══╝╚╝
----------------------------------------------------------------------------------------------------------
|                                   Powered By AbdoPrDZ "Just Code It";                                  |
----------------------------------------------------------------------------------------------------------

version 0.1.1
Starting server...
✔  Running at localhost on port 8443
✔  Listening for http events...
✔  Listening for redis events...
Server ready!
[2024-04-23T12:33:07.071Z] - ⚠ Client r9bNP2X5DCc1JYYzAAAB connected
/usr/lib/node_modules/@abdopr/fixed-laravel-echo-server/dist/channels/presence-channel.js:35
                .clients(function (error, clients) {
                 ^

TypeError: _this.io.of(...).in(...).clients is not a function
    at /usr/lib/node_modules/@abdopr/fixed-laravel-echo-server/dist/channels/presence-channel.js:35:18
    at new Promise (<anonymous>)
    at PresenceChannel.removeInactive (/usr/lib/node_modules/@abdopr/fixed-laravel-echo-server/dist/channels/presence-channel.js:31:16)
    at /usr/lib/node_modules/@abdopr/fixed-laravel-echo-server/dist/channels/presence-channel.js:20:23
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v20.12.1

I have been using https://github.com/tlaverdure/laravel-echo-server. Which works ok but two issues.

stuck on old socket.io
"socket.io": "^2.4.0",
"socket.io-client": "^2.3.1",

Server crashes from https://github.com/tlaverdure/laravel-echo-server/pull/535

Using your package which I really hope I can get, my chatbox does not work. All I see in browser console is
WebSocket connection to 'wss://xxx.dev:8443/socket.io/?EIO=4&transport=websocket' failed: Could not connect to the server.

Then error above popped up in terminal.
My chat.js looks like so:
/**
 * Echo exposes an expressive API for subscribing to channels and listening
 * for events that are broadcast by Laravel. Echo and event broadcasting
 * allows your team to easily build robust real-time web applications.
 */
import Echo from 'laravel-echo';
import Vue from 'vue';
import chatbox from '../components/chat/Chatbox.vue';

import client from 'socket.io-client';

window.io = client;

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: import.meta.env.VITE_ECHO_ADDRESS,
    forceTLS: true,
    withCredentials: true,
    transports: ['websocket'],
    enabledTransports: ['wss'],
});

new Vue({
    el: '#vue',
    components: { chatbox: chatbox },
});

This is my package.json
{
  "private": true,
  "scripts": {
    "dev": "vite",
    "build": "vite build"
  },
  "dependencies": {
    "@abdopr/fixed-laravel-echo-server": "^0.1.1",
    "ajv": "^8.10.0",
    "alpinejs": "^3.9.1",
    "axios": "^0.26.1",
    "cross-env": "^7.0.3",
    "dayjs": "^1.11.0",
    "laravel-echo": "^1.11.4",
    "laravel-mix-purgecss": "^6.0.0",
    "postcss": "^8.4.12",
    "resolve-url-loader": "^5.0.0",
    "sass": "^1.49.9",
    "sass-loader": "^12.6.0",
    "socket.io": "4.7.5",
    "socket.io-client": "4.7.5",
    "sweetalert2": "^11.4.6",
    "virtual-select-plugin": "^1.0.26",
    "vue": "^2.6.14",
    "vue-loader": "^15.9.8",
    "vue-template-compiler": "^2.6.14"
  },
  "devDependencies": {
    "@vitejs/plugin-vue2": "^2.3.1",
    "laravel-vite-plugin": "^1.0.1",
    "prettier-plugin-blade": "^2.0.0",
    "vite": "^5.0.12",
    "vite-plugin-static-copy": "^1.0.1"
  },
  "type": "module"
}

Working perfect now. Thank you for taking this fork on.


Set Allow header for 405 requests

Allow header is required when returning a 405, https://developer.mozilla.org/en-US/docs/web/http/status/405

Looks good, thanks!


⚠ Science Web Services - QState has degraded performance

In b8345ca, Science Web Services - QState (https://sws.labbricks.com/qstate/) experienced degraded performance:

HTTP code: 200
Response time: 1284 ms

Resolved: Science Web Services - QState performance has improved in a6640cf after 49 minutes.


Stuck at the middle of ViewPager.

Every time I swipe back and forth, it keeps stuck in the middle of ViewPager.
This glitch happens on Pixel API 30 emulator.
I/Choreographer: Skipped 139 frames!  The application may be doing too much work on its main thread.

Did you find a solution to this problem?
Please

The app has since been migrated to Compose. Please reopen a new issue if you are still seeing this on the current version of the app


Added custom found/lost events to markerControls for three.js core

What kind of change does this PR introduce?
Feature: Added custom markerFound and markerLost events to markerControls in three.js core
How can we test it?
On any three.js + ar.js app, using markers (Pattern or Barcode) add this listeners and you should see events triggered specifying which marker was found/lost.
window.addEventListener("markerFound", function (e) {
  console.log("Found")
  console.log(e.detail);
});
window.addEventListener("markerLost", function (e) {
  console.log("Lost")
  console.log(e.detail);
});

Summary
I needed to trigger some stuff based on markers visibility and found that Three.js core didn't have this custom events as A-Frame Core has.
Explored different approaches and found that this was the simpler one, since it does not require to change anything on artoolkit api when processing the frame. Visibility check is done after frame is fully processed (confidence tests are already done).
Does this PR introduce a breaking change?
No.
Please TEST your PR before proposing it. Specify here what device you have used for tests, version of OS and version of Browser
Tested with a three.js + ar.js app with 12 pattern markers in the following browsers:

Microsoft Edge Version 89.0.774.45 on Windows 10
Microsoft Edge Version <IP_ADDRESS>40 on Android 10 - Motorola One Action
Firefox Version 86 on Windows 10
Firefox Version 86.1.1 on Android 10 - Motorola One Action
Google Chrome Version 89.0.4389.72 on Windows 10
Google Chrome Version 89.0.4389.72 on Android 10 - Motorola One Action
Safari Version 14.4 on iPad OS 14.14 - iPad Pro 2020

Other information
Not sure if I have to run the make/build command as part of the PR, please let me know. Also if you need a sample app or some help for running tests just let me know.
Added markerControl complete object to event detail, not sure if we want to pass all this info or just some parts of it, like the patternUrl or ID etc.

@fcor Haven't tested the code but from a first sight it seems good to me! Will see if i have a bit of time for testing...

Looks good to me! Thank tou. Merging. We will build on a next release.


Canvas image API should support animated images

 Issue by Hixie
Friday Jul 17, 2015 at 18:20 GMT
Originally opened as https://github.com/flutter/engine/issues/91

From @collinjackson on June 2, 2015 19:19
This will require us to change the Sky engine API to support indexing into individual image frames
Copied from original issue: domokit/mojo#189

 Comment by Hixie
Saturday Jul 25, 2015 at 06:02 GMT

Maybe the canvas image API doesn't have to, if the Image API does it itself and just fires a callback every time the image changes (so we can schedule a new paint).

The API is now structured properly.  (We don't actually support animated images, but that's a separate issue.)


Can't plot dataframe

I'm trying to plot a DataFrame and it wasn't working, so I tried loading the data set from the read_csv docs. It also failed. I think I'm missing something, but I've been successful with matplotlib before. :)
from pandas import read_csv
import matplotlib.pyplot as plt

junk = read_csv('bar.csv')
fig = plt.figure()
junk.plot()
fig.savefig('/tmp/foo3.png')

bar.csv
year,indiv,zit,xit
1977,"A",1.2,.6
1977,"B",1.5,.5
1977,"C",1.7,.8
1978,"A",.2,.06
1978,"B",.7,.2
1978,"C",.8,.3
1978,"D",.9,.5
1978,"E",1.4,.9
1979,"C",.2,.15
1979,"D",.14,.05
1979,"E",.5,.15
1979,"F",1.2,.5
1979,"G",3.4,1.9
1979,"H",5.4,2.7
1979,"I",6.4,1.2

I get the folowing error:
python /tmp/plot.py
Traceback (most recent call last):
  File "/tmp/plot.py", line 6, in <module>
    junk.plot()
  File "/home/mharrison/work/pandas/env/lib/python2.6/site-packages/pandas/core/frame.py", line 3225, in plot
    ax.plot(x, y, label=str(col), **kwds)
  File "/home/mharrison/work/pandas/env/lib/python2.6/site-packages/matplotlib/axes.py", line 3783, in plot
    for line in self._get_lines(*args, **kwargs):
  File "/home/mharrison/work/pandas/env/lib/python2.6/site-packages/matplotlib/axes.py", line 317, in _grab_next_args
    for seg in self._plot_args(remaining, kwargs):
  File "/home/mharrison/work/pandas/env/lib/python2.6/site-packages/matplotlib/axes.py", line 275, in _plot_args
    linestyle, marker, color = _process_plot_format(tup[-1])
  File "/home/mharrison/work/pandas/env/lib/python2.6/site-packages/matplotlib/axes.py", line 93, in _process_plot_format
    if fmt.find('--')>=0:
AttributeError: 'numpy.ndarray' object has no attribute 'find'

The problem is that the indiv column is non-numeric. I could probably catch the exception and add a more helpful error message

That makes sense. Yes, a better error would be wonderful. I'll try to post some code to plot the above, then close this.


Configured data policies prevent activation of flows which use the 'shared_commondataservice' and 'shared_sharepointonline' connectors

Getting this error when trying to start the flow to create document library.

It sounds like your DLP policy doesn't allow you to use both CDS and SPO in a flow.  You'll either need to change your DLP policy or make this table by hand.

i added the connectors while ago.  after i posted the question i tried again - and now it is wokring,

Wonderful. I also just noticed that we didn't include this in the list of connectors needed, so I updated the pre-reqs documentations to note.
Thanks for using CoE!


Fix error LNK1107 and undeclared identifier 'IPPROTO_TCP'

When I Update etcd-cpp-apiv3 version from 0.14.2 to 0.15.2, I get two build error:
fatal error LNK1107: invalid or corrupt file: cannot read at 0x330

error: use of undeclared identifier 'IPPROTO_TCP'

The first error was because the target etcd-cpp-api-core-objects linked the wrong libprotobufd.dll file instead of the .lib file, I used the usage provided by vcpkg to link the correct .lib file to fix this error.
Another error was because IPPROTO_TCP was missing declaration "<netinet/in.h>", I added it to fix this error.

Hi @JonLiu1993,
Thanks for fixing these issues. For (1), from https://cmake.org/cmake/help/latest/module/FindProtobuf.html I think you set Protobuf_USE_STATIC_LIBS before find_package(etcd-cpp-api).
Using protobuf::libprotobufraises a bit of concern as I remember it causes issues in some environments. I remember Protobuf_LIBRARIES works well on vcpkgs's CI.
By the way thanks for bumping up the version in vcpkg registry.

I have updated the pr to prefer protobuf::libprotobuf.

I have updated the pr to prefer protobuf::libprotobuf.

Thanks for your prompt and professional reply! 👍


TS-4720 back port

HttpTransact defaults content length to -1, meaning that if the request has no content length header it will be -1. These checks weren't taking that into consideration -- meaning client aborts during requests with no content length (GET for example) would leave the origin session open until another timeout kicked in.
(cherry picked from commit a075556602d77d79f5a02e2a36053abfa92703f0)

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1210/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1103/ for details.


Add Property to Hide Gridlines in Clinical Data Grid

Feature Request
Description
The Clinical Data Grid needs a property to allow consumers to hide gridlines
Additional Context / Screenshots
N/A
@ Mentions
@tbiethman

Closing as Not a Supportable Feature by UX.
The Terra-clinical-data-grid was intentionally designed to create worklists, a specific type of complex tables, so the design and features of the data-grid are intentionally limited to provide a narrower set of capabilities than other similar basic Terra components (terra-table, etc.).
I'll reach out to discuss your needs further and see if one of the other Terra components, perhaps like the extremely flexible terra-cell-grid, might be better suited to what you may be needing.


2moons.cc site problem.

I can not connect to the 2moons.cc site.

2moons.cc is not maintained by me.


Can't use string ref in ModuleFederationPlugin exposes ?

Bug report
I try to modify an old project code with using ModuleFederationPlugin , but get an error in the browser . Because i use string ref in the exposes module. Although i can use React.crateRef  to fix this issue, but will take a lot of time. Any else way to solve this?
What is the current behavior?
Set the exposes module called Home  in ModuleFederationPlugin  :

In the home module , has a string ref :

Error in the browser :

Other relevant information:
webpack version:  5.18.0
Node.js version: 12.19.0
Operating System: windows 10
Additional tools: visual studio code

Not related to webpack, please read the error message, also you ignore How we can reproduce it, so won't fix, sorry

Not related to webpack, please read the error message, also you ignore How we can reproduce it, so won't fix, sorry

Thanks for your reply . I make the react shared in singleton , it solve this issue.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.28 to before v4.4.289",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=46abc02175b3c246dd5141d878f565a8725060c9",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=25e9f88c7e3cc35f5e3d3db199660d28a15df639"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "46abc02175b3c246dd5141d878f565a8725060c9",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "25e9f88c7e3cc35f5e3d3db199660d28a15df639",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "phy: mdio: fix memory leak\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.4.289 by commit 25e9f88c7e3cc35f5e3d3db199660d28a15df639, it was introduced in version v2.6.28 by commit 46abc02175b3c246dd5141d878f565a8725060c9. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001494


Update last first event id in each batch

LGTM

Coverage increased (+0.1%) to 67.133% when pulling be6c336da480a5ffa5c7762d3700c531c5b67375 on fix-lastfirsteventid into c41974e153cfe2b9824fc219e0160f863ca0d54b on master.


No C global state in modules

This PR removes most of the C global state in Titan modules, the only thing that is left is a cache for tags. We are passing all the tests that we currently have, but I still need to write tests for functionality that this PR enables, such as loading the same Titan module from two distinct Lua states (their module variables will be local to the state, as it should be), or linking module B inside module A.so, while having a separate B.so, and having the B that A imports and the other B require'd by Lua refer to the same module instance.
The canonical module instances for each Lua state, as well the canonical tags and metatables for record types, are kept in the Lua registry, but we only need to hit the registry at module initialization, no accesses to the registry are done on normal execution of Titan code.
One thing that we lose is the ability to leverage GCC's constant propagation to propagate local module variables that have numeric values that can be know at compile-time, but we can add a constant propagation AST->AST pass later on.

I am going to try to rebase this on top of master without the primitives
branch, so this can be merged without being held back by the discussion
that is going to be necessary there.
On Thu, May 17, 2018, 22:41 Fabio Mascarenhas<EMAIL_ADDRESS>wrote:

One thing that I also did in this PR was to make the code that runs only
once in module initialization to be as well-behaved as possible in terms of
using the Lua API instead of the internals, which hopefully will make
decrease the surface area for changes between one Lua version to the other.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/titan-lang/titan/pull/233#issuecomment-390068425, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAO_daCd8UCS8K6ke93rD09ttZ-rVg6Lks5tzibPgaJpZM4UDzX-
.

I am going to try to rebase this PR on top of master without the primitives branch, so this can be merged without being held back by the discussion that is going to be necessary there.

The easiest way to this is probably to do a new commit to this branch that removes the foreign functions, then squashing the the commits from both branches together and applying then on master...
But the objection was to foreign functions exposed to the programmer, not to the concept itself, so I can just not expose then for now.

Ok, now this is a dead-end branch, closing this PR and killing the branch. Thanks for all the fish!


refactor: Candlestick dataset options

Refactor to remove workaround for candlestick dataset options, my PR was merged at the source in chartjs-chart-financial v0.2.0.

Fixed by #178


Move generated documentation to hpx-docs repo

This is still WIP until I see that everything gets pushed correctly to the new repo. Currently it's https://github.com/STEllAR-GROUP/hpx-docs, and the docs would be at https://stellar-group.github.io/hpx-docs/latest/html/index.html, but feel free to suggest another name for it. Once this is finalized I'll clean up the gh-pages branch here.

Thanks !


Log errors: unknown user 'npm'

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

No - using native Linux install

Are you sure you're not using someone else's docker image?

No

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
Installed using:
https://github.com/tteck/Proxmox/raw/main/ct/nginxproxymanager.sh
Running a standard instance of NginxProxyManager, getting the following error message.
In 'journalctl -xe'
Apr 06 14:25:04 nginxproxymanager node[148]: [4/6/2024] [2:25:04 PM] [Setup ] <80> <9A> CommandError: error: /etc/logrotate.d/nginx-proxy-manager:2 unknown user 'npm'
Apr 06 14:25:04 nginxproxymanager node[148]: error: found error in /data/logs/_access.log /data/logs//access.log , skipping
Apr 06 14:25:04 nginxproxymanager node[148]: error: /etc/logrotate.d/nginx-proxy-manager:16 unknown user 'npm'
Apr 06 14:25:04 nginxproxymanager node[148]: error: found error in /data/logs/_error.log /data/logs//error.log , skipping
Apr 06 14:25:04 nginxproxymanager node[148]: at /app/lib/utils.js:16:13
Apr 06 14:25:04 nginxproxymanager node[148]: at ChildProcess.exithandler (node:child_process:410:5)
Apr 06 14:25:04 nginxproxymanager node[148]: at ChildProcess.emit (node:events:513:28)
Apr 06 14:25:04 nginxproxymanager node[148]: at maybeClose (node:internal/child_process:1100:16)
Apr 06 14:25:04 nginxproxymanager node[148]: at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

I have the exact same issue after updating my nginx proxy manager LXC using ttkeck's update script. Have you managed to solve it?

root cause and workaround: https://github.com/tteck/Proxmox/issues/2745#issuecomment-2138811196

root cause and workaround: tteck/Proxmox#2745 (comment)

Thanks, I had notice this and already replaced those lines, but now it's the openresty service that doesn't seem to run:
"nginx: [emerg] open() "/run/nginx/nginx.pid" failed (2: No such file or directory)", seems like the PID file for nginx doesn't get created for whatever reason
I'll keep on digging


[2.3 beta] The install dir is tracked by git, but deleted by Symphony

As the title sais, the install dir is tracked by git, but deleted by Symphony after the installation, which freaks out my git installation with the message I have a lot of changed files.

From what I've experienced I believe all those changed files are more related to Windows and your core.autocrlf setting than deleting a simple directory.

Hmm, no that can't be it, as I recently switched to mac..
I can also confirm the entire folder is gone, by the way.

There's no other way to manage a folder that needs versioning, and then removing after install. I personally don't think that a commit of deleted files after install is that bad really.

On Wed Dec 14 07:40:15 2011, Huib Keemink wrote:

As the title sais, the install dir is tracked by git, but deleted by Symphony after the installation, which freaks out my git installation with the message I have a lot of changed files.

Reply to this email directly or view it on GitHub:
https://github.com/symphonycms/symphony-2/issues/971

Don't really see a way around this one. How's it any different to
tracking the update.php file?

The reason I submitted this is because I prefer to develop on an installed installation, so I can test what I have done. In the previous versions, the update.php file did not pop up (I believe because it was in the gitignore file, but I am not sure). It is quite annoying to have to select the modified files from the dropdown list (when using a GUI) or remembering which files were changed and adding them manually (from the commandline).
Isn't there a way to include a file in the repository, but ignore changes happening to it?

Again, from what I recall this did not happen in previous versions. Please tell me if I'm going crazy though.

Why don't you just keep the directory when developing locally?
By the way, update.php always popped up, too.

I can see your point Hiub, the way I recommend to do it is to have the git repo for developing, then sym link the relevant files to another dir for installing and testing. That way you can avoid having to do commits in an installed directory, while retaining the clean download for submissions.
Sounds a little long-way-round, but it would work.

What about a new config-parameter that hides that particular message?

If Notify is pulled into the core, you'll be able to dismiss that message.

Oh, yes, if I could just dismiss the message that would be the best solution. Thanks all for thinking along!


UnmanagedRackPlugin : Unable to attach computer system chassis with chassistype 'RackMount' to a Rack

Steps to Reproduce:

Start URP service
Add computer system chassis with ChassisType 'RackMount' in odimra
Add URP to odimra
Create Rack Group
Create Rack and do a patch operation on the uri returned in Location in response header as mentioned in 4th step
Attach Computer System chassis to rack

Expected Response code: 200
Actual Response:
400 Bad Request
{
"error": {
"code": "Base.1.6.1.GeneralError",
"message": "An error has occurred. See ExtendedInfo for more information.",
<EMAIL_ADDRESS>[
{
<EMAIL_ADDRESS>"#Message.v1_0_8.Message",
"MessageId": "Base.1.6.1.PropertyValueNotInList",
"Message": "The value [{/redfish/v1/Chassis/<chassis_id>}] for the property Links.Contains is not in the list of acceptable values. Couldn't confirm existence of one or more requested 'Links.Contains' elements or one of them is not a pointer to Chassis asset",
"MessageArgs": [
"[{/redfish/v1/Chassis/<chassis_id>}]",
"Links.Contains"
],
"Severity": "Warning",
"Resolution": "Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed."
}
]
}
}

Could you attach URP's logs?

Could you attach URP's logs?

Below are the URP logs:
Jan  4 16:18:11.290 [INFO] Starting URP v4cff452-20201229-dirty
Jan  4 16:18:11.336 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:101] POST: /ODIM/v1/Startup -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.basicAuthHandler.handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:98] POST: /EventService/Events -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*eventHandler).handleEvent-fm() and 1 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:106] GET: /ODIM/v1/Managers/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getPluginManagerHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:110] GET: /ODIM/v1/Chassis/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getChassisHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:102] GET: /ODIM/v1/Status -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.pluginStatusController.getPluginStatus-fm() and 1 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:105] GET: /ODIM/v1/Managers -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getManagersHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:109] GET: /ODIM/v1/Chassis -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getChassisCollectionHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:111] DELETE: /ODIM/v1/Chassis/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*deleteChassisHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:112] POST: /ODIM/v1/Chassis -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*postChassisHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:113] PATCH: /ODIM/v1/Chassis/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*chassisUpdateHandler).handle-fm() and 2 more
Jan  4 16:18:11.338 [DEBU] Application: running using 1 host(s)
Jan  4 16:18:11.338 [DEBU] Host: addr is URP:45003
Jan  4 16:18:11.338 [DEBU] Host: virtual host is URP:45003
Jan  4 16:18:11.338 [DEBU] Host: register server shutdown on interrupt(CTRL+C/CMD+C)
Jan  4 16:25:58.692 [INFO] 200 568.116µs <IP_ADDRESS> GET /ODIM/v1/Status
Jan  4 16:25:58.786 [INFO] 200 665.364µs <IP_ADDRESS> GET /ODIM/v1/Managers
Jan  4 16:25:58.827 [INFO] 200 197.292µs <IP_ADDRESS> GET /ODIM/v1/Managers/99999999-9999-9999-9999-999999999999
Jan  4 16:26:17.146 [INFO] 201 3.272256ms <IP_ADDRESS> POST /ODIM/v1/Chassis
Jan  4 16:26:29.135 [INFO] 201 1.240833ms <IP_ADDRESS> POST /ODIM/v1/Chassis
Jan  4 16:26:49.703 [INFO] 200 661.358µs <IP_ADDRESS> GET /ODIM/v1/Chassis
Jan  4 16:27:20.870 [ERRO] cannot read validate https://ODIMRA/redfish/v1/Chassis: &{{Base.1.6.1.GeneralError Get https://<IP_ADDRESS>:45000/redfish/v1/Chassis: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs []}}
Jan  4 16:27:20.870 [INFO] 400 5.872646ms <IP_ADDRESS> PATCH /ODIM/v1/Chassis/7299564e-2c9b-55c1-a35e-8cfae21808c2

Below are the URP logs:
Jan  4 16:18:11.290 [INFO] Starting URP v4cff452-20201229-dirty
Jan  4 16:18:11.336 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:101] POST: /ODIM/v1/Startup -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.basicAuthHandler.handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:98] POST: /EventService/Events -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*eventHandler).handleEvent-fm() and 1 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:106] GET: /ODIM/v1/Managers/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getPluginManagerHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:110] GET: /ODIM/v1/Chassis/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getChassisHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:102] GET: /ODIM/v1/Status -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.pluginStatusController.getPluginStatus-fm() and 1 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:105] GET: /ODIM/v1/Managers -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getManagersHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:109] GET: /ODIM/v1/Chassis -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*getChassisCollectionHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:111] DELETE: /ODIM/v1/Chassis/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*deleteChassisHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:112] POST: /ODIM/v1/Chassis -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*postChassisHandler).handle-fm() and 2 more
Jan  4 16:18:11.337 [DEBU] [./home/anjum/go/src/github.com/URP_4jan/ODIM/plugin-unmanaged-racks/rest/module.go:113] PATCH: /ODIM/v1/Chassis/{id} -> github.com/ODIM-Project/ODIM/plugin-unmanaged-racks/rest.(*chassisUpdateHandler).handle-fm() and 2 more
Jan  4 16:18:11.338 [DEBU] Application: running using 1 host(s)
Jan  4 16:18:11.338 [DEBU] Host: addr is URP:45003
Jan  4 16:18:11.338 [DEBU] Host: virtual host is URP:45003
Jan  4 16:18:11.338 [DEBU] Host: register server shutdown on interrupt(CTRL+C/CMD+C)
Jan  4 16:25:58.692 [INFO] 200 568.116µs <IP_ADDRESS> GET /ODIM/v1/Status
Jan  4 16:25:58.786 [INFO] 200 665.364µs <IP_ADDRESS> GET /ODIM/v1/Managers
Jan  4 16:25:58.827 [INFO] 200 197.292µs <IP_ADDRESS> GET /ODIM/v1/Managers/99999999-9999-9999-9999-999999999999
Jan  4 16:26:17.146 [INFO] 201 3.272256ms <IP_ADDRESS> POST /ODIM/v1/Chassis
Jan  4 16:26:29.135 [INFO] 201 1.240833ms <IP_ADDRESS> POST /ODIM/v1/Chassis
Jan  4 16:26:49.703 [INFO] 200 661.358µs <IP_ADDRESS> GET /ODIM/v1/Chassis
Jan  4 16:27:20.870 [ERRO] cannot read validate https://ODIMRA/redfish/v1/Chassis: &{{Base.1.6.1.GeneralError Get https://<IP_ADDRESS>:45000/redfish/v1/Chassis: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs []}}
Jan  4 16:27:20.870 [INFO] 400 5.872646ms <IP_ADDRESS> PATCH /ODIM/v1/Chassis/7299564e-2c9b-55c1-a35e-8cfae21808c2

Also, we are using docker for deployment of odimra which deploys urp also with odimra i.e we are not doing make separately for urp.

Also, we are using docker for deployment of odimra which deploys urp also with odimra i.e we are not doing make separately for urp.

Regarding to following message:
Jan 4 16:27:20.870 [ERRO] cannot read validate https://ODIMRA/redfish/v1/Chassis: &{{Base.1.6.1.GeneralError Get https://<IP_ADDRESS>:45000/redfish/v1/Chassis: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs []}}
URP cannot validate certificate of ODIM. URP deployment (described in docker-compose.yml) has to specify value for PLUGIN_ODIM_URL which is compatible with ODIM's NB API certificate.

Regarding to following message:
Jan 4 16:27:20.870 [ERRO] cannot read validate https://ODIMRA/redfish/v1/Chassis: &{{Base.1.6.1.GeneralError Get https://<IP_ADDRESS>:45000/redfish/v1/Chassis: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs []}}
URP cannot validate certificate of ODIM. URP deployment (described in docker-compose.yml) has to specify value for PLUGIN_ODIM_URL which is compatible with ODIM's NB API certificate.

Fixed.

Fixed.

Verified - Attach computer system chassis to Rack works now

Verified - Attach computer system chassis to Rack works now


Support for requirements clarification around semantic versioning of projects.

May be subsumed by Project Completion work.

Closing for now. DCP 2 team will clarify versioning requirements.


Font Request: DejaVu

DejaVu
Latest Release
License
Additional context
It's a derivative of Bitstream Vera which is also available via OFL.

@ScottGuthart,

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
The above packages have been published onto NPM. Thanks!


Extension's initialize and after_configuration called twice

Using Ruby 2.3.0 with Middleman 4.1.9
$ bundle show middleman
/Users/amirn/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/middleman-4.1.9

How to reproduce:
middleman init mm_app
[snip]
cd mm_app
mkdir lib
curl -L https://git.io/vKqiH > lib/my_extension.rb
echo -e "require 'lib/my_extension.rb'\nactivate :my_extension\n$(cat config.rb)" >! config.rb

middleman server
MyExtension: init
MyExtension: after_configuration
== The Middleman is loading
MyExtension: init
MyExtension: after_configuration
== View your site at "http://localhost:4567", "http://<IP_ADDRESS>:4567"
== Inspect your site configuration at "http://localhost:4567/__middleman", "http://<IP_ADDRESS>:4567/__middleman"

I'm getting this issue too with Ruby 2.3.1
As a work around I'm setting a static flag that i can check incase my code has already executed.

While confusing, I suggest making extensions pure or idempotent enough to handle this. Middleman can restart itself during dev, so it's possible things will be initialized even more times.
In this case, we load extensions twice on purpose. First so they can install global config options to the command line, then again for normal execution. I believe there is app.config[:mode] === :config you can check to see if it's the first run or the normal execution.

I think the fact that middleman loads the config.rb twice on startup, and possibly reloaded during during development, should be clearly stated in the documentation. It's common for users to modify config.rb and that's a pretty important tidbit of information to know.


fix(10): Add badges

Context
Badges are pretty :rose:
Objective

Add badges

Additonal changes:

Lower package install size by making smaller test images
Run npm run coverage on test success to send data to coveralls.io

References

Issue: https://github.com/ScottyFillups/simple-thumbnail/issues/10

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can't use Swift_Transport_FailoverTransport because it no longer has a constructor.

When using Swift_FailoverTransport::newInstance($transports);, it no longer works because the failover transport no longer has a __construct, and Swift_FailoverTransport tries to call it.
This happened in the "[Swift] various dead code cleanups, simplifications and phpdoc fixes" commit.

fixed in 13d4a53


Feat/exemplar units page

Description

Adds exempla fixtures
Adds units to exempla page

Acceptance Criteria:

[x]  Do all the putting together of the page
[x]  Add the yellow boxes in and their titles and associated title
[x]  Title and copy
[x]  Quote bit (if this is annoying, just don’t worry about it on the first pass)
[x]  List of exemplar units

Issue(s)
Fixes #
How to test

Go to https://deploy-preview-1881--oak-web-application.netlify.thenational.academy/beta/teachers-2023/early-release-units
Compare to Figma designs

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

@JBR90 This is likely a pre-existing issue, but the font weight of the X lessons link text is 400, whereas in Figma it looks like it should be 600. A weight of 600 would also make it consistent with other bolded links seen elsewhere on the page.

Another (likely pre-existing) issue with these unit tiles is that, on mobile, the column width of the text content is proportionally too wide, which means that there's not enough space between the text content and the subject icon.

:tada: This PR is included in version 1.235.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


🚀 [Feature Request] - Title Add Search Bar in Community Section

Is your feature request related to a problem ? Please describe. ✍
Yes, the absence of a search bar in the community section makes it challenging for users to locate specific contributors. As the community grows, users may find it increasingly difficult to find individuals without a search function, leading to frustration and inefficiency.
Describe briefly how you would implement this enhancement.
A search bar should be added to the community section to allow users to search for specific members by name or keyword. This feature would improve usability and enhance the overall user experience.

Enhancement:

The implementation of the search bar should be user-friendly and intuitive, allowing for seamless integration with the existing community section layout.

Describe briefly how you would implement this enhancement.
Here are some steps to implement this enhancement:

Design the Search Bar UI:

 Create a visually appealing and accessible search bar design that fits the existing layout of the community section.

Implement Search Functionality:

Use JavaScript or the relevant framework to filter through the list of community members based on user input in real-time.
Ensure the search function is case-insensitive to improve user experience.

Test the Feature:

Conduct usability testing to ensure the search functionality works correctly and is easy for users to understand.

Additional context or screenshots
This feature would significantly enhance the user experience by allowing quick access to community members. Here is a screenshot of the current community section without the search bar for reference:

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

Can I work on this, if it is okay ? please assign if yes


Data Audit save anonymous changes

Hi,
I'm using oro platform 3.1. There is a route in my application which allows anonymous users to submit a form. In my action method I am changing some fields of an existing entity record and persist it to database. When a registered user open the view page of the record and check the change history, the author is saved as system admin. Is there a way to save the author as anonymous/guest in this situation?
Thanks in advance,
Farzam

OroPlatform has no customer portal and out of the box its functionality doesn't work with pages accessible by anonymous users. The final behavior will depend on the security settings you have added for this new route.
Please share the configuration of the firewall that covers this new route.

Thank you for your quick response. In config/security.yml:
...
    firewalls:
        test:
            pattern:            ^/test/*
            anonymous:          true
            security:           false
...
    access_control:
           - { path: ^/test/*, roles: IS_AUTHENTICATED_ANONYMOUSLY }
...

When you open the page in a dev environment, does Symfony profiler say that user is not logged in?

Here is a screenshot of my page in dev environment:


Docs: Implement scripts

The documentation site will require supporting Javascript. Need a task to manage (compile. concat, etc.) needed scripts.

A script tag should be added to the master template for site-wide scripts.
A scripts block should be added to the master template so that each page can include it's own JS if necessary

PR already merged #686