atomist / cli Goto Github PK
View Code? Open in Web Editor NEWThe Atomist CLI
License: Apache License 2.0
The Atomist CLI
License: Apache License 2.0
js-yaml:3.12.2
:
@atomist/automation-client>apollo>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-flow>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-scala>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-swift>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-typescript>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
[atomist:code-inspection:nortissej/spell-out-kubernetes=@atomist/atomist-sdm]
We need support for the following resource providers in the CLI:
the following actions should be supported:
index.ts:65
: (error) command is deprecated.index.ts:84
: (error) command is deprecated.index.ts:101
: (error) command is deprecated.index.ts:106
: (error) command is deprecated.[atomist:code-inspection:atomist-update-branch-master-1543218569607=tslint]
When installed with brew, it works. When (globally) installed with npm, it does not.
Running atomist create sdm
using the CLI fails with the error Cannot set property 'branch' of undefined
with either the empty or uhura SDM and using both user and org owners.
$ atomist create sdm
┌─────────────────────────────────────────────────────────────────────────────────────────┐
│ │
│ ## Create a new Software Delivery Machine (SDM) repository │
│ │
│ Choose blank for a new SDM to which you can add your own functionality. │
│ │
│ Choose uhura for a new SDM that provides self service software delivery │
│ for common project types. │
│ │
│ If you're new to Atomist, choose "uhura" to see Atomist's capabilities quickly. │
│ │
└─────────────────────────────────────────────────────────────────────────────────────────┘
? Type of SDM to create uhura
Please follow the prompts to create a new SDM
? name of the new repository uhura
? (mapped parameter) target-owner looking-for-freedom
# general 2019-04-15 09:22:10 Create Project
Cloning seed project from starting point atomist/uhura at https://github.com/atomist/uhura
# general 2019-04-15 09:22:11 Create Project
Project creation for looking-for-freedom/uhura failed:
Cannot set property 'branch' of undefined
Issue moved from atomist/sdm-local#101
Created by @johnsonr at 2018-08-10T23:06:35Z:
Comment by @ddgenome at 2018-08-10T23:14:57Z:
We will probably have to load the sdm-local commands when --help is run.
Comment by @johnsonr at 2018-08-10T23:50:29Z:
Yes, I think it's confusing otherwise. I will move this issue to cli
axios:0.18.0
:
@atomist/sdm-core>axios
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
marked:0.4.0
:
typedoc>marked
[atomist:code-inspection:nortissej/usage=@atomist/atomist-sdm]
axios:0.18.0
:
@atomist/sdm-core>axios
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
marked:0.4.0
:
typedoc>marked
[atomist:code-inspection:cli-support-for-resource-providers=@atomist/atomist-sdm]
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
handlebars:4.1.0
:
@atomist/sdm-local>express-handlebars>handlebars
typedoc>@types/handlebars>handlebars
typedoc>handlebars
js-yaml:3.12.2
:
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
js-yaml:3.12.2
:
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
marked:0.4.0
:
typedoc>marked
tar:2.2.1
:
@atomist/sdm-core>npm>libcipm>npm-lifecycle>node-gyp>tar
@atomist/sdm-core>npm>libnpm>npm-lifecycle>node-gyp>tar
@atomist/sdm-core>npm>node-gyp>tar
@atomist/sdm-core>npm>npm-lifecycle>node-gyp>tar
[atomist:code-inspection:goal-monitor=@atomist/atomist-sdm]
Add proxy config support to the CLI.
Remove ability to configure GitHub.com SCM provider from CLI and point people to the web app.
lodash:4.17.11
:
@atomist/automation-client>graphql-code-generator>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-server>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-server>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-code-generator>graphql-toolkit>lodash
[atomist:code-inspection:kube-install-104=@atomist/atomist-sdm]
Unless sdm-local
is present in the project, --local
flag should result in refusal to start and advise running enable local
When I type "atomist config" and I'm already configured, I would like it to report about the configuration.
and maybe tell me what to type if I want to change it.
currently it prints nothing.
index.ts:256
: (error) comment must start with a spaceindex.ts:257
: (error) comment must start with a spaceindex.ts:258
: (error) comment must start with a spacelib/deploy.ts:20
: (error) Importing this module is blacklisted. Try importing a submodule instead.lib/deploy.ts:112
: (warn) Use 'undefined' instead of 'null'lib/deploy.ts:32
: (error) Import sources within a group must be alphabetized.lib/deploy.ts:139
: (error) Missing semicolonlib/deploy.ts:137
: (error) Missing trailing comma[atomist:code-inspection:deploy-command=@atomist/atomist-sdm]
atomist login|connect --api-key <> --workspace-ids <>
should create the correct entries in the local config or if omitted log the user in, create an api key and provide access to the list of workspaces.
If there is only one choice, just inform user what is being used rather than giving them a selector with one option. This issue came up with the auth provider selection.
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
handlebars:4.1.0
:
@atomist/sdm-local>express-handlebars>handlebars
typedoc>@types/handlebars>handlebars
typedoc>handlebars
js-yaml:3.12.2
:
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
js-yaml:3.12.2
:
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
marked:0.4.0
:
typedoc>marked
tar:2.2.1
:
@atomist/sdm-core>npm>libcipm>npm-lifecycle>node-gyp>tar
@atomist/sdm-core>npm>libnpm>npm-lifecycle>node-gyp>tar
@atomist/sdm-core>npm>node-gyp>tar
@atomist/sdm-core>npm>npm-lifecycle>node-gyp>tar
[atomist:code-inspection:repository-start=@atomist/atomist-sdm]
That hidden input was a problem, because we could not tell whether we had pasted it in, and the result we got was like ten copies of the APIKey concatenated. Either don't hide it or make it show dots or somethign
The postInstall script calls lib/postInstall.js
which does not exist after an install, only the .ts does.
It would be very useful to have a command to update the @atomist dependencies to the latest known working version.
Similar to what the Spring Boot BOM offers.
cdupuis@imac-pro:~ $ npm install -g @atomist/cli
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: Use uuid module instead
/usr/local/bin/atomist -> /usr/local/lib/node_modules/@atomist/cli/index.js
/usr/local/bin/@atomist -> /usr/local/lib/node_modules/@atomist/cli/index.js
/usr/local/bin/atomist-githook -> /usr/local/lib/node_modules/@atomist/cli/githook.js
+ @atomist/[email protected]
updated 1 package in 34.771s
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
handlebars:4.1.0
:
typedoc>@types/handlebars>handlebars
typedoc>handlebars
js-yaml:3.12.2
:
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
js-yaml:3.12.2
:
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
marked:0.4.0
:
typedoc>marked
[atomist:code-inspection:bom=@atomist/atomist-sdm]
Commands are not working on MS Windows since the switch from child_process.exec
to child_process.spawn
.
exec
spawns a shell which properly deals with both .exe
, .bat
, and .cmd
files on MS Windows. spawn
properly handles .exe
but not .bat
and .cmd
. See https://nodejs.org/api/child_process.html#child_process_spawning_bat_and_cmd_files_on_windows for the current status and nodejs/node-v0.x-archive#2318 for more context.
Reference: https://nodejs.org/api/child_process.html
The kube-*crypt command brought in sdm-pack-k8s as a dependency. Use it rather than kubectl to execute the kube install commands.
lib/config.ts:31
: (error) Importing this module is blacklisted. Try importing a submodule instead.lib/provider/github.ts:24
: (error) Importing this module is blacklisted. Try importing a submodule instead.[atomist:code-inspection:new-provider-flow=tslint]
If you run an SDM in local mode multiple times, you'll get errors that port 2866 is already in use
fstream:1.0.11
:
@atomist/sdm-core>npm>libcipm>npm-lifecycle>node-gyp>fstream
@atomist/sdm-core>npm>libcipm>npm-lifecycle>node-gyp>tar>fstream
@atomist/sdm-core>npm>libnpm>npm-lifecycle>node-gyp>fstream
@atomist/sdm-core>npm>libnpm>npm-lifecycle>node-gyp>tar>fstream
@atomist/sdm-core>npm>node-gyp>fstream
@atomist/sdm-core>npm>node-gyp>tar>fstream
@atomist/sdm-core>npm>npm-lifecycle>node-gyp>fstream
@atomist/sdm-core>npm>npm-lifecycle>node-gyp>tar>fstream
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
handlebars:4.1.0
:
@atomist/sdm-local>express-handlebars>handlebars
typedoc>@types/handlebars>handlebars
typedoc>handlebars
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
marked:0.4.0
:
typedoc>marked
tar:2.2.1
:
@atomist/sdm-core>npm>libcipm>npm-lifecycle>node-gyp>tar
@atomist/sdm-core>npm>libnpm>npm-lifecycle>node-gyp>tar
@atomist/sdm-core>npm>node-gyp>tar
@atomist/sdm-core>npm>npm-lifecycle>node-gyp>tar
[atomist:code-inspection:deploy-command=@atomist/atomist-sdm]
lodash:4.17.11
:
@atomist/automation-client>graphql-code-generator>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-code-generator>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-server>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-server>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
marked:0.4.0
:
typedoc>marked
[atomist:code-inspection:kube-fetch=@atomist/atomist-sdm]
js-yaml:3.12.2
:
@atomist/automation-client>apollo>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-flow>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-scala>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-swift>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-typescript>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
[atomist:code-inspection:nortissej/config-ps=@atomist/atomist-sdm]
tree-kill:1.2.1
:
@atomist/automation-client>tree-kill
[atomist:code-inspection:master=@atomist/atomist-sdm]
lib/job/monitor.ts:116
: (warn) Calls to 'console.log' are not allowed.lib/job/monitor.ts:65
: (warn) Use 'undefined' instead of 'null'lib/remoteStart.ts:25
: (error) Import sources within a group must be alphabetized.lib/job/monitor.ts:94
: (error) expected call-signature: 'podWatch' to have a typedefindex.ts:301
: (error) missing whitespace[atomist:code-inspection:goal-monitor=@atomist/atomist-sdm]
This happens whenever I run atomist feed
lodash:4.17.11
:
@atomist/automation-client>graphql-code-generator>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-server>graphql-codegen-typescript-common>graphql-codegen-plugin-helpers>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-client>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-codegen-typescript-server>graphql-codegen-typescript-common>graphql-codegen-core>graphql-toolkit>lodash
@atomist/automation-client>graphql-code-generator>graphql-toolkit>lodash
[atomist:code-inspection:kube-encrypt-100=@atomist/atomist-sdm]
Add the ability to encrypt and decrypt Kubernetes secrets and values using our standard encryption/decryption algorithm. The commands should be able to operate on a string or a secret spec.
A user reports that on windows 7 server amd 64 bit desktop, the installation of the CLI fails. Here are the relevant parts of the log:
65181 verbose lifecycle @atomist/[email protected]~postinstall: CWD: C:\Users\XXXX\AppData\Roaming\npm\node_modules\@atomist\cli
65182 silly lifecycle @atomist/[email protected]~postinstall: Args: [ '/d /s /c', 'node bin/postInstall.js' ]
65183 silly lifecycle @atomist/[email protected]~postinstall: Returned: code: 1 signal: null
65184 info lifecycle @atomist/[email protected]~postinstall: Failed to exec postinstall script
65185 verbose unlock done using C:\Users\XXXX\AppData\Roaming\npm-cache\_locks\staging-e32421e33087ce3b.lock for C:\Users\XXXX\AppData\Roaming\npm\node_modules\.staging
65186 silly rollbackFailedOptional Starting
65187 silly rollbackFailedOptional Finishing
65188 silly runTopLevelLifecycles Finishing
65189 silly install printInstalled
65190 verbose stack Error: @atomist/[email protected] postinstall: `node bin/postInstall.js`
65190 verbose stack Exit status 1
65190 verbose stack at EventEmitter.<anonymous> (G:\Tools\node-6.9.4\node_modules\npm\lib\utils\lifecycle.js:255:16)
65190 verbose stack at emitTwo (events.js:106:13)
65190 verbose stack at EventEmitter.emit (events.js:191:7)
65190 verbose stack at ChildProcess.<anonymous> (G:\Tools\node-6.9.4\node_modules\npm\lib\utils\spawn.js:40:14)
65190 verbose stack at emitTwo (events.js:106:13)
65190 verbose stack at ChildProcess.emit (events.js:191:7)
65190 verbose stack at maybeClose (internal/child_process.js:877:16)
65190 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
65191 verbose pkgid @atomist/[email protected]
65192 verbose cwd C:\Windows\system32
65193 error Windows_NT 6.1.7601
65194 error argv "G:\\Tools\\node-6.9.4\\node.exe" "G:\\Tools\\node-6.9.4\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "@atomist/cli@next"
65195 error node v6.9.4
65196 error npm v3.10.10
65197 error code ELIFECYCLE
65198 error @atomist/[email protected] postinstall: `node bin/postInstall.js`
65198 error Exit status 1
65199 error Failed at the @atomist/[email protected] postinstall script 'node bin/postInstall.js'.
65199 error Make sure you have the latest version of node.js and npm installed.
65199 error If you do, this is most likely a problem with the @atomist/cli package,
65199 error not with npm itself.
65199 error Tell the author that this fails on your system:
65199 error node bin/postInstall.js
65199 error You can get information on how to open an issue for this project with:
65199 error npm bugs @atomist/cli
65199 error Or if that isn't available, you can get their info via:
65199 error npm owner ls @atomist/cli
65199 error There is likely additional logging output above.
65200 verbose exit [ 1, true ]
While the postInstall script exited with a status of 1, there is no indication of why.
In 'atomist start' we run 'npm install' if it thinks it's needed.
We should do 'npm ci' eh? ... we don't want mysterious package upgrades to happen.
@ddgenome what do you think?
axios:0.18.0
:
@atomist/sdm-core>axios
graphql-code-generator:0.16.1
:
@atomist/automation-client>graphql-code-generator
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
marked:0.4.0
:
typedoc>marked
[atomist:code-inspection:add-update-command=@atomist/atomist-sdm]
lib/kube.ts:212
: (error) Promises must be handled appropriatelylib/kube.ts:213
: (error) Promises must be handled appropriatelylib/kube.ts:220
: (error) Promises must be handled appropriatelylib/kube.ts:221
: (error) Promises must be handled appropriatelytest/gql.test.ts:40
: (error) Promises must be handled appropriately[atomist:code-inspection:master=@atomist/atomist-sdm]
js-yaml:3.12.2
:
@atomist/automation-client>apollo>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-flow>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-scala>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-swift>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-codegen-typescript>apollo-codegen-core>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>apollo>apollo-language-server>cosmiconfig>js-yaml
@atomist/automation-client>graphql-code-generator>graphql-config>js-yaml
@atomist/sdm-core>@kubernetes/client-node>js-yaml
tslint>js-yaml
js-yaml:3.12.1
:
@atomist/automation-client>graphql-code-generator>js-yaml
js-yaml:3.12.0
:
mocha>js-yaml
[atomist:code-inspection:provider-repo-config=@atomist/atomist-sdm]
[master] first-uhura-sdm $ atomist config
atomist: [ERROR] Failed to validate API key: Network error: Response not successful: Received status code 401
I knew it was invalid, I revoked it. I was hoping this would prompt me again, and like create another one for me.
(I know, I know, I'll delete the config and start over, but still, it would be nice)
This feature would let me not have to hunt down the existing one. It would also let me run both a goal feed and a regular feed on a mac.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.