-
Notifications
You must be signed in to change notification settings - Fork 140
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
Taps Server Error: uninitialized constant Config #143
Comments
Facing the same issue.. |
+1 |
eric1234
added a commit
to eric1234/taps
that referenced
this issue
May 28, 2015
If you wanted to support older versions of Ruby you could test if `RbConfig` was defined and use `Config` if it was not. But `Config` has been deprecated for a while so not sure if it's really necessary to support it anymore so going with the simpler patch. This fixes ricardochimal#143.
stickymess
pushed a commit
to stickymess/taps
that referenced
this issue
Jun 4, 2015
If you wanted to support older versions of Ruby you could test if `RbConfig` was defined and use `Config` if it was not. But `Config` has been deprecated for a while so not sure if it's really necessary to support it anymore so going with the simpler patch. This fixes ricardochimal#143.
+1 |
1 similar comment
+1 |
I don't think this repo is being maintained anymore. This issue (as well as a few others) should be fixed in https://rubygems.org/gems/tapsicle |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Followed all instructions and cannot shake this error....
The text was updated successfully, but these errors were encountered: