-
Notifications
You must be signed in to change notification settings - Fork 9
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
Introduce running of protocol substrate node and dkg node via the test-utils package #278
Conversation
…ami/consolidate-test-util � Conflicts: � package.json
} from './substrateNodeBase.js'; | ||
|
||
const STANDALONE_DOCKER_IMAGE_URL = | ||
'ghcr.io/webb-tools/protocol-substrate-standalone-node:edge'; |
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.
Can we use stable version here?
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.
The stable version is not with consistent with master.
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.
Thanks for checking @dharjeezy, @dutterbutter please make sure we keep things up to date. I'm not sure what stable
is but possibly worth removing. Would rather we consider something called production
instead of stable
.
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.
stable
is a deployed docker image on protocol-substrate. It's purpose is to prevent all of our CIs from breaking when a breaking change is made on protocol-substrate. Changing the name is trivial - but would welcome suggestions on better methods for releasing software incrementally across our repos.
image: string; | ||
}): void { | ||
if (!this.checkIfImageExists(opts.image) || opts.frocePull) { | ||
execSync(`docker pull ${opts.image}`, { |
Check warning
Code scanning / CodeQL
Unsafe shell command constructed from library input
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.
LG so far, need more comments and would appreciate formatting more things.
"main": "./cjs/index.js", | ||
"module": "./index.js", | ||
"types": "./index.d.ts", | ||
"main": "./build/cjs/index.js", |
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.
CC @nepoche to check these since he would know best if this is how we should point to the files. Have a feeling we shouldn't have this. Any reason why its added @dharjeezy ?
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.
Yh, so i was having issue trying to use the package in the integration tests. So, i had to point to the files like that just as it is being done here https://github.com/webb-tools/webb.js/blob/master/packages/sdk-core/package.json
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.
This is consistent with the way we are building packages for the monorepo, esm, and cjs.
"main": "./cjs/index.js", | ||
"module": "./index.js", | ||
"types": "./index.d.ts", | ||
"main": "./build/cjs/index.js", |
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.
This is consistent with the way we are building packages for the monorepo, esm, and cjs.
} from './substrateNodeBase.js'; | ||
|
||
const STANDALONE_DOCKER_IMAGE_URL = | ||
'ghcr.io/webb-tools/protocol-substrate-standalone-node:edge'; |
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.
stable
is a deployed docker image on protocol-substrate. It's purpose is to prevent all of our CIs from breaking when a breaking change is made on protocol-substrate. Changing the name is trivial - but would welcome suggestions on better methods for releasing software incrementally across our repos.
Co-authored-by: nepoche <[email protected]>
Co-authored-by: nepoche <[email protected]>
Co-authored-by: nepoche <[email protected]>
… dami/consolidate-test-util # Conflicts: # packages/test-utils/src/substrate/substrateNodeBase.ts
…ami/consolidate-test-util
@dharjeezy please resolve conflicts |
…ami/consolidate-test-util � Conflicts: � packages/test-utils/package.json
PR Description
This PR solves part of the issue in #270 so as to start up different node types such as