These are chat archives for mirumee/saleor

Aug 2018
Aug 24 2018 02:49
docker-compose build is failing with following error

(node:16) DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead
ℹ 「atl」: Using typescript@3.0.1 from typescript
ℹ 「atl」: Using tsconfig.json from /app/tsconfig.json
DEPRECATION WARNING on line 4, column 8 of stdin:
Including .css files with @import is non-standard behaviour which will be removed in future versions of LibSass.
Use a custom importer to maintain this behaviour. Check your implementations documentation on how to create a custom importer.

npm ERR! errno 137
npm ERR! saleor@0.0.0 build-assets: webpack -p
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the saleor@0.0.0 build-assets script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-08-23T17_06_52_924Z-debug.log

Aug 24 2018 05:47
I am getting following error after successful payment. Can anyone help please? @NyanKiyoshi
Filip Kucharczyk
Aug 24 2018 07:18
@Kuntal-KK You should plug some error tracking software (eg. Sentry) into your production app as we cannot tell much about what's happening, as there's nothing on the screen.
Aug 24 2018 07:24
Can somebody please help with docker compose build issue
Filip Kucharczyk
Aug 24 2018 07:25
Sorry but I don't know what's the issue, could you post a complete stacktrace on the pastebin or github gist?
Aug 24 2018 07:27
I am just running docker compose build command ...and got above issue while running 'webpack -p' command
I got this error after taking latest pull
Filip Kucharczyk
Aug 24 2018 07:32
We've merged dashboard-2.0 branch into the current master, have you reinstalled your npm packages? Some new dependencies were added.
However, can't tell anything looking at this error, first one is just a warning, not an issue.
Aug 24 2018 07:41
Ya just stuck there with warning and don't proceed
I will remove node_modules and check
Николай Инкогнито
Aug 24 2018 08:43 - don't give enter (there present dashboard 2.0?)
Filip Kucharczyk
Aug 24 2018 08:47
@mmmsvit_gitlab Thanks, we're on it
Николай Инкогнито
Aug 24 2018 08:48
i'm in, th
Aug 24 2018 09:18
@Pacu2 will do so. Thanks.
Stephen Moloney
Aug 24 2018 10:02
I have a question about what is allowed in, specifically if overriding settings previously made is allowed
consider if you write a file like this
from saleor.settings import * <- We are importing all normal settings
    if ES_URL:
        SEARCH_BACKEND = ''
            'default': {
                'hosts': ES_URL,
                'sniff_on_start': True,
                'timeout': 30}}
and then try to override one of the settings made earlier.
however, it seems that maybe this is not allowed ?
The error I am getting:
*** Operational MODE: preforking ***
Traceback (most recent call last):
  File "./saleor/wsgi/", line 21, in <module>
    application = get_wsgi_application()
  File "/usr/local/lib/python3.6/site-packages/django/core/", line 12, in get_wsgi_application
  File "/usr/local/lib/python3.6/site-packages/django/", line 24, in setup
  File "/usr/local/lib/python3.6/site-packages/django/apps/", line 93, in populate
    "duplicates: %s" % app_config.label)
django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: django_elasticsearch_dsl
or if i remove INSTALLED_APPS.append('django_elasticsearch_dsl') - is that sufficient for it to work ?
I'll try that first anyways.
Stephen Moloney
Aug 24 2018 10:59
removing INSTALLED_APPS.append('django_elasticsearch_dsl') did the trick