Issues with the installation

[Jairo Anaya]

Hello, I have this issue with the installation

[ec2-...@ip-12.34.56.78 carbo1]$ yarn start
Internal Error: root-template@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile
    at AF.getCandidates (/home/ec2-user/carbo1/.yarn/releases/yarn-3.1.1.cjs:437:4421)
    at pd.getCandidates (/home/ec2-user/carbo1/.yarn/releases/yarn-3.1.1.cjs:432:5275)
    at /home/ec2-user/carbo1/.yarn/releases/yarn-3.1.1.cjs:441:7674
    at du (/home/ec2-user/carbo1/.yarn/releases/yarn-3.1.1.cjs:382:4003)
    at R (/home/ec2-user/carbo1/.yarn/releases/yarn-3.1.1.cjs:441:7654)
[ec2-...@ip-12.34.56.78 carbo1]$ 

I previously ran the command yarn install

Thanks for your support

[Cloud Carbon Footprint]

HI there,

Thanks for reaching out.

Would you be able to provide any more details on how to reproduce this issue?

Best,

The Cloud Carbon Footprint Team at Thoughtworks

[Jairo Anaya]

Hello, here is the information

1. I am try to install Cloud Carbon Footprint App in a EC2 instance from AWS with lunux

2. I put in the instance the Prerequisites that app needs

3. But when I run the command yarn guided-install I received the following message

[ec2-user@ip-172-31-36-68 carbon-footprint]$ yarn guided-install

Internal Error: root-template@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile

    at AF.getCandidates (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:437:4421)

    at pd.getCandidates (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:432:5275)
    at /home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:441:7674
    at du (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:382:4003)
    at R (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:441:7654)

ec2-user@ip-172-31-36-68 carbon-footprint]$ yarn install
➤ YN0000: ┌ Resolution step
➤ YN0061: │ @types/mockdate@npm:3.0.0 is deprecated: This is a stub types definition. mockdate provides its own type definitions, so you do not need this installed.
➤ YN0061: │ @types/history@npm:5.0.0 is deprecated: This is a stub types definition. history provides its own type definitions, so you do not need this installed.
➤ YN0061: │ @azure/arm-consumption@npm:8.0.1 is deprecated: Please note, versions of this package with version numbers 8.0.1 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 9.0.0 or above to continue receiving updates. Refer to our deprecation policy: https://azure.github.io/azure-sdk/policies_support.html for more details.
➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ read-package-tree@npm:5.3.1 is deprecated: The functionality that this package provided is now in @npmcli/arborist
➤ YN0061: │ uuid@npm:3.4.0 is deprecated: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
➤ YN0061: │ svgo@npm:1.3.2 is deprecated: This SVGO version is no longer supported. Upgrade to v2.x.x.
➤ YN0061: │ querystring@npm:0.2.0 is deprecated: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
➤ YN0061: │ stable@npm:0.1.8 is deprecated: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
➤ YN0061: │ request@npm:2.88.2 is deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
➤ YN0061: │ har-validator@npm:5.1.5 is deprecated: this library is no longer supported
[ec2-user@ip-172-31-36-68 carbon-footprint]$

4.- I cannot pass of this step, I always receive the same error  

Internal Error: root-template@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile

and I cannot run the command yarn start

ec2-user@ip-172-31-36-68 carbon-footprint]$ yarn start

Internal Error: root-template@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile

    at AF.getCandidates (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:437:4421)
    at pd.getCandidates (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:432:5275)
    at /home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:441:7674
    at du (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:382:4003)
    at R (/home/ec2-user/carbon-footprint/.yarn/releases/yarn-3.1.1.cjs:441:7654)
[ec2-user@ip-172-31-36-68 carbon-footprint]$ 

Thanks for your help I will wait for your comments

Regards

[Jairo Anaya]

Can you help me with your comments please

Regards

On Thursday, September 8, 2022 at 12:05:36 PM UTC-5 Cloud Carbon Footprint wrote:

Locations in Germany, Portugal, Spain and Vietnam · Legal · Zoi TechCon GmbH and associated entities · This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. 

Zoi TechCon GmbH, Quellenstraße 7, 70376 Stuttgart. Geschäftsführer: Benjamin Hermann, Dr. Daniel Heubach. Amtsgericht Stuttgart HRB 759619, Gerichtsstand Stuttgart. Die genannten Angaben werden automatisch hinzugefügt und lassen keine Rückschlüsse auf den Rechtscharakter der E-Mail zu. 

[Cloud Carbon Footprint]

Thanks for sharing the detailed steps. We're not exactly sure what the issue is, so we will have to try to replicate by running it in EC2 ourselves.

One thing to try if you haven't already might be to delete the existing lockfile and then run yarn install again.

Cheers,
The Cloud Carbon Footprint team at Thoughtworks

[Cloud Carbon Footprint]

Hi Jairo,

 We did run the guided install on a EC2 micro instance without the lock file problem. This is what we did:

1. Installed the node pre-requisites as described in: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html

2. git clone --depth 1 --branch release-2022-08-02 https://github.com/cloud-carbon-footprint/cloud-carbon-footprint.git

3. cd cloud-carbon-footprint; npm install yarn

4. npx yarn install

5. npx yarn guided-install

From there the application starts to prompt for information for its setup. Please let us know if this works for you.

Cheers,

The Cloud Carbon Footprint team at Thoughtworks

[Noel Crowley]

I just ran the command => cd cloud-carbon-footprint; npm install yarn and got the messages below. Any help approciated.

npm ERR! code ERESOLVE

npm ERR! ERESOLVE unable to resolve dependency tree

npm ERR! 

npm ERR! While resolving: @cloud-carbon-footprint/cli...@3.2.0

npm ERR! Found: re...@17.0.2

npm ERR! node_modules/react

npm ERR!   react@"^17.0.2" from @cloud-carbon-footprint/cli...@3.2.0

npm ERR!   packages/client

npm ERR!     @cloud-carbon-footprint/cli...@3.2.0

npm ERR!     node_modules/@cloud-carbon-footprint/client

npm ERR!       workspace packages/client from the root project

npm ERR! 

npm ERR! Could not resolve dependency:

npm ERR! peer react@"^0.14 || ^15.5.4 || ^16.1.1" from react...@21.8.0

npm ERR! node_modules/react-dates

npm ERR!   react-dates@"^21.8.0" from @cloud-carbon-footprint/cli...@3.2.0

npm ERR!   packages/client

npm ERR!     @cloud-carbon-footprint/cli...@3.2.0

npm ERR!     node_modules/@cloud-carbon-footprint/client

npm ERR!       workspace packages/client from the root project

npm ERR! 

npm ERR! Fix the upstream dependency conflict, or retry

npm ERR! this command with --force, or --legacy-peer-deps

npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

npm ERR! 

npm ERR! See /home/ec2-user/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:

npm ERR!     /home/ec2-user/.npm/_logs/2022-10-21T16_26_41_843Z-debug-0.log