-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Improve ASCII tree representation in docs #2294
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
Conversation
features/directory_structure.feature
Outdated
@@ -36,10 +36,10 @@ Feature: Directory Structure | |||
`RSpec.describe` block with the `type: :controller` metadata: | |||
|
|||
```ruby | |||
# spec/legacy/things_controller_spec.rb | |||
# spec/legacy/things_controller_spec.rb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that the "weird character" is there for a reason, it tricks gherkin parser to ignore the comment because otherwise, the parser expects the free-form description to end after the comment. The original pull request doesn't explain nor highlight that it was done. I'll revert this change.
Tried newer cucumber
/gherkin
just to make sure it's not a bug in earlier versions.
└── views | ||
├── books | ||
└── books |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sincerely yours, ASCII artist.
Merge when green. |
Again error on jruby but it seems different this time... But maybe link to jruby/jruby#6125
|
Yep. And in another case (Rails 6.0) the error is different:
|
Filed jruby/jruby#6131 |
To be honest, I am surprised that CI errors from other dependencies are so often catch by our CI. I don't think we are living that much on the edge with unstable release. |
Can we change to a more stable version of JRuby? |
Lets see what happens to #2296 (edit, no effect) |
One answer ruby/racc#132 (comment)
|
I'm waiting for Travis to update their RVM cache http://rubies.travis-ci.org/ubuntu/14.04/x86_64/jruby-head to the release that would include the fix to |
I think we can just set allow failures for now... |
Chances are it'll never recover, and the number of those job issues will grow. E.g. I expect to see a Rails-related failure next when We're in a tricky situation here. Rails doesn't ensure compatibility with JRuby, not to say the bleeding edge of it, JRuby doesn't ensure compatibility with RSpec nor RuboCop that we use as part of our build. What we can do:
WDYT? |
I'm fine with reducing our jruby build to not run rubocop |
Surprisingly enough, the build is green. |
Yes because I allowed failures from jruby |
I mean both JRuby jobs were green https://travis-ci.org/github/rspec/rspec-rails/jobs/665433957 https://travis-ci.org/github/rspec/rspec-rails/jobs/665433954 |
😂 Maybe we can already undo my changes then |
Maybe because of ruby/racc#132 (comment) ? |
IDK, I expected
to remain, but it fixed itself :D |
This reverts commit 3e36b8f. Related: - #2294 (comment)
This reverts commit 3e36b8f. Related: - #2294 (comment)
No description provided.