Top Menu

Jump to content
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    Home
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      OpenProject ID Google

Side Menu

Collapse project menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Expand project menu
Development
  1. OpenProject Community
  2. OpenProject
  3. Forums
  4. Development
  5. Trouble to make migration

Trouble to make migration

Added by Dailson Campos almost 8 years ago

Hello everyone!

I’m trying to run this command ./bin/rake db:migrate db:seed db:test:prepare, but the terminal return this error “SystemStackError: stack level too deep”

Settings:
Rails 5.0.6
Ruby 2.4.2

Anyone may help me, please?


Replies (1)

RE: Trouble to make migration - Added by Jorge Salcedo over 7 years ago

Hello Dailson,

While running OpenProject in my local, version 7.3.0, I faced this issue after deleting the Gemfile.lock and generating it back again.

I just restored it back from the repository and everything went back to normal.

My guess is that a library gets upgraded when regenerating the lock file, and this causes the issue.

Hope it helps

  • (1 - 1/1)
Loading...