Skip to content

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

Merged
merged 1 commit into from
Mar 25, 2020
Merged

Improve ASCII tree representation in docs #2294

merged 1 commit into from
Mar 25, 2020

Conversation

pirj
Copy link
Member

@pirj pirj commented Mar 21, 2020

No description provided.

@pirj pirj self-assigned this Mar 21, 2020
@@ -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
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually,

image

Copy link
Member Author

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
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sincerely yours, ASCII artist.

@JonRowe
Copy link
Member

JonRowe commented Mar 21, 2020

Merge when green.

@benoittgt
Copy link
Member

benoittgt commented Mar 22, 2020

Again error on jruby but it seems different this time... But maybe link to jruby/jruby#6125

An error occurred while loading spec_helper. - Did you mean?

                    rspec ./spec/spec_helper.rb

Failure/Error:

  ControllerAssertionDelegator = RSpec::Rails::AssertionDelegator.new(

    ActionDispatch::Assertions::RoutingAssertions

  )

LoadError:

  no such file to load -- racc/info

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/activesupport-5.2.4.2/lib/active_support/dependencies.rb:291:in `block in require'

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/activesupport-5.2.4.2/lib/active_support/dependencies.rb:257:in `load_dependency'

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/activesupport-5.2.4.2/lib/active_support/dependencies.rb:291:in `require'

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/activesupport-5.2.4.2/lib/active_support/dependencies.rb:291:in `block in require'

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/activesupport-5.2.4.2/lib/active_support/dependencies.rb:257:in `load_dependency'

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/activesupport-5.2.4.2/lib/active_support/dependencies.rb:291:in `require'

# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/nokogiri-1.9.1-java/lib/nokogiri/css/parser.rb:7:in `<main>'

@pirj
Copy link
Member Author

pirj commented Mar 22, 2020

Yep. And in another case (Rails 6.0) the error is different:

An error occurred while loading spec_helper.
Failure/Error: require 'rails/all'

NameError:
  uninitialized constant ActionDispatch::Routing::RouteSet
# /home/travis/build/rspec/bundle/jruby/2.5.0/gems/railties-6.0.2.2/lib/rails/engine.rb:537:in `routes'

@pirj
Copy link
Member Author

pirj commented Mar 22, 2020

Rails 6.0.2.2 is out
image

@pirj
Copy link
Member Author

pirj commented Mar 22, 2020

Filed jruby/jruby#6131

@benoittgt
Copy link
Member

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.

@JonRowe
Copy link
Member

JonRowe commented Mar 23, 2020

Can we change to a more stable version of JRuby?

@JonRowe
Copy link
Member

JonRowe commented Mar 23, 2020

Lets see what happens to #2296 (edit, no effect)

@pirj pirj changed the title Remove weird symbols Improve ASCII tree representation in docs Mar 23, 2020
@benoittgt
Copy link
Member

benoittgt commented Mar 24, 2020

One answer ruby/racc#132 (comment)

Different error now. No jruby/jruby#6131

@pirj
Copy link
Member Author

pirj commented Mar 24, 2020

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 racc.
Strongly doubt that it will fix the second issue with uninitialized constant ActionDispatch::Routing::RouteSet though.

@JonRowe
Copy link
Member

JonRowe commented Mar 24, 2020

I think we can just set allow failures for now...

@pirj
Copy link
Member Author

pirj commented Mar 24, 2020

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 racc/info is fixed.

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:

  • extract RuboCop part from the main build, and only run it for 2.3, 2.4, 2.5, 2.6 and 2.7, skip it for JRuby, as the syntax is basically the same (as 2.5) - less possibilities to fail, more coverage, more total builds, total run time probably on par
  • propose JRuby to take care of adding builds for Rails, 5.2, and 6-stable so that in case they make some breaking changes, they don't get merged (and if Rails patch version breaks JRuby, they know of it, not us reporting it) - our jruby-head builds don't suffer

WDYT?

@JonRowe
Copy link
Member

JonRowe commented Mar 24, 2020

I'm fine with reducing our jruby build to not run rubocop

@pirj pirj merged commit eb3377b into master Mar 25, 2020
@pirj pirj deleted the fix-doc-layout branch March 25, 2020 14:28
@pirj
Copy link
Member Author

pirj commented Mar 25, 2020

Surprisingly enough, the build is green.

@JonRowe
Copy link
Member

JonRowe commented Mar 25, 2020

Surprisingly enough, the build is green.

Yes because I allowed failures from jruby

@pirj
Copy link
Member Author

pirj commented Mar 25, 2020

@JonRowe
Copy link
Member

JonRowe commented Mar 25, 2020

😂 Maybe we can already undo my changes then

@benoittgt
Copy link
Member

Maybe because of ruby/racc#132 (comment) ?

@pirj
Copy link
Member Author

pirj commented Mar 25, 2020

IDK, I expected

NameError:
  uninitialized constant ActionDispatch::Routing::RouteSet

to remain, but it fixed itself :D

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

Successfully merging this pull request may close these issues.

3 participants