Discussion about next Bookshelf version

I figured that now that I have enough code and ideas that I'm starting to get somewhere with the next iteration of Bookshelf I should open a ticket to discuss some ideas I have and see if anyone has thoughts / feedback / ideas / unaddressed pain points as I continue to work on it in the coming weeks.
Rationale / Background:
Bookshelf was originally ported heavily from Backbone, to bring some of the ideas of the Model & Collection structure to the server via an ORM. While it's been nice, a lot of the underlying concepts of Backbone are either unnecessary or antithetical to the core of what an good ORM should include. Also, sharing code on the client and server between Bookshelf and Backbone isn't really going to happen to any major degree (beyond ad-hoc handmade integrations). Further, a lot of the code to keep consistent with Backbone has also turned the source into a damn disaster.
So now that I've had a chance to step back and evaluate / learn a bit from other ORMs, languages, libraries, etc I feel it's time to refine a decent bit of the core of Bookshelf to really make for the best possible experience out of the box, while providing for a lot of the issues that have come up which we haven't been able to address and simultaneously cutting the codebase in at least half, hopefully more.
Active Record vs Data Mapper
Bookshelf currently, unfortunately, follows an Active Record Pattern. Put simply, it means the backing classes know about the underlying connection. This is a design flaw making things harder to test and ultimately to use in an application. Currently, the initialized bookshelf instance needs to be either created as a singleton cached require module or injected into every file creating a model. #90
This isn't sustainable:
var bookshelf = require('/path/to/bookshelf-init.js');

var User = bookshelf.Model.extend({
  tableName: 'users'
})

rather than just being able to do:
var Bookshelf = require('bookshelf');

var User = Bookshelf.Model.extend({
  tableName: 'users'
});

or with ES6:
var Bookshelf = require('bookshelf');

class User extends Bookshelf.Model {
   getTableName() {
     return 'users';
   }
}

