pundit | Minimal authorization through OO design | REST library

There are three issues with this code snippet.

• Issue-1: max_df and min_df should be both int or both float.
• Issue-2: At the prediction time you have to use the same CountVectorizer.
• Issue-3: At the prediction time you have to use the transform method, not the fit_transform method of CountVectorizer.

Here is an example code that will help you:

What you can do is chain && operators.

As soon as one is false, ruby will not evaluate the others (And the update method will return false).

First of all, the message about DidYouMean is a deprecation warning not an error, it doesn't break your app. It means that usage of DidYouMean::SPELL_CHECKERS is deprecated and will be removed in a future version of ruby. In this case in Ruby 3.3. You shouldn't worry about it until you use versions that are lower than 3.3. It's not your code that triggers the warning. It comes from a gem named Thor. The issue was solved in thor version 1.2.0. You can update the gem by calling bundle update thor.

The actual error comes from the bootsnap gem:

I will create custom permission under RegistrantPolicy to check recommendation allowed or not.

policy:

Ruby's operators have a certain precedence order and thus bind depending on this order (similar to how in math formulas - and ruby - multiplication bind stringer than addition.

Important for your case her eis that the && operator binds stronger than the || operator. Your rule thus uses following implicit precedences (expressed by adding parentheses):

You could try to use something like this:

Its a simple pluralization error. Your model has_many :venues and accepts_nested_attributes_for :venues so you need to use the plural :venues in your form:

Since you're adding venue attributes to the user registration form, you may need to add these attributes to the strong_parameters list so they can be passed to the RegistrationsController#create action.

Devise's documentation shows how to do this: https://github.com/heartcombo/devise#strong-parameters

Ok, found the problem. Turns out that I had copied the setting config.session_store :cache_store in development.rb from a different project I had been working on. However, this setting was added as part of the StimulusReflex setup for that other project.

From the StimulusReflex docs:

Cookie-based session storage is not currently supported by StimulusReflex.

Instead, we enable caching in the development environment so that we can assign our user session data to be managed by the cache store.

The default setting for this option is cookie_store. By changing it to :cache_store without specifying a cache repo, it implements ActionDispatch::Session::CacheStore and defaults to storing it in Rails.cache, which uses the :file_store option, which dumps it in tmp/cache.

However, further down in development.rb, there is some conditional logic that assigns config.cache_store to :null_store if there is no caching-dev.txt file. This implements ActiveSupport::Cache::NullStore, which is "a cache store implementation which doesn't actually store anything."

So because I had not enabled caching with rails dev:cache for this project, the session cache was getting toasted with every request.

LESSON LEARNED: Be very careful when copying config settings from an old project to a new one!