```$ yarn install yarn install v1.22.10 [1/4] Reso...
# ui
i
Copy code
$ yarn install
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.1.2: The platform "linux" is incompatible with this module.
info "fsevents@2.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "workspace-aggregator-4a03fcd2-2d3d-413d-80bf-d5ee1a3df7ab > @nacho-ui/core > @fortawesome/ember-fontawesome > rollup-plugin-node-resolve@5.2.0" has unmet peer dependency "rollup@>=1.11.0".
[4/4] Building fresh packages...
$ chmod +x ./node_modules/husky/husky.js;node ./node_modules/husky/husky.js install
husky > Setting up git hooks
husky > Done
husky > Like husky? You can support the project on Patreon:
husky > <https://www.patreon.com/typicode> šŸ•
Done in 141.62s.
cc @green-football-43791 it's easier to read
g
nice looks good
reading from here, try running
ember s --proxy=<http://localhost:9001>
i
page not found
there we go ^
āœ… 1
i
zsh: command not found: ember
šŸ˜†
g
give that a try- if it seems successful I'd give the gradle command another go
bah
npm install -g ember-cli
?
i
running
After install ember and running the
ember s -- ...
command
No ember-cli-build.js found.
g
did you cd into packages/data-portal?
i
my bad
Copy code
Cannot find module 'nearley'
Require stack:
- /home/pedro/dev/datahub/datahub-web/packages/data-portal/lib/ember-nearley/broccoli-nearley.js
- /home/pedro/dev/datahub/datahub-web/packages/data-portal/lib/ember-nearley/index.js
- /usr/lib/node_modules/ember-cli/lib/models/package-info-cache/package-info.js
- /usr/lib/node_modules/ember-cli/lib/models/package-info-cache/index.js
- /usr/lib/node_modules/ember-cli/lib/models/project.js
- /usr/lib/node_modules/ember-cli/lib/utilities/get-config.js
- /usr/lib/node_modules/ember-cli/lib/utilities/instrumentation.js
- /usr/lib/node_modules/ember-cli/lib/cli/index.js
- /usr/lib/node_modules/ember-cli/bin/ember
g
hmm try running yarn install from data-portal as well
actually before you do-
is there a node_modules directory inside
packages/data-portal
?
i
there is
ok, i got ember s --proxy to run but no connection on localhost:9001
g
what was the output of the command?
i
connection refused
g
that was the full output?
i
Copy code
Proxying to <http://localhost:9001>
WARNING: Detected collisions between .js and .ts files of the same name. This can result in nondeterministic build output; see <https://git.io/JvIwo> for more information.
  - datahub-web/components/ivy-tabs-tablist.{js,ts}
  - datahub-web/helpers/changeset-set.{js,ts}
  - datahub-web/helpers/changeset.{js,ts}
ā ¦ building... [Package /assets/vendor.js]The following dependencies were not found:
  @aduh95/viz.js
  @aduh95/viz.js
You might need to `npm install` the above.
ā § building... [Bundler][BABEL] Note: The code generator has deoptimised the styling of /home/pedro/dev/datahub/datahub-web/packages/data-portal/node_modules/vis/dist/vis.js as it exceeds the max of 500KB.
ā ¼ building... [Bundler][BABEL] Note: The code generator has deoptimised the styling of /home/pedro/dev/datahub/datahub-web/node_modules/lodash/lodash.js as it exceeds the max of 500KB.

Build successful (25756ms) – Serving on <http://localhost:4200/>

Slowest Nodes (totalTime >= 5%)                                        | Total (avg)      
-----------------------------------------------------------------------+------------------
Bundler (1)                                                            | 6507ms           
ember-auto-import-analyzer (8)                                         | 1884ms (235 ms)  

Error proxying to <http://localhost:9001>
connect ECONNREFUSED 127.0.0.1:9001
g
Copy code
Build successful (25756ms) – Serving on <http://localhost:4200/>
i
I have no ports listening on 9001 or 4200
g
does 4200 show anything?
dang
i
localhost:4200 shows nothing either
g
do you have ./quickstart running?
hmm i wonder if the port is in use already somehow
i
no
lsof
reports no process on either port
This is clearly something wierd with my laptop. I have a colleague who sucessfully built datahub without having node, npm or yarn installed.
Thank you for help Gabe, I will try to debug this
g
ok, sounds good. good luck
i
šŸ‘ appreciate the help
b
@incalculable-ocean-74010 let us know if you want to schedule time to chat about this. you should not have to have node npm yarn
if this is not a one off we'll want to root cause it to avoid this phenomena in the future
i
I can talk right now if you want.
I think it is a one-off though
a colleague of mine was able to build the project with needing anything
I would suggest one thing right though, better error messages in the gradle process. I don't know if there is anything in the context of the repo to be done but gradle is not showing any useful information
whether I activate debug mode in the build process or not
b
Yeah so gradle wraps the yarn processes and effectively forks them off. Errors that occur in the underlying process may not be getting piped over
That's something we can look into
i
Out of curiosity, do any of you compile the project in a linux machine? Looking at the logs. I see that the package "fsevents@2.1.2: The platform "linux" is incompatible with this module." My colleague has a mac, this may be a very large coincidence but at this point I question everything
I've asked another 2 colleagues to compile the project (in linux machines, ubuntu to be exact). Both have the same issue.
b
@gray-shoe-75895 Compiles on Linux. When you run the main
gradlew build
you're only seeing issues in
datahub-web
ember module, is that correct?
i
Yes. I think I have found the issue on my side
I was compiling the project and skipping test tasks. One of them was emberWorkspaceTest
It appears that
emberWorkspaceTest
will populate some cache required for proceding tasks, namely
emberBuild
šŸ‘€ 1
I needed to compile once with emberWorkspaceTest enabled and then compilation works without a problem.
For some reason my machine also had an npm faulty installation, by removing it, I was able to run the whole pipeline šŸ™‚
I may be misinterpreting but shouldn't the emberBuild task depend on execEmber and not emberWorkspaceTest?
g
glad to see you got it working Pedro
b
It looks like we want to always run the tests as part of a full build. Guessing for easier CI/CD flows? Not exactly sure on the reasoning here