smart action, can't access my data about forest-rails HOT 11 OPEN

from forest-rails.

Edit: now half-works... I restarted my rails server (puma) and it started working well. Some tries later it stopped working (and no code modified).

from forest-rails.

I think I'm close to be able to reproduce it every time. It lookalike it behave as such:

1. rails s
2. open forest interface
3. click collections
4. pick selection
5. select row
6. click on action
7. -> fails
8. cmd + c to stop server
9. click on action again (As you see, didn't change page or anything)
10. action works
11. it refreshes the data
12. click on action again
13. -> fails
14. cmd + c to stop server
15. click on action again (As you see, didn't change page or anything)
16. action works
17. ... etc

It might be a problem because of another (auto-loading or other) gem? Below my Gemfile

source 'https://rubygems.org'

ruby "2.4.1"

# Core
gem 'rails', '~> 5.1.2'
gem 'puma', '~> 3.7'
gem 'sass-rails', '~> 5.0'
gem 'coffee-rails', '~> 4.2'
gem 'uglifier', '>= 1.3.0'
gem 'turbolinks', '~> 5'
gem 'json'
gem 'bcrypt'
gem 'pg'

# Front End
gem 'jquery-rails', '~> 4.3.1'
gem 'modernizr-rails'
gem 'will_paginate'
gem 'bootstrap', '~> 4.0.0.beta2.1'

# Admin dasjboard
gem 'forest_liana'

# Backend
gem 'nokogiri'
gem 'sidekiq'
gem 'httparty'

group :development do
  gem 'dotenv-rails'
  gem 'better_errors'
  gem 'listen', '>= 3.0.5', '< 3.2'
  gem 'spring'
  gem 'spring-watcher-listen', '~> 2.0.0'
end

group :production, :staging do
  gem 'rack-timeout'
  gem 'newrelic_rpm'
end

from forest-rails.

Any idea about the problem?

from forest-rails.

Anyone still alive here? Any thoughts on this? Anyone else having this issue or able to reproduce it?

from forest-rails.

Hi @daniel-costa,

I guess the error you have happens a this specific line:
puts Venues.all
Because you're in the Forest::VenuesController
Am I right?

Maybe ::Venues.all could fix the issue?

from forest-rails.

from forest-rails.

If you're using Puma, it might be an issue with Forest support of multithreading in development environment.

Did you try to deploy this code in a staging/production environment? My guess is that it could work perfectly in such non-development environment. (Even though, it remains an issue that should be fixed in development environment.)

from forest-rails.

from forest-rails.

Still no solution here?

from forest-rails.

Can you try:

Rails.application.configure do
  # Settings specified here will take precedence over those in config/application.rb.

  # In the development environment your application's code is reloaded on
  # every request. This slows down response time but is perfect for development
  # since you don't have to restart the web server when you make code changes.
  config.cache_classes = true

  # Do not eager load code on boot.
  config.eager_load = true

to see if it improve things.

from forest-rails.