Skip to content
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

[HOTFIX] Fix bad npm registry #294

Merged
merged 3 commits into from
Aug 18, 2022
Merged

[HOTFIX] Fix bad npm registry #294

merged 3 commits into from
Aug 18, 2022

Conversation

dyst5422
Copy link
Contributor

@dyst5422 dyst5422 commented Aug 18, 2022

  • Tickets addressed: HOTFIX
  • Review: By commit
  • Merge strategy: Merge (no squash)

Description

When I updated the user code runner, my npm registry was set to JPL artifactory, so that got encoded into the package-lock files. This fixes that blunder.

Also locks version for typescript-json-schema to work around a dependency error with the 0.53.1 version

Verification

Documentation

Future work

Copy link
Contributor

@goetzrrGit goetzrrGit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These files were deleted but don't we want to create new lock files?

@dyst5422
Copy link
Contributor Author

dyst5422 commented Aug 18, 2022

These files were deleted but don't we want to create new lock files?

🤦 amended the commit - ugh why is this such a PITA, gimme a sec - THERE WE GO

@dyst5422 dyst5422 force-pushed the hotfix/bad-npm-source branch from 84c59c2 to daf10f4 Compare August 18, 2022 18:04
@dyst5422 dyst5422 temporarily deployed to e2e-test August 18, 2022 18:04 Inactive
Copy link
Contributor

@goetzrrGit goetzrrGit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks better :D One more question what about the command-expansion-server lock file? Was that one not messed up?

There was an issue in 0.53.1 and 0.54.0, so we'll lock it here for now
@dyst5422 dyst5422 temporarily deployed to e2e-test August 18, 2022 18:33 Inactive
@dyst5422
Copy link
Contributor Author

This has turned into a dependency nightmare. I think I've got it right this time.

@dyst5422
Copy link
Contributor Author

dyst5422 commented Aug 18, 2022

That looks better :D One more question what about the command-expansion-server lock file? Was that one not messed up?

Great question. I have no idea. It's clearly right here https://github.com/NASA-AMMOS/aerie/blob/hotfix/bad-npm-source/command-expansion-server/package-lock.json#L1046

Perhaps I had already installed the 0.3.1 locally on a different day when my registry was correctly set and so the package-lock didn't change.

@dyst5422
Copy link
Contributor Author

@goetzrrGit finally got it

@dyst5422 dyst5422 requested a review from goetzrrGit August 18, 2022 18:44
Copy link
Contributor

@skovati skovati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥵

Copy link
Contributor

@goetzrrGit goetzrrGit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge, Merge, Merge

@dyst5422 dyst5422 merged commit 6fe776e into develop Aug 18, 2022
@dyst5422 dyst5422 deleted the hotfix/bad-npm-source branch August 18, 2022 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants