Our pure JavaScript Scheduler component


[REACT] Trial license bad for CI

Post Reply

Post by dyqode »

my username is dyqode@gmail.com
and I used trial password when generated token for CI. like this:
npm token create --registry=https://npm.bryntum.com

But when I use in .npmrc it gives me error:
lerna bootstrap
lerna notice cli v4.0.0
lerna info ci enabled
lerna info bootstrap root only
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error https://npm.bryntum.com/@bryntum%2fschedulerpro-trial-lib/-/schedulerpro-trial-lib-1.0.0.tgz: Integrity check failed for "@bryntum/schedulerpro-trial-lib" (computed integrity doesn't match our records, got "sha512-SyLdkFes5iHy2cA6Hb+E0w3aP1C3zqVTaW0B1QH0qlKdu8NRgaTMVasI+1i9qeH53h2KaTuV+hSxBx+jiWoMgQ== sha1-XdaABsTq2pWO2c4SqYGCgHkyg6Y=")
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Process stalled

I think this is some problem with token. What do I do?

Post by saki »

I have tried your credentials to create a new token and it worked. I'll send it to you in PM.

Post by dyqode »

Did you send? How do I get it?
I also was able to create token but when I copied it to .npmrc and used it on CI got error above.

Ok, I can checkout token that you were able to get may be it will be valid token. Can you send it to me?

Post by saki »

I have sent it in this forum's private messages: ucp.php?i=pm

Post by dyqode »

I tried your key and still got the same error

[2/4] Fetching packages...
error https://npm.bryntum.com/@bryntum%2fschedulerpro-trial-lib/-/schedulerpro-trial-lib-1.0.0.tgz: Integrity check failed for "@bryntum/schedulerpro-trial-lib" (computed integrity doesn't match our records, got "sha512-SyLdkFes5iHy2cA6Hb+E0w3aP1C3zqVTaW0B1QH0qlKdu8NRgaTMVasI+1i9qeH53h2KaTuV+hSxBx+jiWoMgQ== sha1-XdaABsTq2pWO2c4SqYGCgHkyg6Y=")
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Process stalled
Active handles:

  • Socket
  • Socket
  • Socket
  • TLSSocket
  • TLSSocket
  • TLSSocket
  • TLSSocket

What is "@bryntum/schedulerpro-trial-lib" ? Do I have to do anything in package.json?
Right now I got these as dependencies:

"dependencies": {
    "@bryntum/schedulerpro": "npm:@bryntum/schedulerpro-trial@^4.2.6",
    "@bryntum/schedulerpro-react": "^4.2.6",
  ...
}

Post by saki »

Strange, it worked for me. Have you tried to execute troubleshooting steps from here: https://bryntum.com/docs/scheduler-pro/guide/SchedulerPro/npm-repository#troubleshooting ?

Post by dyqode »

I applied log to CI build process and I see that it uses the exact key you provided and this ends up with error. Are you completely sure that this key you sent me correct?

On my local machine I am able to download these packages even without .npmrc setup:

"dependencies": {
    "@bryntum/schedulerpro": "npm:@bryntum/schedulerpro-trial@^4.3.2",
    "@bryntum/schedulerpro-react": "^4.3.2"
  }

Why?

Post by dyqode »

May be we need generate to key some other way? I see that key lengths of mine and yours are different, is that possible?

Post by saki »

Well, I more suspect that the .npmrc with the token is not taken into account by the CI. I'm pretty sure that the token is correct; see the attached screencast.

token.gif
token.gif (263.78 KiB) Viewed 1358 times

Post by dimehb »

I'm getting the same issue when I try to set up Vercel:

error https://npm.bryntum.com/@bryntum%2fscheduler-trial-lib/-/scheduler-trial-lib-1.0.0.tgz: Integrity check failed for "@bryntum/scheduler-trial-lib" (computed integrity doesn't match our records, got "sha512-CsvHHEMrCbYlBdGoqFyI2p18MPNfPvJ3KdtTBwa2bzchlMc+GQ4TzNooEIt9BAlKdI1gtqqITocWobbsUz3zRg== sha1-9JxveS23NdtcEHVNapAkpRsh0uk=")

I am using the following packages:

"@bryntum/scheduler": "npm:@bryntum/scheduler-trial@5.0.7",
"@bryntum/scheduler-react": "5.0.7"

And the following .npmrc file:

@bryntum:registry="https://npm.bryntum.com"
//npm.bryntum.com/:_authToken=MYTOKEN

When I ran Vercel's CLI command to set up the registry:
vc env add NPM_RC [environment] < ~/.npmrc

I got the error message as described above.

Any idea what could be going wrong here?

Post Reply