Forem Creators and Builders

Discussion on: ArgumentError: wrong number of arguments (given 3, expected 2)

Collapse
akhil profile image
Akhil Naidu Author

Upgrading old Forem instace (old repo) to new Forem (new repo)

surprisingly, this didn't failed; but displaying few errors.

       Using release configuration from last framework (Ruby).
----------> Discovering process types
       Procfile declares types -> release, sidekiq_worker, web
----------> Releasing forem...
---------------> Deploying forem...
---------------> Checking for predeploy task
       No predeploy task found, skipping
---------------> Checking for release task
---------------> Executing release task from Procfile: ./release-tasks.sh
=====> Start of forem release task (48159e5ed) output
       + [[ '' = \b\l\o\c\k\e\d ]]
       + STATEMENT_TIMEOUT=4500000
       + bundle exec rails app_initializer:setup
       == Preparing database ==
       == Performing setup tasks ==
       == Updating Data ==
       == Bust Caches ==
       + bundle exec rake fastly:update_configs
       + bundle exec rails runner 'puts '\''app load success'\'''
       /app/app/services/edge_cache/bust/nginx.rb:44: warning: already initialized constant Net::HTTP::Purge::METHOD
       /app/vendor/bundle/ruby/3.0.0/gems/fastly-3.0.2/lib/fastly/client.rb:166: warning: previous definition of METHOD was here
       /app/app/services/edge_cache/bust/nginx.rb:45: warning: already initialized constant Net::HTTP::Purge::REQUEST_HAS_BODY
       /app/vendor/bundle/ruby/3.0.0/gems/fastly-3.0.2/lib/fastly/client.rb:167: warning: previous definition of REQUEST_HAS_BODY was here
       /app/app/services/edge_cache/bust/nginx.rb:46: warning: already initialized constant Net::HTTP::Purge::RESPONSE_HAS_BODY
       /app/vendor/bundle/ruby/3.0.0/gems/fastly-3.0.2/lib/fastly/client.rb:168: warning: previous definition of RESPONSE_HAS_BODY was here
       app load success
=====> End of forem release task (48159e5ed) output
---------------> App Procfile file found
---------------> DOKKU_SCALE file exists
=====> Processing deployment checks
       No CHECKS file found. Simple container checks will be performed.
       For more efficient zero downtime deployments, create a CHECKS file. See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
---------------> Attempting pre-flight checks (web.1)
       Waiting for 10 seconds ...
       Default container check successful!
       Scheduling old container shutdown for web.1 in 60 seconds
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
---------------> Attempting pre-flight checks (sidekiq_worker.1)
       Waiting for 10 seconds ...
       Default container check successful!
       Scheduling old container shutdown for sidekiq_worker.1 in 60 seconds
---------------> Running post-deploy
---------------> Configuring app.leewardslope.com...(using built-in template)
---------------> Creating https nginx.conf
       Enabling HSTS
---------------> Configuring redirect for 75.119.143.54 to app.leewardslope.com via HTTP 301...
       Reloading nginx
---------------> Renaming containers
       Found previous container(s) (95202fdca051) named forem.sidekiq_worker.1
       Renaming container (95202fdca051) forem.sidekiq_worker.1 to forem.sidekiq_worker.1.1630646260
       Renaming container (629bf973e5c9) adoring_wilson to forem.sidekiq_worker.1
       Found previous container(s) (26be38e39873) named forem.web.1
       Renaming container (26be38e39873) forem.web.1 to forem.web.1.1630646261
       Renaming container (c0b2d3ee2f79) compassionate_lederberg to forem.web.1
---------------> Checking for postdeploy task
       No postdeploy task found, skipping
---------------> Shutting down old containers in 60 seconds
=====> Application deployed:
       http://app.leewardslope.com
       https://app.leewardslope.com
Enter fullscreen mode Exit fullscreen mode