crandmck

Conformance

The C2PA Conformance Program provides assurance that products adhere to the Content Credentials specification, and fulfill a set of security requirements to ensure they are producing and validating C2PA data correctly.

The Conformance Program is a risk-based, transparent and unbiased governance process intended to hold generator products, validator products, and certification authorities accountable to the Content Credentials specification, the Certificate Policy, and the Security Requirements. Conforming products are placed on a publicly accessible list. This conveys confidence in the implementation and its security to the public and guarantees interoperability across products in the Content Credentials ecosystem.

The C2PA will provide additional technical guid

crandmck

(base) ~/c2pa-js $rush install

Rush version 5.90.2 is not currently installed. Installing...
Trying to acquire lock for rush-5.90.2
Deleting old files from /Users/randmckinney/.rush/node-v16.13.0/rush-5.90.2

Running "npm install" in /Users/randmckinney/.rush/node-v16.13.0/rush-5.90.2
Successfully installed Rush version 5.90.2 in /Users/randmckinney/.rush/node-v16.13.0/rush-5.90.2.

Rush Multi-Project Build Tool 5.90.2 - https://rushjs.io

crandmck

The Node Interactive conference in Portland kicked off yesterday with well-attended keynote talks from some prominent members of the Node community.

First off was James Snell from IBM, with a presentation titled "Convergence: Evolving Node.js with Open Governance and an Open Community." Snell is IBM's open technologies architect, and a member of the Node Core Technical Committee (CTC) and Technical Steering Committee (TSC). He observed that 2015 was an interesting year for Node, with the io.js fork generating some fear, doubt, and uncertainty.  Although there was a lot of excitement around Node, he said, there was a general belief that it could be better.

He noted that everyone was passionate about the technology, but there were profoundly different opinions about how project decisions were being made and the project was progressing. IBM, which started to embrace Node a few years ago, wanted to figure out how to help bring Node.js and io.js back together again to allow the project to continue to thrive, gro

crandmck

$ npm ls -g | grep strong-remoting
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/bl requires readable-stream@'~1.0.26' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.33-1
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream@'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/chalk requires strip-ansi@'^3.0.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_mod

crandmck

Since `loopback-explorer` was renamed to `loopback-component-explorer` (see https://github.com/strongloop/loopback-component-explorer/issues/123), we need to propagate this change to the example apps; specifically the same changes made in https://github.com/strongloop/loopback-example-app/pull/79:

**1.** In `package.json`, change 

` "loopback-explorer": "^2.0.0",` to  `"loopback-component-explorer": "^2.1.0",`

**2.** In `server/component-config.json`, change 
```
{
  "loopback-explorer": {

crandmck

$ npm cache clear
$ npm i -g strong-mesh-models --registry http://ci.strongloop.com:4873
/usr/local/bin/sl-meshctl -> /usr/local/lib/node_modules/strong-mesh-models/bin/sl-meshctl.js
/usr/local/bin/sl-meshadm -> /usr/local/lib/node_modules/strong-mesh-models/bin/sl-meshadm.js
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/bl requires readable-stream@'~1.0.26' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.33-1
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream@'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/readable-stre

crandmck

$ slc ctl -C http://45.55.19.126
/usr/local/lib/node_modules/strongloop/node_modules/loopback-datasource-juggler/lib/utils.js:381
        if (!target[key]) {
                   ^
TypeError: Cannot read property 'default' of null
    at /usr/local/lib/node_modules/strongloop/node_modules/loopback-datasource-juggler/lib/utils.js:381:20
    at Array.forEach (native)
    at mergeSettings (/usr/local/lib/node_modules/strongloop/node_modules/loopback-datasource-juggler/lib/utils.js:376:22)
    at Function.ModelClass.extend (/usr/local/lib/node_modules/strongloop/node_modules/loopback-datasource-juggler/lib/model-builder.js:384:26)
    at Registry.createModel (/usr/local/lib/node_modules/strongloop/node_modules/loopback/lib/registry.js:122:25)

crandmck

$ git commit -m "Clean up and fix API docs"
[master 4d96596] Clean up and fix API docs
 5 files changed, 108 insertions(+), 84 deletions(-)
Rands-MacBook-Air:strong-remoting rand$ git push
To https://github.com/strongloop/strong-remoting.git
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'https://github.com/strongloop/strong-remoting.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes

crandmck

express-example-app rand$ DEBUG=* slc start
  slc slc.run: +0ms argv [ 'start' ] options { _: [ 'start' ], '$0': 'slc' }
  slc loadCommand +3ms name start run? function usage? object
  strong-start:start app is "." +1s
  strong-start:pm start +2ms
  strong-start:pm alive? undefined +4ms
  strong-start:pm pm is alive +1ms
  strong-start:start deploy to "http://127.0.0.1:8701" app "." +0ms
  strong-mesh-models:client connecting to http://127.0.0.1:8701/api +1ms
  express:application compile etag weak +1ms

crandmck

Unexpected exit with 8 from Runner: commit default/local-directory in /Users/rand/StrongLoop/loopback-example-app
Start Runner: commit default/local-directory in /Users/rand/StrongLoop/loopback-example-app

/usr/local/lib/node_modules/strongloop/node_modules/strong-supervisor/bin/sl-run.js:19
  strongTracer: tracer(),
                ^
TypeError: undefined is not a function
    at Object.<anonymous> (/usr/local/lib/node_modules/strongloop/node_modules/strong-supervisor/bin/sl-run.js:19:17)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)