Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #13514

Closed
Open
Created Feb 16, 2016 by Drew Blessing@dblessingMaintainer

Rails console goes funky after several commands since Rails upgrade

Since RC1 was deployed to GitLab.com the Rails console has consistently gone wonky after 1-2 queries. @yorickpeterse @balameb and I have all seen it. Is this a Rails bug (searched, but didn't find much) or something else?

Unsure if related, but certain things also cause a segfault in the console. @yorickpeterse saw this and so did I today.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking