-
Notifications
You must be signed in to change notification settings - Fork 101
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
Fix rubocop offenses #614
Fix rubocop offenses #614
Conversation
I can see one rubocop offense on this cop And another one is |
Tests are failing but I guess not because of the changes here. I need to take a look what's going on there. |
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.
I think the benefit isn't really there with that cop. Looks just like a style thing to me so I'd initially ignore it. Haven't looked at the reversible cop yet
3571981
to
78bc96d
Compare
We can see in #615 that the test suite is already broken. That makes it hard to judge if these items break anything (further) or not. |
In ruby tests, there is one test that is failing everywhere:
I will take a look during this week. The |
78bc96d
to
a710d1d
Compare
This is: foreman_discovery/test/unit/host_discovered_test.rb Lines 263 to 277 in 6aaa8d2
It's updating the legacy fact |
It could also be caching facts via theforeman/foreman@735b401. |
From some testing it does appear to be failing it, which I could reproduce locally. I think #617 fixes that particular test. |
#618 fixes another test that has long been broken. |
a710d1d
to
7dd46ea
Compare
I merged fix for broken |
7dd46ea
to
f0f645a
Compare
@stejskalleos I wouldn't squash commits because it's easier to review the changes per cop |
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.
@archanaserver can you rebase please so the CI will get run on the latest changes?
(You don't have to squash the commits, as Ewoud said)
@stejskalleos it is rebased and running on the latest changes. The checks are failing due to some webpack changes, I have looked into it, this seems like some routing issue and I'm not sure what is the exact issue here. Would you mind taking a look here? |
f0f645a
to
ef0219b
Compare
ef0219b
to
c3eecd6
Compare
@ekohl i can't find why it is failing clearly, would you please help me here? Edit: Also I guess foreman_default_hostgroup this repo theforeman/foreman_default_hostgroup#62 also has similar kind of failure https://github.com/theforeman/foreman_default_hostgroup/actions/runs/8135910181/job/22231270234?pr=62 |
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.
As you noted, we see the failures in other places too. It's being worked on. It doesn't have to block merging.
test "should add a link to navigation" do | ||
get :index, params: {}, session: set_session_user | ||
assert_response :success | ||
assert_includes(response.body, '/discovery_rules/') | ||
end |
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.
You can drop this since #618 removed the assertion and created a better one.
c3eecd6
to
8ad58ac
Compare
@ekohl @stejskalleos would you mind taking a look on the final changes? |
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.
Thanks @archanaserver @ekohl |
No description provided.