Tien Do

Yes, sadly that it can't be done, thanks. BTW, you have rewritten this plugin but also removed several things e.g. change event, could you add them back? you know, change...

It was not "original" plugin, I'm sorry to make you confused. I was talking about other iOS datepicker plugin, it's here and you can easily see onchange event: https://github.com/radhar/phonegap-ios-datepicker-plugin IMHO,...

It seems that `lmdbxx` is a dead repo now but it's small enough for a *hard* fork :D

Using `ncurses` to improve user interactions too, just press a single key without enter.

You can take a look at [this repo](https://github.com/sago007/PlatformFolders) for finding user data folder on operating systems, but I'd do as what @ronflima suggested.

> @tiendq Please keep in mind that `runserver` is not a production solution, it's meant for local debugging and is quite limited. You can try restarting it to see if...

> I have never seen this happen. Did you modify any part of the stack? Custom PostgreSQL configuration? Absolutely no change, just setup everything with default configuration.

Do you use anything like this `db_from_env = dj_database_url.config(conn_max_age=500)`? Some guys (not all) could fixed the issue by dropping `conn_max_age`, more detail [here](https://github.com/django/channels/issues/871#issuecomment-371592113).

I just faced this bug too after upgraded to 3.5.0 while it didn't happen with previous instance 3.3.3 Although related function (shop settings) is not critical but the error is...

I think `context.res` and `context.req` are not good names and they make people confused with `context.response` and `context.request`. Is it better if we can name them behind `NodeJS` names, so...