SystemStackError (stack level too deep) during checkout payment step on fresh installation

[chatnuere]

SystemStackError (stack level too deep) during checkout payment step on fresh installation

Environment

• Solidus version: Latest (fresh installation)
• Rails version: 7.2.2.1
• Ruby version: 3.2.2
• Database: PostgreSQL
• Installation type: Starter option from generator (sample store)

Issue Description

I'm encountering a SystemStackError (stack level too deep) when trying to complete the payment step during checkout on a completely fresh Solidus installation. This happens every time I attempt to process a payment, whether using the default payment method or external payment providers like Stripe.

Steps to Reproduce

1. Fresh Solidus installation using the starter generator option
2. Navigate to the sample store
3. Add a product to cart
4. Proceed through checkout steps
5. Fill out payment information on the payment step
6. Submit payment form
7. Error occurs immediately

Error Details

The error occurs in CheckoutsController#update method, specifically in the update_order method at line 38. The stack trace shows an infinite recursion:

SystemStackError (stack level too deep):

app/controllers/checkouts_controller.rb:38:in `update_order'
app/controllers/checkouts_controller.rb:15:in `update'
app/controllers/store_controller.rb:28:in `block in lock_order'
app/controllers/store_controller.rb:28:in `lock_order'

Request Parameters

The request that triggers the error is a PATCH to /checkout/update/payment with standard payment form data including:

• Payment method ID
• Credit card information (filtered in logs)
• Billing address details
• Payment source attributes

Database Activity

The logs show normal database activity up until the error:

• Order loading and locking mechanisms work correctly
• Stock validation passes
• Payment method validation succeeds
• Address lookup completes successfully
• Error occurs after order mutex cleanup

What I've Tried

• Tested with different payment methods (default and Stripe)
• Verified this is a completely clean installation with no custom modifications
• Searched through existing issues and discussions
• Confirmed all dependencies are properly installed

Additional Context

This appears to be a configuration issue since it's happening on a fresh installation with the provided sample data. The error suggests there might be an infinite loop in the order update process, but I haven't been able to identify the root cause.

Has anyone encountered a similar issue with recent Rails/Ruby versions? Any suggestions for debugging steps or potential configuration fixes would be greatly appreciated.

Request for Help

I'm really hoping someone in the community might have encountered something similar or could point me in the right direction. As someone new to Solidus, I'm a bit stuck and would greatly appreciate any insights, debugging tips, or suggestions you might have.

Specifically, I'm looking for:

1. Potential causes of this infinite recursion during payment processing
2. Debugging steps to identify where the loop is occurring
3. Known compatibility issues with Rails 7.2.2.1 and Ruby 3.2.2
4. Configuration settings that might prevent this issue

Thanks in advance for taking the time to read through this! The Solidus community seems really supportive and I'm excited to get this working and start contributing back. 🙏

---

P.S.: This post has been formatted with the help of an LLM to ensure clarity - English isn't my first language and I wanted to make sure the technical details were communicated as clearly as possible for the community.

[chatnuere]

seems to be working when using main branch

gem 'solidus', github: 'solidusio/solidus'

[benjaminwil]

Hey there. If you were looking for a bit more context about this issue: it's due to a recent update to the state_machines dependency.

The reason things are working on main is because there was a recent merge to pin to an older version of state_machines: #6286

If you want to use the current release of Solidus, you can add the pin to your Gemfile until there is a new release:

gem "state_machines", "~> 0.6"