-
Notifications
You must be signed in to change notification settings - Fork 151
Update foreman package dependencies #3070
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
|
could you also add nodejs-jed as a dependency ? imho theforeman/foreman#5342 will be merged today. |
fa04f35 to
e607669
Compare
|
It fails with a compilation error that I can't quite explain: |
|
Interesting.. I will look more into it tomorrow :) |
|
any chance this is similar to theforeman/foreman#6043 ? /cc @sharvit |
tbrisker
left a comment
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.
Lgtm
tbrisker
left a comment
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.
Oops, on mobile, didn't notice the failing build
|
@ekohl does the node_modules directory contain |
|
@ohadlevy no, it's an indirect dependency that's bundled via patternfly. |
|
@ekohl where can I find the resulting node_modules directory? is it available on koji somewhere? |
|
There is a small diff between patternfly and foreman scss loaders, but I am not sure it is causing the problem: Foreman: Patternfly: |
|
looks like thie is the offensive code: https://github.com/patternfly/patternfly-react/blob/master/packages/patternfly-3/patternfly-react/sass/patternfly-react/_type-ahead-select.scss#L1 - patternfly-react seems to expect that on the top level. |
|
On Tue, Oct 9, 2018 at 11:32 AM Tomer Brisker ***@***.***> wrote:
looks like thie is the offensive code:
https://github.com/patternfly/patternfly-react/blob/master/packages/patternfly-3/patternfly-react/sass/patternfly-react/_type-ahead-select.scss#L1
- patternfly-react seems to expect that on the top level.
if we can't fix it by tomorrow i'd rather we revert the search change and
postpone it to after branching rather than delay branching or branch with
broken code.
in that case, can't we simply package it as a top level?
… —
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3070 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABOx07KMcyX4NtmhHtIryAAU340viwRks5ujF85gaJpZM4XMqsV>
.
|
|
@tbrisker I find it odd, as patternfly require a lot of packages, and so far we had no problems with yet, I assume here there is something to do with how the node_modules we generate looks like using packages, if we have a way to get a sample of it, maybe we can figure out whats exactly wrong. regardless, I would hope just packaging it as top level can solve the issue? |
|
I do think packaging it at the top level would be a short term fix. Previously the package was unbundled so perhaps that's why we weren't seeing it. Perhaps the |
|
I stand corrected: after |
No, I'm saying we have most packages at top level but with patternfly we switched from unbundled to bundled in the latest update. That's why we might be seeing this now and not before. |
so in this case, maybe even reverting won't help as its just the first error out of a few others...? |
|
OK, what is the next step than? Should we return patternfly-react to be unbundled? |
|
In case we don't want the |
I am leaning to that yes. |
|
@ekohl let's do that then, we need to have working nightlies prior to branching. |
|
For completeness: #3077 |
|
When https://ci.theforeman.org/job/foreman-packaging-release/147/ is done the tests can be restarted. |
|
[test rpm] |
|
Looks like our repoclosure check doesn't take repositories into account. nodejs-invariant is in the katello repository but Foreman can't use that. Going to do some shuffling |
|
I stand corrected, it was a release issue. foreman-packaging-release can't deal with a package already existing and http://koji.katello.org/koji/buildinfo?buildID=27723 was already built. It was skipped but is tagged to the wrong repo. During the PR it was built locally as a scratch and so repoclosure passed. |
|
[test rpm] |
1 similar comment
|
[test rpm] |
|
Since it's green now, I'm going to merge this. Haven't verified the actual in UI functionality but it'll at least unblock our builds. |
|
Thanks for all the hard effort @ekohl ! |
|
+1 thanks!
…On Wed, Oct 10, 2018, 10:50 PM Tomer Brisker ***@***.***> wrote:
Thanks for all the hard effort @ekohl <https://github.com/ekohl> !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3070 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABOx6t3jCcSRZBTBg_IXmdlWwIMFurqks5ujk-YgaJpZM4XMqsV>
.
|
No description provided.