Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using guard-teabag stops guard-rspec from working #4

Open
marten opened this issue Apr 4, 2013 · 2 comments
Open

Using guard-teabag stops guard-rspec from working #4

marten opened this issue Apr 4, 2013 · 2 comments

Comments

@marten
Copy link

marten commented Apr 4, 2013

➜  ~/rgoc/roqua git:(382m|timeline) be guard start -d
23:02:08 - DEBUG - Command execution: git rev-parse HEAD 2>/dev/null
Starting the Teabag server...
23:02:10 - ERROR - Invalid Guardfile, original error is:
> [#] can't modify frozen String
[...]

Beyond this, everything seems to start up okay, except Guard no longer does anything when changing files which guard-rspec is watching. guard-teabag itself is correctly handling file system changes, it's just that it breaks RSpec for some reason.

If I comment out the teabag section in my Guardfile RSpec works again, and the error message goes away. I don't actually need to set up any watch things for this issue to appear.

Any clues on how to proceed debugging?

@jejacks0n
Copy link
Owner

Are you using the one that was generated?

@marten
Copy link
Author

marten commented Apr 5, 2013

Not quite, so I checked, and that one worked fine. However, it was also added completely at the end, which got me experimenting, and as long as I put teabag below RSpec, everything works. Here's our Guardfile in the version that now works: https://gist.github.com/marten/5317010

So if I move that rspec_tests! line to below the guard :teabag block, then the message about frozen strings re-appears and RSpec stops working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants