warden | use process management library for keeping track | Monitoring library

Decoding with let actors = Bundle.main.decode([String: String].self, from: "actors.json") would work if you had a JSON like this:

This seems to a be a known issue with Rails 7 and Devise now. To fix it in the meantime simply add the following line to your devise.rb.

config.navigational_formats = ['*/*', :html, :turbo_stream]

Source: https://github.com/heartcombo/devise/issues/5439

Your XML is not namespace-well-formed: It uses undefined namespace prefixes.

First fix your XML. Then fix your getNamespaceURI() method to return the right namespace URI for each used namespace prefix.

See How does XPath deal with XML namespaces? for an example of a working getNamespaceURI() method.

Okay, I figured it out.

It seems that this is an issue with the Zache gem. See this line:

https://github.com/yegor256/zache/blob/master/lib/zache.rb#L206

This I believe introduces an external sleep.

I was able to fix my code by wrapping the method BEFORE called zache.get

Something like this:

This error is happening because you have the following print statement outside of the function nuke:

If you are going to use ssl then using certbot is an ok solution to use but you should no longer serve http requests so you need to set your server block that listens on port 80 to redirect to an ssl block i.e. a block that listens on port 443. This doesn't look like it is setup to act as a reverse proxy to your rails server either, there should be puma or unicorn or whatever rails server you are running declarations. so none of this really makes sense.

You have a few options set in your config that I am unfamiliar with plus you seem to have the sites_available options mixed in with the nginx.conf file, this is ok but it is not a normal nor very configurable setup, however, because of the few options you have that I am not familiar with I'm not going to comment on your options, I'm just going to make a suggestion that you tidy up your server blocks so that the block listening on port 80 redirects to the port 443 block. You will need to open up your firewall to allow port 443. If using ufw then there is an nginx app you can set otherwise I'll leave you to figure out or ask in a different question how to setup your specific firewall for SSL on port 443.

Anyway, besides the above you should change your port 80 http block to look like this

Try using this

The issue was related to environment variables and not being able to find the correct path for the gems. I found a solution and updated the schedule.rb file.

Can you still use @DataJpaTest?