(ESNext spec doesn't provide for prop definitions on the class body, still thinking about different syntax ideas for some of these things).
Models would then be constructed by the initialized bookshelf instance, via (long form):
var bookshelf = require('bookshelf')(knex);
var User = require('./models/user')

bookshelf.createModel(User).where({id: 1}).fetch().then(...

or alternatively:
bookshelf('user').where({id: 1}).fetch().then(...

bookshelf('user', {name: 'Tim'}).save().then(...

The second form would act similar to how the registry plugin does now, allowing one to register specific models on the bookshelf instance, or look them up on a require path (default process.cwd() + '/models')... or just create a new model constructor which assumes that table exists, you just don't want to do any configuration on it (similar to how knex assumes the table exists). If a schema follows the conventions laid out by the library, there's a good possibility you won't need to define any model files.
Collections
Collections should not be as first class as they are in Bookshelf, (I would argue they shouldn't be as much in Backbone, but I guess with a limited scope of simple REST API calls it doesn't matter as much to most).
I'm thinking in Bookshelf, the collection will be stripped down measurably, turning into a very simple ResultSet object. This will have no purpose other than to iterate the results of a query, and possibly to load extra data onto the result models (though I'm thinking even that might be better placed elsewhere).
It won't be possible to add directly to a ResultSet anymore, you'll only be able to iterate. If you want to add to it, you'll need to cast as an array and work with it there. Further, you can't lookup based on PK, since ResultSets won't be indexed map-like as they are in Backbone (though it'll be possible to do this on the backing session described below).
So, in summary, the heavy collection is pretty much going to go away as is, though it'll be possible to define the target ResultSet class if you really need to define something special for handling your results.
Looking here for any cases where people are using features from the current Collection api which seem like they might go away and you won't be able to live without them, to see how we can work on that.
Attributes
There does need to be some way of doing prop type validation / casting that can be optionally defined on the model, but ideally we'll be able to gather this meta information on the model and apply/cache it prior to the first async action. This way we'll have the nice getter/setters on the attributes. It'll also be possible for anyone to create their own type definitions and transforms.
Relations
Relations should be both more configurable and more generic than they are now, currently the lack of ability to define every possible permutation of joins is a weakness, as is the lack of support for such items as foreign keys. Relation methods should take two arguments, the Target class and options, where flags can be defined constraining the relation (we can figure out what these mean later).
The related method on a model is also a bit ambiguous, since you can only have a single instance of a related model e.g. user.related('accounts'), but you can construct multiple related models via creating new instances with user.accounts().
So I'm thinking there'll be two ways of defining relations, dynamically and statically. The only difference with statically defined relations is they be made available with defineProperty getters on the model, and they will always return the same fetched instance.
I'm also thinking that on relations, you should be able to do something like:
withRelated: {
   users: {
     where: {active: true},
     withRelated: {
        posts: {
           where: {moderated: true},
           withRelated: {
             comments: {limit: 5}
           }
        },
        comments: true
     }
   }
}

as a more declarative version of:
withRelated: [{'users': function(qb) {
  qb.where('active', true)
}}, {'users.posts': function(qb) {
  qb.where('moderated', true)
}}, 'users.comments',
{'users.posts.comments': function(qb) {
  qb.limit(5);
}}]

This would address issues like #516
I have some other ideas about being able to do joins on models so you don't need to do multiple queries to load some relations, especially now that we should know the table schemas prior to querying.
Session
The concept of having a backing "Session" would be helpful in mitigating the "object relational impendence problem" a bit. Here we can keep track of the rows which are fetched and ensure each model has a === backing "row". This should not be mistaken for a cache, though we could likely fast-path some very simple queries which have been already fully fetched and only lookup based on primary keys. Any visibility modifications defined on a specific model would happen at the model layer (so if two models share the same table/backing row but you're not permitted to set or retrieve a model item on one, that'd be the model's job to handle during the get / set / iterate).
Because all the data is fetched to a single location, it should be significantly easier to format everything into something like "JSON API" or Transit or whatever you want.
The session will also be able to log every query applied over a certain amount of time, which would be awesome if it's tied to the request/response cycle, all of the queries that go into a particular request/response can be easily dumped or displayed in a dashboard or something like that. If anyone has any interest in building a nice UI for that once this gets a little further along let me know, I think it could be a really great debug feature.
Transactions
Transactions are certainly more cumbersome than they are in knex, particularly since the 0.6 release of knex. They're also a bit dangerous, since in order for them to work reliably, you need to explicitly pass the transacting option to every query you want on the transaction. I think Bookshelf should follow a similar model as knex, where the transaction is bound to the instance:
bookshelf.transaction(function(bookshelf) {
   return bookshelf('users').fetchAll().then(function(users) {
     return users.accounts().fetch();
   }).then(function(accounts) {
     return P.all(accounts.map(function(account) {
       return account.destroy();
     }))
   })
}).then(function() {
  // transaction success
}).catch(errHandler)

Object Lifecycles
When a model is persisted, it should be immediately fetched afterwards by default. In postgres this can be done easily in one hit with returning * on pretty much every query. This could be optionally skipped, but in most cases I'm thinking keeping everything in a consistent state will be worth it (and if you don't need that, use knex).
Bulk inserts / deletes / updates:
These should be made possible by setting a flag to queue for deletion / save, etc.
users.forEach(function(user) {
  if (user.status === 'inactive') users.markDestroyed();
})
users.getSession().sync().then(function() {
  // delete from users where id in (....)
})

This should help us cut-down on queries in these situations. Not sure what the best interface would be here, users.destroy({queue: true}), users.destroy({defer: true}), users.queueDestroy()
Soft Deletes
These should be available by default. No more hacking around to make this work, it'll just be a thing. One question would be how to deal with the case where you sometimes want to work with deleted items. I'm imagining a withDeleted function would be used to indicate you want to fetch / iterate the soft-deleted models.
model.withDeleted(function(model) {
   return model.fetchAll();
}).then(function(models) {
  // all models, even the deleted ones, though to see them
  // in the iterator, you'll need to be within a withDeleted block
})

Dialect specific adapters
So one thing I mentioned was the fact that we should be able to do things like returning *, this would require that we have different backing adapters. With this we should be able to start adding some of the nice new features of PG which have been released recently (and sort of prompted writing this post).
This may also eventually open up the potential for integrating with additional databases (though definitely not an immediate concern, it would be pretty cool), at the very least I'm thinking it'll be possible to relate with different relational db's - which would actually be really cool for instances of applications with sharded DB's.
Other Thoughts:
Camel Case
parse and transform and such are pretty weak, and they're mostly used for camel casing attrs, so we'll just add this as an option, keeping the model as the transform layer for the keys so we don't need to go to and from all the time when coming from the db. Then we'll advertise the parse and transform
Events
I'm wondering whether events are still the best way to deal with lifecycle actions. I haven't decided that they're going to be kicked entirely but I feel like having lifecycle methods defined on models would be much cleaner, less ad-hoc and easier to reason about. It'd also be simple to just hook the events into the lifecycle events at the top-level if need be.
Summary
I'll add other thoughts as they come up, just wanted to see what anyone thoughts and if there were any major concerns with some of the ideas expressed here. Obviously in order to do something like this, there will be some breaking changes but I think the tradeoff between potential performance, features, and general code quality will heavily lean in favor of a little breakage, particularly if there's a very clear upgrade path. I've also got a sample application in mind to show off some of these features.
Looking forward to addressing a lot of the flaws that have come up and getting back on track to making Bookshelf the de-facto JS ORM in 2015.
/cc @tkellen

Good to see you sharing the concerns I've had with Bookshelf (besides everything amazing it does)
We use a single tenant database model, meaning I have to initialize my models for every client. It works but it's far from ideal..
Moving away from Backbone would be great for performance. In some tests I ran, fetching a thousand models would easily spend close to 200ms in the set() method from lib/base/model, multiplied by the number of relations.
I changed the way attributes were assigned and got a 15x performance increase for the hydration:
for (var attr in attrs) {
  val = attrs[attr];
  if (!_.isEqual(prev[attr], val)) {
    this.changed[attr] = val;
    if (!_.isEqual(current[attr], val)) hasChanged = true;
  } else {
    delete this.changed[attr];
  }
  unset ? delete current[attr] : current[attr] = val;
}

becomes
if (Object.keys(current).length === 0) {
    current = attrs;
  }else{
    // For each `set` attribute, update or delete the current value.
    for (var attr in attrs) {
      unset ? delete current[attr] : current[attr] = val;
    }
  }
}

Keeping track of changes could be a parameter, or you could just initialize what's required on the first actual change, not the initial fetch. Big collections in read only would benefit a lot.

Cant wait for ES6 features to hit bookshelf. With the coming of IO.js hopefully developers start adopting more ES6 features for their libraries. Wondering if bookshelf would look at adopting a more verbose ORM's like doctrine e.g..

class User  extends Bookshelf.Model{
  constructor() {
    this.attributes = {}
  }

  get email () {
    return this.attributes.email;
  }

  set email (val) {
    this.attributes.email = val;
  }
}

User = bookshelf.makeModel(User);

var user = new User();
user.email =<EMAIL_ADDRESS>user.save();

Well in some aspects, yes it will be similar to Doctrine fundamentally internally but without some of the verbosity and overcomplications. The idea is that the getters & setters would ideally be determined based on introspecting the schema at first access with the option to disable or override as opposed to defining them yourself on the model.
So yeah I don't think it'll go quite far as Doctrine with what they require you to define, they go a bit too far in the other direction IMO, but fundamentally it will share philosophies from the Data Mapper approach (not having the User model know as much about the underlying connection details), with syntactic sugar for making it "feel" like more of an active-record.
bookshelf('user').set({email<EMAIL_ADDRESS>
rather than
var user = bookshelf.createModel(User)
user.set({email<EMAIL_ADDRESS>

This makes me pretty excited for Bookshelf!
Is there a timeline for when work on this might get started?

Oh it's well underway, just nothing public yet. Look forward to some developments in the next month or so...

Awesome! Really looking forward to it.

The new transaction api wouldnt let me to share a transaction object between expressjs/restify middlewares, would it?

Well you can do that know by grabbing the transaction object inside the closure and assigning it to something in a higher scope. You lose the ability to auto-commit the transaction but it'll work fine.

Hi, just a thought upon reading the new Transaction model (which works beautifully in knex).
If I understand correctly this replaces one gotcha with another. Currently the gotcha is that you could omit the { transacting: t } option. The new gotcha might be that you'd want to use a model fetched outside of the bookshelf.transaction function scope, or take results out into another scope and then do further queries on them (resulting in an error because the transaction had already concluded). Both seem to be likely use cases.
For example (trying to use a pre-fetched model):
bookshelf.transaction(function(bookshelf) {
   // users is collection of models that already exists in outer scope.
   return users.accounts().fetch().then(function(accounts) {
     return P.all(accounts.map(function(account) {
       return account.destroy();
     }))
   })
  // Oops, that wasn't actually a transaction.
}).then( //...

I had an idea for an alternate API, but upon thinking about it more it might not be that different to the current pattern. Here it is anyway:
bookshelf.transaction(function(trx) {
   // users is collection of models that already exists in outer scope.
   // wrap it with `trx` function to (without mutating it) perform queries in a transation.
   return trx(users).accounts().fetch().then(function(accounts) {
     return P.all(trx(accounts).map(function(account) {
       return trx(account).destroy();
     }))
   })
}).then(function() {
  // transaction success
}).catch(errHandler)

Perhaps you could overload the returned object (trx) to either take a string or a model, and enable both use cases.

As a user coming from Sails.js/Waterline and looking for a more "Data Mapping" approach to things, Bookshelf.js looks really exciting. Especially all of the changes proposed here!
If I start writing my project now using Bookshelf 0.7, how tricky do you anticipate the transition to be with all of the breaking changes?

@thomasdashney great, hopefully we don't make it too tricky! :)
Actually with the proposed syntax changes it should be possible to develop a lot of the new API alongside the existing Bookshelf codebase so it's less of a big-bang rewrite and we can figure out where exactly things are changing/breaking to be able to provide useful upgrade paths or error messages as we shuffle things around a bit.
Need to plan some time in the near future to hash out some of the new ideas with @tkellen @bendrucker and @johanneslumpe and provide a bit more of a concrete roadmap, but I wouldn't say it'll be a rewrite your app type deal.

The ability to hot-swap database instances would be an awesome byproduct of #90. Right now, with knex/bookshelf, if the DB goes down, the nodejs instance has to be restarted with a new configuration. It's really terrible for failover.
Being able to just watch a JSON file that a devops system can edit, and hot swap instances accordingly would be amazing.

I'd say that two critical things for relations are as follows:
1. Refined relation queries
It ought to be possible to define certain constraints on relations beyond the foreign key - think something along these lines (see also the second point below):
node: function(){
    return this
        .belongsTo("Node", "node_id", "perma_id")
        .where( { is_latest_revision: true } );
}

2. Column names
Right now, relations make certain assumptions; they sometimes assume things about the column naming scheme (like was the case with polymorphic relations prior to my patch for this), and they assume that the primary key is always the key that is used for foreign keys. Neither assumption is correct.
A practical example of the second issue: in a revisioned table, a revision may be identified by a particular primary key, while foreign keys in other tables may be refering to the persistent (revision-independent) ID of an object, and where it is expected to simply resolve to the latest revision for that object ID (this also ties into my first point above, regarding refined relations).

@tgriesser, it's good to hear that collections are going. Is there anything more concrete planned for the new Collection API? I thought I'd share my two cents on the topic.
I think simply using fetchAll is sufficient. Relationships could return a Model, rather than a Collection instance. Something like this:

Person = bookshelf.Model.extend
  tableName: 'persons'
  employees: -> @hasMany 'Person', 'employer_id'
  employer:  -> @belongsTo 'Person', 'employer_id'

person = Person.forge(id: 42)
employeesPromise = person.employees().fetchAll()
employerPromise = person.employer().fetch()
# `fetch` is the same as `fetchAll`, but uses `limit(1)` and returns the model
# rather than returning a `ResultSet`

Where the Person model returned by employees() would have its attributes prefilled to { employer_id: 42 }. Calling fetchAll would return a ResultSet filtered by those attributes. This would address a number of pain points I've experienced recently.
Is this similar to what is planned?

@tgriesser Is the API going to change to a ES6 syntax? Or that change is internal only?

It'll depend, internally it'll be ES6/7 but it'll of course still be possible to continue to write in ES5, there might just be some things that are simpler/more idiomatic when written in ES6

Hey, what I'd love to see is some possibility to share schema definitions with the browser, so parsing the models from JSON Schema or some base-class that doesn't require bookshelf. What do you think?

@bkniffler I'd imagine that if models become decoupled from a Bookshelf instance (ie. stateless), that shouldn't be too hard to write a third-party module for, even if it isn't in core.

Don't know if this is the right place, but I'd like to be able to provide a context for my queries on a specific model or set of models. For instance, if a user logs into a multi-user application, I only want queries to target rows that involve that user ID. I can do that manually, but I think I'd like an API like this:
var model = bookshelf('tasks').context({
		tasks: user_id: user.user_id
	});

I'm not yet sure if this is really possible with bookshelf. It looks as though calling model.where() doesn't returns a chainable object, but not the root model object. I'd like to be able to set a clause on the model object that I could use for all subsequent calls to that model. I have more experimentation to do, but I'd love to learn what I can do to make this work.

@jedd-ahyoung Would that context need to be persisted across requests?

@ricardograca It could, for certain cases, like issuing complex queries only specifying active tasks (as an example). In other cases, I think it could work as something that you could set per lifecycle; in the previous example, I'd like to be able to set the user in the bookshelf query per HTTP request without having to make multiple where clauses.
I've been trying to set this up manually. Perhaps this functionality is already available with Bookshelf.Collections.extend.

For instance, if a user logs into a multi-user application, I only want queries to target rows that involve that user ID.

You're describing relations. This is already supported:
// In this example I'm using the `user` variable as assigned by PassportJS.
// It is just a normal Bookshelf `Model` instance.
router.route('/items')
.get(function (req, res, next) {
  req.user.load('items').then(function (user) {
    req.status(200).json(user.related('items'));
  });
})
.post(function (req, res, next) {
  req.user.related('items').create(req.body).then(res.json);
});

Perhaps this functionality is already available with Bookshelf.Collections.extend.

Yes it is actually. Although there is no need for a special context method. You can do this:
var tasksForUser = Task.where({user_id: user.user_id}).fetchAll();

// Or you can make helper functions (better for more complex filters):

Collection = bookshelf.Model.extend({
  tableName: 'tasks',
  forUser: function(userId) {
    return this.where({userId: userId});
  }
  // ...
});

Task.forge().forUser(user.user_id).fetchAll();

If you want nicer behaviour you could check out the scopes plugin that @jtwebman created.

:+1:
@tgriesser: Do you have any thoughts regarding the implementation of this?

Camel Case

parse and transform and such are pretty weak, and they're mostly used for camel casing attrs, so we'll just add this as an option, keeping the model as the transform layer for the keys so we don't need to go to and from all the time when coming from the db. Then we'll advertise the parse and transform

If you are willing, I would like to help by implementing this to your specifications. The simplest way may be to apply case conversion in the set, get and toJSON methods of the base/Model, as well as add a call to convertKeysToSnakeCase anywhere that format is currently called.
Is this something that could be added into Bookshelf now-ish, then updated as necessary as the other new features mentioned above roll in?

In addition to this:
bookshelf('user').where({id: 1}).fetch().then(...
bookshelf('user', {name: 'Tim'}).save().then(...

I would give the possibility to work with Repositories:
// app/models/user.js
var Bookshelf = require('bookshelf');

class User extends Bookshelf.Model {
   getTableName() {
     return 'users';
   }
}

// app/repos/users.js
var Bookshelf = require('bookshelf');
var User = require('../models/user');

class Users extends Bookshelf.Repository {
   getModel() {
     return User;
   }
}

// app/services/users.js
var bookshelf = require('../services/bookshelf');
var Users = require('../repos/users');

module.exports = bookshelf.createRepo(Users); // Instanciates repo..

// app/controllers/user.js
var User = require('../models/user');
var users = require('../services/users');

module.exports = {
  get: function(id) {
    return users.find(id).toJson(); // Returns `User` instance
  },
  post: function() {
    var user = new User(...postData...);
    // -- or --
    var user = users.create(...postData...);

    user = users.save(user);

    return user.toJson();
  },
  put: function(id) {
    var user = users.find(id);
    user.email = ...putParams.email;

    user = users.save(user);

    return user.toJson();
  }
};

Or the like.

The project leadership of Bookshelf recently changed. In an effort to advance the project we close all issues older than one year.
If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.
We also started an open discussion about the future of Bookshelf.js here https://github.com/bookshelf/bookshelf/issues/1600. Feel free to drop by and give us your opinion.
Let's make Bookshelf great again


NPM Test is failing

  4 passing (21s)
  1 failing

  1) Google Tests
       should return the correct length with pagination:

      AssertionError: expected 0 to equal 300
      + expected - actual

      -0
      +300

      at Context.<anonymous> (test/google.js:31:31)

Thanks for reporting @Extracreative . I believe it is fixed in: https://github.com/pevers/images-scraper/pull/50
There were some issues with JS injection of the real image URLs.

@pevers  Thank you


jdbc postgres fail

hello ,  jdbc bridage fail for postgres driver as the following
Code: 86. DB::Exception: Received from localhost:9000. DB::Exception: Received error from remote server /identifier_quote?connection_string=jdbc%3Apostgresql%3A%2F%2Fttc-...... HTTP status code: 500 Server Error, body: No suitable driver found for jdbc:postgresql://.......

Download postgresql-42.2.5.jar

Where to put the driver jar files?

/var/lib/clickhouse-jdbc-bridge
or
change in  default config BRIDGE_DRIVER_DIR  variable

Close as this looks like a configuration issue,  not a defect in code.


GCC: Graph Contrastive Coding for Graph Neural Network Pre-training.

Alibaba Cloud. GCC: Graph Contrastive Coding for Graph Neural Network Pre-training.

Overview
Download the “Cloud Knowledge Discovery on KDD Papers” whitepaper to explore 12 KDD papers and knowledge discovery from 12 Alibaba experts. By Jiezhong Qiu, Qibin Chen, Yuxiao Dong, Jing Zhang, Hongxia Yang, Ming Ding, Kuansan Wang, Jie Tang.
Graph representation learning has received extensive attention. However, most graph representation learning methods are used to learn and model graphs for domain specific problems. The generated graph neural networks are difficult to transfer out of the domain. Recently, pre-training has been a great success in many domains, which significantly improves the model performance in downstream tasks. Inspired by Bidirectional Encoder Representations from Transformers (BERT, Devlin et al., 2018), we began to study the pre-training of graph neural networks, hoping to learn the general graph topology features. We design Graph Contrastive Coding (GCC), a graph neural network pre-training framework that

uses the contrastive learning method to learn the intrinsic and transferable structure representations.

This paper “GCC: Graph Contrastive Coding for Graph Neural Network Pre-training” has been accepted by KDD 2020 Research Track.
Traditional graph representation learning primarily uses skip-gram based word representation learning models such as DeepWalk and Node2vec in natural language processing (NLP). These methods model the similarities between neighboring nodes, and the created models and trained representations are not generic but limited to specific networks. Different from these traditional attempts, GCC focuses on structural similarities. The representations learned by GCC are generic and can be transferred to all types of networks. The following figure shows the basic framework of GCC.

Graph Contrastive Coding
Traditional graph representation learning primarily uses skip-gram based word representation learning models such as DeepWalk and Node2vec in natural language processing (NLP). These methods model the similarities between neighboring nodes, and the created models and trained representations are not generic but limited to specific networks. Different from these traditional attempts, GCC focuses on structural similarities. The representations learned by GCC are generic and can be transferred to all types of networks. The following figure shows the basic framework of GCC.

GCC leverages the contrastive learning framework to reduce the spatial distance between positive sample representations and sample representations while increasing the spatial distance between negative sample representations. In contrastive learning, for a given query representation $q$, a candidate set contains $K+1$ representations $\{k_0,k_1,⋯,k_K\}$$, of which $k_+$ are positive samples. The loss function is optimized as follows:

$q$ and $k$ are low-dimensional representations of the samples $x^q$ and $x^k$, respectively. GCC is mainly designed to sample the subgraph of the network (or r-ego network) that is formed by the r-order neighbors of a specific node. Positive samples are the networks sampled from the same r-ego network, whereas a large number of negative samples are the subgraphs sampled from other r-ego networks. After acquiring both positive and negative samples, we started to build a graph encoder for graph representation learning. Any graph neural network can be used as a GCC encoder. In practice, we used a graph isomorphism network (GIN) as the encoder.
In contrastive learning, it is required to maintain the $K$-size dictionary and encoders. Ideally, to calculate the preceding loss function, the dictionary should cover all negative samples. This makes $K$ extremely large and the dictionary difficult to maintain. To ensure model efficiencies, we added Momentum Contrast (MoCo, He et al., 2020). In the MoCo framework, we need to maintain a queue of negative samples in order to increase the dictionary size $K$. These negative samples are derived from the samples of previously trained batches. For the $\theta_q$ parameter of the $f_q$ encoder of $q$, updates are propagated in reverse order. For the $\theta_k$ parameter of the $f_k$ encoder of $k$, updates are propagated as follows:

$m$ denotes the momentum, which is specified by a hyperparameter. For GCC, MoCo is more efficient than other methods.
GCC is applicable to downstream tasks at the graph level and node level. Downstream tasks at the graph level can be input as subgraphs. This situation is the same as that in pre-training. For downstream tasks at the node level, we need to acquire their r-ego networks or subgraphs sampled from their r-ego networks.
To verify the effect of GCC, we conducted a series of experiments, including node classification, graph classification, and similarity search. The results are as follows:

Node classification.

Graph classification.

Similarity search.

According to the experiment results, GCC excels at processing multiple tasks and datasets. Its performance is close to or better than the existing optimal model. This shows the effectiveness of GCC.

Experiments
To verify the effect of GCC, we conducted a series of experiments, including node classification, graph classification, and similarity search. The results are as follows:

Node classification.

Graph classification.

Similarity search.

According to the experiment results, GCC excels at processing multiple tasks and datasets. Its performance is close to or better than the existing optimal model. This shows the effectiveness of GCC.

Summary
To sum up, in this work, we propose GCC, which is a graph-based contrastive learning framework to pre-train graph neural networks. The GCC method learns the generic representations of graph structures to acquire the structured information of graphs. These representations can be transferred to all types of downstream tasks and graphs. The experiment results show the effectiveness of GCC. In the future, we plan to test GCC on more tasks and experiments, and explore the application of GCC in other fields.

References

Devlin, J., Chang, M. W., Lee, K., & Toutanova, K. (2018). Bert: Pre-training of deep bidirectional transformers for language understanding. arXiv preprint arXiv:1810.04805.
He, K., Fan, H., Wu, Y., Xie, S., & Girshick, R. (2020). Momentum contrast for unsupervised visual representation learning. In Proceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition (pp. 9729–9738).


Where does the call back code go

Where do we put the following code:
// Define your callback URI's here
'redirect' => [
'success' => 'http://chargebee.app/success',
'cancelled' => null,
],

The chargebee.php config file was not automatically copied over.


CI: embedings

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: glookka:x: donhardmanYou have signed the CLA already but the status is still pending? Let us recheck it.


[Javascript] Call for Contribution and Suggestions

This thread is opened to bring attention to https://github.com/dmlc/mxnet.js . The javascript port of mxnet that runs completely on browser, thanks to emscripten and amalgamation. This is fun. This thread is opened for suggestions and contributions to the library, including

[ ] Improve html demo
[ ] Cleanup and generate documents for Javascript code
[ ] More fun demos, as it enables any mxnet model basically on js.

Non of the current DMLC developers are javascript hackers, so the library was in primal but working stage, we are definitely looking for contributors to improve and lead the project

Nice idea. We just need a working plan.

Very Nice, I still need to catch up with the white paper to learn more. I
will post if I have any suggestions. Great job, guys!
thanks.
junli
On Fri, Dec 4, 2015 at 1:07 PM, skevidu<EMAIL_ADDRESS>wrote:

Nice idea. We just need a working plan.
—
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/issues/821#issuecomment-162082021.

--

Junli Gu--谷俊丽
Coordinated Science Lab
University of Illinois at Urbana-Champaign

moving discussion directly to https://github.com/dmlc/mxnet.js/issues/2


Error connecting

Since some days I'm getting a connection error. I haven't changed anything in configuration or password. Is something changed or it's on my end?
[15:38:56 WRN] Error connecting to https://authz.sdpr-01.fcagcv.com/v2/cognito/identity/token. Result: Forbidden. Retrying in 00:00:01 [15:38:57 WRN] Error connecting to https://authz.sdpr-01.fcagcv.com/v2/cognito/identity/token. Result: Forbidden. Retrying in 00:00:02 [15:39:00 WRN] Error connecting to https://authz.sdpr-01.fcagcv.com/v2/cognito/identity/token. Result: Forbidden. Ret

Had to relogin trough app and give privacy consent again


CREATE_FAILED rCreateContainerLambda when trying to add video

App Id: d1krklz2q4zgk0
Region: ap-southeast-1
Step: rCreateContainerLambda
Status: CREATE_FAILED
Issue/question
Been following the Introducing AWS Amplify Video blog post to test out the AWS Amplify Video setup.
When trying to push the setup to the AWS Console in the cloud, I get the follow errors in the local console.
Error message
...
CREATE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:53:20 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_FAILED      rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:53:20 GMT+0800 (Singapore Standard Time) Failed to create resource. See details in CloudWatch Log Stream: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154
CREATE_FAILED      amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack     Wed Oct 28 2020 15:53:21 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rCreateContainerLambda].
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED rContainer AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:24 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L/a148b0e0-18f2-11eb-8e9b-06f82009c61a was not successfully created: The following resource(s) failed to create: [rCreateContainerLambda].
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED rMS                                                                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:25 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU/6f83e840-18f2-11eb-9dc3-0243768bbe4a was not successfully created: The following resource(s) failed to create: [rContainer].
CREATE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:26 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rMS].
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:24 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rContainer].
⠇ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED               videomylivestream                       AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:39 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX/6c307780-18f2-11eb-9a87-0a9a2b745e0a was not successfully created: The following resource(s) failed to create: [rMS].
UPDATE_ROLLBACK_IN_PROGRESS amplify-myamplifyvideostream-dev-151005 AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:39 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [videomylivestream].
⠏ Updating resources in the cloud. This may take a few minutes...
...

Additional information
The entire log posted below
[myamplifyvideostream] amplify push
Scanning for plugins...
Plugin scan successful
⠙ Copying video resources. This may take a few minutes...(node:38105) ExperimentalWarning: The fs.promises API is experimental
✔ All resources copied.
✔ Successfully pulled backend environment dev from the cloud.

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Video    | mylivestream  | Create    | awscloudformation |
? Are you sure you want to continue? Yes
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005 AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:38 GMT+0800 (Singapore Standard Time) User Initiated
UPDATE_IN_PROGRESS DeploymentBucket                        AWS::S3::Bucket            Wed Oct 28 2020 15:51:43 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS videomylivestream                       AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:43 GMT+0800 (Singapore Standard Time)
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS UnauthRole        AWS::IAM::Role             Wed Oct 28 2020 15:51:43 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS AuthRole          AWS::IAM::Role             Wed Oct 28 2020 15:51:43 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:44 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:44 GMT+0800 (Singapore Standard Time) User Initiated
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rMS AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:49 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rMS AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:49 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠇ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:49 GMT+0800 (Singapore Standard Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rIAM AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:54 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rIAM AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:54 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EO-rIAM-1XU6D6THJ641N AWS::CloudFormation::Stack Wed Oct 28 2020 15:51:54 GMT+0800 (Singapore Standard Time) User Initiated
CREATE_IN_PROGRESS rManagedPolicy                                                                                AWS::IAM::ManagedPolicy    Wed Oct 28 2020 15:51:58 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE UnauthRole AWS::IAM::Role Wed Oct 28 2020 15:52:02 GMT+0800 (Singapore Standard Time)
UPDATE_COMPLETE AuthRole   AWS::IAM::Role Wed Oct 28 2020 15:52:02 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE DeploymentBucket AWS::S3::Bucket Wed Oct 28 2020 15:52:03 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rManagedPolicy AWS::IAM::ManagedPolicy Wed Oct 28 2020 15:52:00 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE    rManagedPolicy AWS::IAM::ManagedPolicy Wed Oct 28 2020 15:52:20 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rProvisionRole AWS::IAM::Role          Wed Oct 28 2020 15:52:22 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rProvisionRole AWS::IAM::Role          Wed Oct 28 2020 15:52:24 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE rProvisionRole                                                                                AWS::IAM::Role             Wed Oct 28 2020 15:52:45 GMT+0800 (Singapore Standard Time)
CREATE_COMPLETE amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EO-rIAM-1XU6D6THJ641N AWS::CloudFormation::Stack Wed Oct 28 2020 15:52:47 GMT+0800 (Singapore Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE    rIAM                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:52:56 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rProvisionLambdaFunction AWS::CloudFormation::Stack Wed Oct 28 2020 15:52:58 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rProvisionLambdaFunction AWS::CloudFormation::Stack Wed Oct 28 2020 15:52:59 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠼ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM-rProvisionLambdaFunction-BMLGKFMGPC07 AWS::CloudFormation::Stack Wed Oct 28 2020 15:52:58 GMT+0800 (Singapore Standard Time) User Initiated
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rLambdaFunction AWS::Lambda::Function Wed Oct 28 2020 15:53:04 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rLambdaFunction                                                                                AWS::Lambda::Function      Wed Oct 28 2020 15:53:04 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_COMPLETE    rLambdaFunction                                                                                AWS::Lambda::Function      Wed Oct 28 2020 15:53:05 GMT+0800 (Singapore Standard Time)
CREATE_COMPLETE    amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM-rProvisionLambdaFunction-BMLGKFMGPC07 AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:07 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE    rProvisionLambdaFunction AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:09 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rContainer               AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:12 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rContainer               AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:13 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:13 GMT+0800 (Singapore Standard Time) User Initiated
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rCreateContainerLambda Custom::rCreateContainerLambda Wed Oct 28 2020 15:53:17 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:53:20 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_FAILED      rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:53:20 GMT+0800 (Singapore Standard Time) Failed to create resource. See details in CloudWatch Log Stream: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154
CREATE_FAILED      amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack     Wed Oct 28 2020 15:53:21 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rCreateContainerLambda].
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED rContainer AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:24 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L/a148b0e0-18f2-11eb-8e9b-06f82009c61a was not successfully created: The following resource(s) failed to create: [rCreateContainerLambda].
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED rMS                                                                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:25 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU/6f83e840-18f2-11eb-9dc3-0243768bbe4a was not successfully created: The following resource(s) failed to create: [rContainer].
CREATE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:26 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rMS].
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:24 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rContainer].
⠇ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED               videomylivestream                       AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:39 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX/6c307780-18f2-11eb-9a87-0a9a2b745e0a was not successfully created: The following resource(s) failed to create: [rMS].
UPDATE_ROLLBACK_IN_PROGRESS amplify-myamplifyvideostream-dev-151005 AWS::CloudFormation::Stack Wed Oct 28 2020 15:53:39 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [videomylivestream].
⠏ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS AuthRole         AWS::IAM::Role  Wed Oct 28 2020 15:53:47 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS UnauthRole       AWS::IAM::Role  Wed Oct 28 2020 15:53:47 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS DeploymentBucket AWS::S3::Bucket Wed Oct 28 2020 15:53:47 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              AuthRole                                AWS::IAM::Role             Wed Oct 28 2020 15:54:06 GMT+0800 (Singapore Standard Time)
UPDATE_COMPLETE                              UnauthRole                              AWS::IAM::Role             Wed Oct 28 2020 15:54:06 GMT+0800 (Singapore Standard Time)
UPDATE_COMPLETE                              DeploymentBucket                        AWS::S3::Bucket            Wed Oct 28 2020 15:54:07 GMT+0800 (Singapore Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS amplify-myamplifyvideostream-dev-151005 AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:08 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:09 GMT+0800 (Singapore Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:09 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rMS                                                                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:12 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:12 GMT+0800 (Singapore Standard Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rContainer AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:15 GMT+0800 (Singapore Standard Time)
⠧ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack     Wed Oct 28 2020 15:54:15 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:54:18 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:54:20 GMT+0800 (Singapore Standard Time) Failed to delete resource. See details in CloudWatch Log Stream: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154
DELETE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack     Wed Oct 28 2020 15:54:20 GMT+0800 (Singapore Standard Time) The following resource(s) failed to delete: [rCreateContainerLambda].
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED      rContainer               AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:25 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L/a148b0e0-18f2-11eb-8e9b-06f82009c61a was not successfully deleted: The following resource(s) failed to delete: [rCreateContainerLambda].
DELETE_IN_PROGRESS rProvisionLambdaFunction AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:26 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM-rProvisionLambdaFunction-BMLGKFMGPC07 AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:27 GMT+0800 (Singapore Standard Time) User Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rLambdaFunction AWS::Lambda::Function Wed Oct 28 2020 15:54:29 GMT+0800 (Singapore Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rLambdaFunction                                                                                AWS::Lambda::Function      Wed Oct 28 2020 15:54:30 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM-rProvisionLambdaFunction-BMLGKFMGPC07 AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:30 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE    rProvisionLambdaFunction AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:37 GMT+0800 (Singapore Standard Time)
DELETE_IN_PROGRESS rIAM                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:38 GMT+0800 (Singapore Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EO-rIAM-1XU6D6THJ641N AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:38 GMT+0800 (Singapore Standard Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rProvisionRole AWS::IAM::Role Wed Oct 28 2020 15:54:41 GMT+0800 (Singapore Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE    rProvisionRole                                                                                AWS::IAM::Role             Wed Oct 28 2020 15:54:44 GMT+0800 (Singapore Standard Time)
DELETE_IN_PROGRESS rManagedPolicy                                                                                AWS::IAM::ManagedPolicy    Wed Oct 28 2020 15:54:45 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    rManagedPolicy                                                                                AWS::IAM::ManagedPolicy    Wed Oct 28 2020 15:54:47 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EO-rIAM-1XU6D6THJ641N AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:48 GMT+0800 (Singapore Standard Time)
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rIAM AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:49 GMT+0800 (Singapore Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:49 GMT+0800 (Singapore Standard Time) The following resource(s) failed to delete: [rContainer].
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED rMS                                                                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:54:59 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU/6f83e840-18f2-11eb-9dc3-0243768bbe4a was not successfully deleted: The following resource(s) failed to delete: [rContainer].
DELETE_FAILED amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:55:00 GMT+0800 (Singapore Standard Time) The following resource(s) failed to delete: [rMS].
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED videomylivestream AWS::CloudFormation::Stack Wed Oct 28 2020 15:55:11 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX/6c307780-18f2-11eb-9a87-0a9a2b745e0a was not successfully deleted: The following resource(s) failed to delete: [rMS].
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:12 GMT+0800 (Singapore Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:13 GMT+0800 (Singapore Standard Time) User Initiated
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rMS AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:15 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:15 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rContainer                                                                               AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:17 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:18 GMT+0800 (Singapore Standard Time) User Initiated
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:58:20 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Wed Oct 28 2020 15:58:21 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L AWS::CloudFormation::Stack     Wed Oct 28 2020 15:58:22 GMT+0800 (Singapore Standard Time)
⠼ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rContainer AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:28 GMT+0800 (Singapore Standard Time)
⠼ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-UY4EOLD4GKLU AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:29 GMT+0800 (Singapore Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rMS                                                                     AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:37 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE amplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:38 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE          videomylivestream                       AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:47 GMT+0800 (Singapore Standard Time)
UPDATE_ROLLBACK_COMPLETE amplify-myamplifyvideostream-dev-151005 AWS::CloudFormation::Stack Wed Oct 28 2020 15:58:47 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠴ Updating resources in the cloud. This may take a few minutes...

Following resources failed

Resource Name: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154 (Custom::rCreateContainerLambda)
Event Type: create
Reason: Failed to create resource. See details in CloudWatch Log Stream: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154

Resource Name: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154 (Custom::rCreateContainerLambda)
Event Type: delete
Reason: Failed to delete resource. See details in CloudWatch Log Stream: 2020/10/28/[$LATEST]f5391630f46c497e9fffc67543750154
URL: https://console.aws.amazon.com/cloudformation/home?region=ap-southeast-1#/stacks/arn%3Aaws%3Acloudformation%3Aap-southeast-1%3A816642277606%3Astack%2Famplify-myamplifyvideostream-dev-151005-videomylivestream-1PM38Q7JFDXNX-rMS-rContainer-9MKKCTFNMG5L%2Fa148b0e0-18f2-11eb-8e9b-06f82009c61a/events

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete
[myamplifyvideostream]

Hi @kristian-netflix. I wasn't able to reproduce this on the latest version of the CLI.
What version are you using? amplify -v

Hi @jhockett , I tried a fresh setup running amplify version 4.31.1.
These are my logs
Check amplify version
[myamplifyvideostream] amplify -v
4.31.1

Install amplify-category-video
[myamplifyvideostream] npm install amplify-category-video -g

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/amplify-category-video
> node scripts/post-install.js

------------------------------------

Successfully installed Amplify Video

------------------------------------

+<EMAIL_ADDRESS>updated 3 packages in 5.09s

Initiate amplify
[myamplifyvideostream] amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project myamplifyvideostream
? Enter a name for the environment dev
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building javascript
Please tell us about your project
? What javascript framework are you using vue
? Source Directory Path:  src
? Distribution Directory Path: dist
? Build Command:  npm run-script build
? Start Command: npm run-script serve
Using default provider  awscloudformation

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Do you want to use an AWS profile? (Y/n) (node:51751) ExperimentalWarning: The fs.promises API is experimental
? Do you want to use an AWS profile? Yes
? Please choose the profile you want to use default
Adding backend environment dev to AWS Amplify Console app: d3l09a8pdxzdcj
⠼ Initializing project in the cloud...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942 AWS::CloudFormation::Stack Fri Oct 30 2020 14:29:47 GMT+0800 (Singapore Standard Time) User Initiated
CREATE_IN_PROGRESS AuthRole                                AWS::IAM::Role             Fri Oct 30 2020 14:29:51 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS DeploymentBucket                        AWS::S3::Bucket            Fri Oct 30 2020 14:29:51 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS UnauthRole                              AWS::IAM::Role             Fri Oct 30 2020 14:29:51 GMT+0800 (Singapore Standard Time)
⠴ Initializing project in the cloud...

CREATE_IN_PROGRESS AuthRole         AWS::IAM::Role  Fri Oct 30 2020 14:29:52 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_IN_PROGRESS UnauthRole       AWS::IAM::Role  Fri Oct 30 2020 14:29:53 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_IN_PROGRESS DeploymentBucket AWS::S3::Bucket Fri Oct 30 2020 14:29:53 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠧ Initializing project in the cloud...

CREATE_COMPLETE AuthRole   AWS::IAM::Role Fri Oct 30 2020 14:30:12 GMT+0800 (Singapore Standard Time)
CREATE_COMPLETE UnauthRole AWS::IAM::Role Fri Oct 30 2020 14:30:12 GMT+0800 (Singapore Standard Time)
⠇ Initializing project in the cloud...

CREATE_COMPLETE DeploymentBucket                        AWS::S3::Bucket            Fri Oct 30 2020 14:30:14 GMT+0800 (Singapore Standard Time)
CREATE_COMPLETE amplify-myamplifyvideostream-dev-142942 AWS::CloudFormation::Stack Fri Oct 30 2020 14:30:17 GMT+0800 (Singapore Standard Time)
✔ Successfully created initial AWS cloud resources for deployments.
✔ Initialized provider successfully.
Initialized your environment successfully.

Your project has been successfully initialized and connected to the cloud!

Some next steps:
"amplify status" will show you what you've added already and if it's locally configured or deployed
"amplify add <category>" will allow you to add features like user login or a backend API
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify console" to open the Amplify Console and view your project status
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

Pro tip:
Try "amplify add api" to create a backend API and then "amplify publish" to deploy everything

Add amplify video to the project
[myamplifyvideostream] amplify video add
? Please select from one of the below mentioned services: AWS Elemental Live Stream
? Provide a friendly name for your resource to be used as a label for this category in the project: mylivestream
? Do you want to modify any advanced video encoding parameters? Yes
? GOP Size: 1
? GOP(s) Per Segment: 2
? Segment(s) Per Playlist: 3
? Input Security Group:  <IP_ADDRESS>/0
? MediaLive ingest type:  RTMP_PUSH
? Encoding Profile:  FULL (6 renditions)
? Auto Start:  Yes
? Where do you want to stream to? MediaStore
✔ All resources built.

Push setup to AWS Console cloud
[myamplifyvideostream] amplify push
⠙ Copying video resources. This may take a few minutes...(node:51875) ExperimentalWarning: The fs.promises API is experimental
✔ All resources copied.
✔ Successfully pulled backend environment dev from the cloud.

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Video    | mylivestream  | Create    | awscloudformation |
? Are you sure you want to continue? Yes
⠼ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942 AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:02 GMT+0800 (Singapore Standard Time) User Initiated
⠼ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:07 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS DeploymentBucket  AWS::S3::Bucket            Fri Oct 30 2020 14:33:07 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS UnauthRole        AWS::IAM::Role             Fri Oct 30 2020 14:33:07 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS AuthRole          AWS::IAM::Role             Fri Oct 30 2020 14:33:07 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:09 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:09 GMT+0800 (Singapore Standard Time) User Initiated
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rMS AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:13 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rMS AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:15 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:15 GMT+0800 (Singapore Standard Time) User Initiated
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rIAM AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:19 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rIAM AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:21 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD-rIAM-HTP7JKZ4EFR4 AWS::CloudFormation::Stack Fri Oct 30 2020 14:33:21 GMT+0800 (Singapore Standard Time) User Initiated
⠧ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE UnauthRole AWS::IAM::Role Fri Oct 30 2020 14:33:26 GMT+0800 (Singapore Standard Time)
UPDATE_COMPLETE AuthRole   AWS::IAM::Role Fri Oct 30 2020 14:33:26 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rManagedPolicy AWS::IAM::ManagedPolicy Fri Oct 30 2020 14:33:26 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rManagedPolicy AWS::IAM::ManagedPolicy Fri Oct 30 2020 14:33:27 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠇ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE DeploymentBucket AWS::S3::Bucket Fri Oct 30 2020 14:33:27 GMT+0800 (Singapore Standard Time)
⠧ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE rManagedPolicy AWS::IAM::ManagedPolicy Fri Oct 30 2020 14:33:46 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rProvisionRole AWS::IAM::Role Fri Oct 30 2020 14:33:48 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rProvisionRole AWS::IAM::Role Fri Oct 30 2020 14:33:50 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE rProvisionRole                                                                                AWS::IAM::Role             Fri Oct 30 2020 14:34:09 GMT+0800 (Singapore Standard Time)
CREATE_COMPLETE amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD-rIAM-HTP7JKZ4EFR4 AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:11 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE    rIAM                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:23 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rProvisionLambdaFunction AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:24 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rProvisionLambdaFunction AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:26 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJ-rProvisionLambdaFunction-1H99Z6AY2WET6 AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:26 GMT+0800 (Singapore Standard Time) User Initiated
⠼ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rLambdaFunction AWS::Lambda::Function Fri Oct 30 2020 14:34:30 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rLambdaFunction AWS::Lambda::Function Fri Oct 30 2020 14:34:31 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_COMPLETE    rLambdaFunction AWS::Lambda::Function Fri Oct 30 2020 14:34:31 GMT+0800 (Singapore Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE rProvisionLambdaFunction AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:37 GMT+0800 (Singapore Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rContainer AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:39 GMT+0800 (Singapore Standard Time)
CREATE_IN_PROGRESS rContainer AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:41 GMT+0800 (Singapore Standard Time) Resource creation Initiated
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:40 GMT+0800 (Singapore Standard Time) User Initiated
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rCreateContainerLambda Custom::rCreateContainerLambda Fri Oct 30 2020 14:34:45 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED rContainer                                                                               AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:51 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE/fcc78030-1a79-11eb-a048-06c012599cae was not successfully created: The following resource(s) failed to create: [rCreateContainerLambda].
CREATE_FAILED amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:52 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rContainer].
⠧ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Fri Oct 30 2020 14:34:48 GMT+0800 (Singapore Standard Time) Resource creation Initiated
CREATE_FAILED      rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Fri Oct 30 2020 14:34:48 GMT+0800 (Singapore Standard Time) Failed to create resource. See details in CloudWatch Log Stream: 2020/10/30/[$LATEST]be2a520db04b4db796eccce21353a09f
CREATE_FAILED      amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE AWS::CloudFormation::Stack     Fri Oct 30 2020 14:34:49 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rCreateContainerLambda].
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED rMS                                                                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:35:10 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ/c9c97440-1a79-11eb-9799-06f82009c61a was not successfully created: The following resource(s) failed to create: [rContainer].
CREATE_FAILED amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I AWS::CloudFormation::Stack Fri Oct 30 2020 14:35:11 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [rMS].
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED               videomylivestream                       AWS::CloudFormation::Stack Fri Oct 30 2020 14:35:24 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I/c60a4960-1a79-11eb-a713-0aab1244f3ea was not successfully created: The following resource(s) failed to create: [rMS].
UPDATE_ROLLBACK_IN_PROGRESS amplify-myamplifyvideostream-dev-142942 AWS::CloudFormation::Stack Fri Oct 30 2020 14:35:25 GMT+0800 (Singapore Standard Time) The following resource(s) failed to create: [videomylivestream].
⠧ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS UnauthRole       AWS::IAM::Role  Fri Oct 30 2020 14:35:40 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS DeploymentBucket AWS::S3::Bucket Fri Oct 30 2020 14:35:40 GMT+0800 (Singapore Standard Time)
UPDATE_IN_PROGRESS AuthRole         AWS::IAM::Role  Fri Oct 30 2020 14:35:40 GMT+0800 (Singapore Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              AuthRole                                AWS::IAM::Role             Fri Oct 30 2020 14:35:59 GMT+0800 (Singapore Standard Time)
UPDATE_COMPLETE                              UnauthRole                              AWS::IAM::Role             Fri Oct 30 2020 14:35:59 GMT+0800 (Singapore Standard Time)
UPDATE_COMPLETE                              DeploymentBucket                        AWS::S3::Bucket            Fri Oct 30 2020 14:36:00 GMT+0800 (Singapore Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS amplify-myamplifyvideostream-dev-142942 AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:01 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:03 GMT+0800 (Singapore Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:03 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rMS                                                                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:06 GMT+0800 (Singapore Standard Time)
⠼ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:06 GMT+0800 (Singapore Standard Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rContainer AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:08 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE AWS::CloudFormation::Stack     Fri Oct 30 2020 14:36:09 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Fri Oct 30 2020 14:36:11 GMT+0800 (Singapore Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJ-rProvisionLambdaFunction-1H99Z6AY2WET6 AWS::CloudFormation::Stack Fri Oct 30 2020 14:34:34 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Fri Oct 30 2020 14:36:14 GMT+0800 (Singapore Standard Time) Failed to delete resource. See details in CloudWatch Log Stream: 2020/10/30/[$LATEST]be2a520db04b4db796eccce21353a09f
DELETE_FAILED amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE AWS::CloudFormation::Stack     Fri Oct 30 2020 14:36:14 GMT+0800 (Singapore Standard Time) The following resource(s) failed to delete: [rCreateContainerLambda].
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED      rContainer               AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:19 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE/fcc78030-1a79-11eb-a048-06c012599cae was not successfully deleted: The following resource(s) failed to delete: [rCreateContainerLambda].
DELETE_IN_PROGRESS rProvisionLambdaFunction AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:20 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJ-rProvisionLambdaFunction-1H99Z6AY2WET6 AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:20 GMT+0800 (Singapore Standard Time) User Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rLambdaFunction AWS::Lambda::Function Fri Oct 30 2020 14:36:23 GMT+0800 (Singapore Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rLambdaFunction                                                                                AWS::Lambda::Function      Fri Oct 30 2020 14:36:23 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJ-rProvisionLambdaFunction-1H99Z6AY2WET6 AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:24 GMT+0800 (Singapore Standard Time)
⠧ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE    rProvisionLambdaFunction AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:31 GMT+0800 (Singapore Standard Time)
DELETE_IN_PROGRESS rIAM                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:32 GMT+0800 (Singapore Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD-rIAM-HTP7JKZ4EFR4 AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:32 GMT+0800 (Singapore Standard Time) User Initiated
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rProvisionRole AWS::IAM::Role Fri Oct 30 2020 14:36:35 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rProvisionRole AWS::IAM::Role Fri Oct 30 2020 14:36:38 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rManagedPolicy                                                                                AWS::IAM::ManagedPolicy    Fri Oct 30 2020 14:36:39 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    rManagedPolicy                                                                                AWS::IAM::ManagedPolicy    Fri Oct 30 2020 14:36:41 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD-rIAM-HTP7JKZ4EFR4 AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:41 GMT+0800 (Singapore Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rIAM                                                                                AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:43 GMT+0800 (Singapore Standard Time)
DELETE_FAILED   amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:43 GMT+0800 (Singapore Standard Time) The following resource(s) failed to delete: [rContainer].
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED rMS                                                                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:53 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ/c9c97440-1a79-11eb-9799-06f82009c61a was not successfully deleted: The following resource(s) failed to delete: [rContainer].
DELETE_FAILED amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I AWS::CloudFormation::Stack Fri Oct 30 2020 14:36:54 GMT+0800 (Singapore Standard Time) The following resource(s) failed to delete: [rMS].
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_FAILED videomylivestream AWS::CloudFormation::Stack Fri Oct 30 2020 14:37:04 GMT+0800 (Singapore Standard Time) Embedded stack arn:aws:cloudformation:ap-southeast-1:816642277606:stack/amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I/c60a4960-1a79-11eb-a713-0aab1244f3ea was not successfully deleted: The following resource(s) failed to delete: [rMS].
⠋ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS videomylivestream AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:07 GMT+0800 (Singapore Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:08 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rMS                                                                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:10 GMT+0800 (Singapore Standard Time)
⠼ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:11 GMT+0800 (Singapore Standard Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS rContainer AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:13 GMT+0800 (Singapore Standard Time)
⠧ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE AWS::CloudFormation::Stack     Fri Oct 30 2020 14:40:13 GMT+0800 (Singapore Standard Time) User Initiated
DELETE_IN_PROGRESS rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Fri Oct 30 2020 14:40:16 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    rCreateContainerLambda                                                                              Custom::rCreateContainerLambda Fri Oct 30 2020 14:40:16 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE    amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE AWS::CloudFormation::Stack     Fri Oct 30 2020 14:40:17 GMT+0800 (Singapore Standard Time)
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rContainer                                                                               AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:24 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-OASYD5HWNBIJ AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:25 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE rMS                                                                     AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:33 GMT+0800 (Singapore Standard Time)
DELETE_COMPLETE amplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:33 GMT+0800 (Singapore Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE videomylivestream AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:42 GMT+0800 (Singapore Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE amplify-myamplifyvideostream-dev-142942 AWS::CloudFormation::Stack Fri Oct 30 2020 14:40:42 GMT+0800 (Singapore Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠴ Updating resources in the cloud. This may take a few minutes...

Following resources failed

Resource Name: 2020/10/30/[$LATEST]be2a520db04b4db796eccce21353a09f (Custom::rCreateContainerLambda)
Event Type: create
Reason: Failed to create resource. See details in CloudWatch Log Stream: 2020/10/30/[$LATEST]be2a520db04b4db796eccce21353a09f

Resource Name: 2020/10/30/[$LATEST]be2a520db04b4db796eccce21353a09f (Custom::rCreateContainerLambda)
Event Type: delete
Reason: Failed to delete resource. See details in CloudWatch Log Stream: 2020/10/30/[$LATEST]be2a520db04b4db796eccce21353a09f
URL: https://console.aws.amazon.com/cloudformation/home?region=ap-southeast-1#/stacks/arn%3Aaws%3Acloudformation%3Aap-southeast-1%3A816642277606%3Astack%2Famplify-myamplifyvideostream-dev-142942-videomylivestream-1LJOW4ZD2WJ3I-rMS-rContainer-3O7QGPKJX2WE%2Ffcc78030-1a79-11eb-a048-06c012599cae/events

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete

Could it have something to do with my region?
Thanks

@kristian-netflix I don't think the region is the issue. Amplify and the AWS Elemental services listed in the blog are supported in ap-southeast-1: https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/
What version of node are you using?
I ask because I haven't seen amplify init print this warning before: Do you want to use an AWS profile? (Y/n) (node:51751) ExperimentalWarning: The fs.promises API is experimental

Hi @kristian-netflix have you tried filing an issue in the Amplify Video repo? https://github.com/awslabs/amplify-video
For video plugin specific issues, you might get a better response there. cc @wizage

Hi @kristian-netflix rCreateContainerLambda is a Lambda function to spin up MediaStore. Some more specific logs can be found in CloudWatch under the lambda that it spins up. My best bet is either of these:
a) Your account has to many MediaStore buckets/not proper permissions
b) The MediaStore bucket name is not unique (might need to fix from our perspective)
c) Your account is too new to spin up MediaStore (highly unlikely)

Thanks all for the help. I finally got it working. Turned out MediaStore was only supported in following regions, and not Singapore

Europe (Stockholm)
Europe (London)
Europe (Ireland)
Asia Pacific (Sydney)
Europe (Frankfurt)
Asia Pacific (Seoul)
Asia Pacific (Tokyo)
US East (N. Virginia)
US West (Oregon)

It's all running now without any errors.


add var in for loop

If exif-js is required as a module then it throws an Uncaught ReferenceError: n is not defined. Adding the proper scoping with var solves this issue.

+1 , please push hotfix to npm as soon as possible

This code merge was 1 year ago. The npm version is still out-dated and unusable.


Skip removing of non-existent field

Codecov Report

Merging #34 into master will decrease coverage by 0.26%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master    #34      +/-   ##
========================================
- Coverage   85.26%    85%   -0.27%
========================================
  Files          33     33
  Lines        2118   2120       +2
========================================
- Hits         1806   1802       -4
- Misses        312    318       +6

Impacted Files
Coverage Δ

src/lashup_kv.erl
84.72% <100%> (+0.21%)
:arrow_up:

src/lashup_hyparview_ping_handler.erl
79.71% <0%> (-5.8%)
:arrow_down:

src/lashup_hyparview_membership.erl
84.13% <0%> (-0.44%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24b1841...68c19d6. Read the comment docs.


feat(cliffy): add cliffy cli library

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.10%. Comparing base (1645d49) to head (6ad41bf).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1210   +/-   ##
=======================================
  Coverage   79.10%   79.10%
=======================================
  Files          40       40
  Lines         512      512
  Branches       84       84
=======================================
  Hits          405      405
- Misses        101      107    +6
+ Partials        6        0    -6

Flag
Coverage Δ

unittests
79.10% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix(models): more aggressive name deconflicting for inline (anonymous) models generated in the operations package

fixes #2306

Signed-off-by: Frederic BIDON<EMAIL_ADDRESS>

Also added CloudSmithAPI to CI codegen. 127 specs are now submitted to CI for full codegen & build test.


Re-enabled fingerprint validation on EC2

@akanto
reenabled fingerprint validation on AWS with new RHEL images with proper serial console setup in grub
run some smoke tests (cluster installs) on EC2, Google and Azure

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1625/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1626/


Add disabling options to README

I discovered these options in the code but noticed they weren't mentioned in the README file, so I've added them now.

I made a mistake with forking the wrong version, should be resolved now tho.

ty!


Unable to adjust mouse sensitivity using windows CP applet

Reported that since R5 you can no longer change the in-game mouse sensitivity from the Windows Control Panel applet, apparently you could do this in <= R4.  Make it so the sensitivity adjustments in the "control panel" have an effect in-game once again.
Imported from trac ticket #134,  created by Imago on 07-11-2010 at 18:09, last modified: 05-15-2012 at 20:49

Replying to [ticket:134 Imago]:

Reported that since R5 you can no longer change the in-game mouse sensitivity from the Windows Control Panel applet, apparently you could do this in <= R4.  Make it so the sensitivity adjustments in the "control panel" have an effect in-game once again.

Also noted that in order to notice any changes you need to use the Min/Max extremes of the control panel applet to notice any changes in game.
Trac comment by anonymous on 07-12-2010 at 01:18

mouse speed adjustment from control panel now has effect r733
Trac comment by Imago on 07-16-2010 at 05:26

this was removed - make up your mind people
Trac comment by Imago on 08-09-2010 at 02:54

If implemented this absolutely needs to be a toggle.
Trac comment by Spunky on 04-29-2012 at 16:14

This feature should be either controlled by the windows CP applet to allow more acceleration curves for given speed selections or implement a toggle for users to switch between using either the CP applet or the mouse control settings Imago placed in R6
Trac comment by Big_Beta_Tester on 04-15-2012 at 15:42


bash

npm ERR<EMAIL_ADDRESS>postinstall: bash build_ios_frameworks.sh
npm ERR! Exit status 1

what can i do

Have you installed  Carthage before running npm install ?

@haohcraft  I have tried npm install carthage  ,but the problem exits already.

<EMAIL_ADDRESS>postinstall E:\react native\work_place\test_ble\node_modules\react-native-ble-plx
bash build_ios_frameworks.sh

'bash' 不是内部或外部命令，也不是可运行的程序
或批处理文件。
I am in windows dev envirenment。

I also encountered this problem in windows dev envirenment。 What else do you do before you install the npm install react-native-ble-plx？

On Windows you have to have bash in system path to install this library. It is something which could be improved.

Bash is not used anymore in build process.


websocket.ts

we need to put everything into websocket.ts one way or another so everything is accessible under the package name (at the export level)

Done


Request to add updated ordering info link to readme

The uk.farnell link in your readme is a product page listing the explorer board as 'no longer stocked'. A similar link took me to a distributor called CPC which only ships to the UK.
The catalog link that did work for me (and ships to many countries, including UK and US) is:
https://www.newark.com/nxp/explore-nfc-ww/nfc-add-on-board-raspberry-pi/dp/45X6356
Thanks,
Charlie

Updated, thanks!