DISABLE_SPRING=1 doesn't seem to work

Open
#521 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rails, ruby
Domain
tooling

Research direction

Start by tracing how the DISABLE_SPRING=1 environment variable is handled and reproduce the CI behavior that produces the directory-monitoring error. Done means Spring is globally prevented from running when the variable is exported, without the listener error appearing in the logs.

Written by the indexing model from the issue text.

Description

bug

We don't want to use spring at all on our CI server, so we export the var DISABLE_SPRING=1, which is supposed to stop spring from running. However, we are seeing this in the logs: FATAL: Listen error: unable to monitor directories for changes., which is also failing our builds. How can we globally disable spring?

Dominant language
Ruby
Stars
2.8k
Forks
342
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rails/spring

All issues in rails/spring

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.