Empty html for projects/ page at startup

When startup up label-studio I am directed to the projects page on the local host. Unfortunately this just brings me to an empty HTML page.
This is the output to the terminal:
$ label-studio
Data base and media directory:  C:\Users\bbarbieri\AppData\Local\label-studio\label-studio
Start browser at URL: http://localhost:8080
Performing system checks...

System check identified no issues (0 silenced).
March 17, 2021 - 09:51:52
Django version 3.1.4, using settings 'label_studio.core.settings.label_studio'
Starting development server at http://<IP_ADDRESS>:8080/
Quit the server with CTRL-BREAK.
[17/Mar/2021 09:51:55] "GET / HTTP/1.1" 302 0
[17/Mar/2021 09:51:55] "GET /projects/ HTTP/1.1" 200 2270
[17/Mar/2021 09:51:55] "GET /static/fonts/roboto/roboto.6ffe390dd5ff.css HTTP/1.1" 200 4451
[17/Mar/2021 09:51:55] "GET /static/css/uikit.e49a7a43adbd.css HTTP/1.1" 200 3892
[17/Mar/2021 09:51:55] "GET /static/css/main.3b36b24fbb6f.css HTTP/1.1" 200 15457
[17/Mar/2021 09:51:55] "GET /react-app/main.css?v=1eac65 HTTP/1.1" 200 121279
[17/Mar/2021 09:51:55] "GET /static/js/jquery.min.220afd743d9e.js HTTP/1.1" 200 88145
[17/Mar/2021 09:51:55] "GET /static/js/helpers.9a01b074ff58.js HTTP/1.1" 200 13336
[17/Mar/2021 09:51:55] "GET /react-app/index.js?v=1eac65 HTTP/1.1"<PHONE_NUMBER>
[17/Mar/2021 09:51:58] "GET /static/fonts/roboto/roboto-v20-latin_cyrillic-regular.9af3b948743a.woff2 HTTP/1.1" 200 22428
[17/Mar/2021 09:51:59] "GET /react-app/main.css.map HTTP/1.1" 200 133214

@brianbarbieri Could you please show a screenshot with the browser console?

Are you trying to run it on localhost domain? What address for LS instance is in the browser?

@brianbarbieri Could you please show a screenshot with the browser console?

Are you trying to run it on localhost domain? What address for LS instance is in the browser?

It's running on the http://localhost:8080/, what do you mean by LS domain?

@brianbarbieri Yes, I mean the thing you mentioned.

Are you using LS from repository or from pip package?

From

Are you using LS from repository or from pip packages?

From the pip packages in an fresh conda environment.
$ pip list
appdirs                  1.4.3
asgiref                  3.3.1
attr                     0.3.1
attrs                    20.3.0
azure-core               1.12.0
azure-storage-blob       12.8.0
boto                     2.49.0
boto3                    1.16.28
botocore                 1.19.28
boxing                   0.1.4
cachetools               4.2.1
certifi                  2020.12.5
cffi                     1.14.5
chardet                  4.0.0
click                    7.1.2
colorama                 0.4.4
coreapi                  2.3.3
coreschema               0.0.4
cryptography             3.4.6
Django                   3.1.4
django-annoying          0.10.6
django-cors-headers      3.6.0
django-debug-toolbar     3.2
django-extensions        3.1.0
django-filter            2.4.0
django-model-utils       4.1.1
django-redis-cache       3.0.0
django-rest-swagger      2.2.0
django-rq                2.3.2
django-user-agents       0.4.0
djangorestframework      3.12.2
drf-dynamic-fields       0.3.0
drf-generators           0.3.0
drf-yasg                 1.20.0
google-api-core          1.26.1
google-auth              1.28.0
google-cloud-core        1.6.0
google-cloud-storage     1.28.1
google-resumable-media   0.5.1
googleapis-common-protos 1.53.0
htmlmin                  0.1.12
idna                     2.10
inflection               0.5.1
isodate                  0.6.0
itypes                   1.2.0
Jinja2                   2.11.3
jmespath                 0.10.0
joblib                   1.0.1
jsonschema               3.2.0
label-studio             1.0.0
label-studio-converter   0.0.25
lockfile                 0.12.2
lxml                     4.6.2
MarkupSafe               1.1.1
mock                     4.0.3
more-itertools           8.7.0
moto                     1.3.16.dev122
msrest                   0.6.21
nltk                     3.5
numpy                    1.20.1
oauthlib                 3.1.0
openapi-codec            1.3.2
ordered-set              4.0.2
packaging                20.9
pandas                   1.2.3
Pillow                   7.2.0
pip                      21.0.1
protobuf                 3.15.6
psycopg2-binary          2.8.4
pyasn1                   0.4.8
pyasn1-modules           0.2.8
pycparser                2.20
pydantic                 1.7.3
pyparsing                2.4.7
pyrsistent               0.17.3
python-dateutil          2.8.1
pytz                     2019.3
PyYAML                   5.4.1
redis                    3.5.3
regex                    2020.11.13
requests                 2.25.1
requests-oauthlib        1.3.0
responses                0.13.0
rq                       1.7.0
rsa                      4.7.2
ruamel.yaml              0.16.13
ruamel.yaml.clib         0.2.2
rules                    2.2
s3transfer               0.3.4
setuptools               52.0.0.post20210125
simplejson               3.17.2
six                      1.15.0
sqlparse                 0.4.1
tqdm                     4.59.0
ua-parser                0.10.0
ujson                    4.0.2
uritemplate              3.0.1
urllib3                  1.26.4
user-agents              2.2.0
Werkzeug                 1.0.1
wheel                    0.36.2
wincertstore             0.2
xmljson                  0.2.0
xmltodict                0.12.0
zipp                     3.4.1

@brianbarbieri Could you please:

right click the broken link in the browser console
open in new tab
send a screenshot of this page

Thank you in advance!

@brianbarbieri Could you please:

right click the broken link in the browser console
open in new tab
send a screenshot of this page

Thank you in advance!

and

No thank you for helping me out.

It looks like you are using DEBUG=False with git cloned repo..
Please, try this:
DEBUG=True label-studio

DEBUG=True label-studio

Doing this yields same blank html with this in the console:

@brianbarbieri And what if you open /react-app/index.js?.... in a new tab?

@brianbarbieri And what if you open /react-app/index.js?.... in a new tab?

Finding the dir and the file:

What browser do you use and what version is it?
Could you try to use another browser?

@brianbarbieri
What browser do you use and what version is it?
Could you try to use another browser?

I'm using chrome, but I get the same behavior on MS edge

Yep! Got it on Edge. In chrome browser it works fine for me.

It's chrome  89.0.4389.82 . I think everything will be ok if you update it.

Could you send your chrome browser version?

It's chrome 89.0.4389.82 . I think everything will be ok if you update it.

Fully up to date, does still not work :/

@brianbarbieri Don't you use nginx over label studio? Or something like this.. Because I can reproduce it on Edge and there is another error (I have very old Edge version).

I did the exact same things on my personal laptop and I'm facing no issues at all/

I'm getting the same error along with the following console messages

@sam-fisco are you on windows?

@brianbarbieri is your personal laptop on windows?

@sam-fisco are you on windows?

Yes I am

@brianbarbieri is it your personal laptop on windows?

Yes both systems are on windows, I will asl a colleague tomorrow to install the tool aswell to see if the work laptop is the problem.

I had same problem with arg host is set to "<IP_ADDRESS>" and solved by remove it. If you also define host, you may try.
Remove --host "<IP_ADDRESS>" like this one:
label-studio start weblabel -b --host "<IP_ADDRESS>" --port 8080
Into this:
label-studio start weblabel -b --port 8080

@trhgnhat Thank you for your solution!
Could you explain more please: where did you get this command label-studio start weblabel -b --host "<IP_ADDRESS>" --port 8080 with host "<IP_ADDRESS>" ?..

@makseq got randomly on the internet for long time and don't know why. Just removed it yesterday since i got this error.

Solved by the setting the correct Windows registry for JavaScript files.

@brianbarbieri Thank you very much for the provided solution!
@sam-fisco Could you check @brianbarbieri solution?

Hi
I ran into a similar issue, turns out in my case it was being caused by the pip release label-studio-1.0.0.post0 which after startup and logging in the projects page was empty but in my browser console i found:
GET http://X.X.X.X:8080/projects/x86_64-conda_cos6-linux-gnu/react-app/index.js?v=60ba41 net::ERR_ABORTED 404 (Not Found)
IP removed for privacy. Clearly the path looks a bit odd and i was checking for existing issues and found this one.  I noticed the package list above showed 1.0.0 so i rolled back to that and it works ok, so seems this one is related to the latest post0 release.
Thanks
Tony

@antonyscerri Thank you very much for your report.
Could you please show your HOST env variables?
echo $HOST
echo $LABEL_STUDIO_HOST

@antonyscerri I think it's releated to https://github.com/conda/conda/issues/7031
If you set HOST="" then the issue will be fixed.
HOST="" label-studio start

Hi
Yes that appears to be the case, so i can run the latest version now. Its only impacting the 1.0.0.post0 release though, it has no impact on 1.0.0. The values were:
echo $HOST
x86_64-conda_cos6-linux-gnu
echo $LABEL_STUDIO_HOST

We fixed it in 1.0.0.post1 (without changing Windows registry).

@makseq I am getting this same behavior on an aws ec2 w/ an ubuntu 18.04 deep learning base ami using v 1.0.0.post2. My chrome version is Version 89.0.4389.90 (Official Build) (x86_64). The console output from the login page is pasted below:

Additionally, chrome generated some issue messages which I am pasting below.

@EconML Could you send a screenshot with the browser console where I can see an exact error with MIME?

@makseq thx for the reply, here it is. I blocked out the private ip for privacy

Additionallly, if this is helpful after logging on and navigating to a test project i get the following in the console

@EconML

Do you use LS as pip package?
What is your start LS command?
Have you set up HOST=... ?

BTW I tried 1.0.0.post2 to check on some fixes but the UI didnt render properly. The animating logo player on the top left and then menu items were displayed down the left side of the page. It looked like a CSS problem but there didn't seem to be an obvious CSS resource missing/broken. I had to downgrade to continue testing something, i was using the same HOST="" to launch.

@antonyscerri @EconML could you check 1.0.0.post3?

@makseq apologies for lack of response.  When I have a chance I will check 1.0.0.post3.

I just happened to see post3 was available and then your note. I was able to install and launch it (using HOST="") and i can pull up the homepage, and project page.  However I reloaded the homepage again to try a fresh view. When i clicked on the title of the project and got to this url - http://x.x.x.x:8080/projects/1/data (ip redacted) then it appeared to get stuck again, the top nav bar shows but the rest of the page is blank. Browser debug console doesnt show anything useful, the last line seems to be an object being output from DataManager.js:100.  I am still getting the same 404 errors and MIME type check errors. Here is console output w/ post3

@makseq I pulled down post3 and I am still getting the 404 and MIME type errors. Console output is below. Additionally, since I'm not on my mac, I'm using firefox and getting the exact same behavior.

@makseq It looks to be more consistently failing if i reload the page when on the data tab view, where as going to projects and clicking on the project seems to display the page. The only thing in debug console is a mention "Breadcrumbs must be initialized first" coming from breadrumbs.js:9, which is what happens on both pages when refreshed, on the project data view though it occurs after the first call to DataManager.js:100, which doesnt happen when you start on the project page as its already been intialised. I can see the call to the api to retrieve the project details but there is no further calls to get the columns etc which seem to originate from the data manager.

@EconML are you running Label Studio locally or on a remote machine compared to where the browser is located? And are you running it behind any web server (nginx etc) or other proxy or ELB (you mentioned AWS). And what launch command are you now using?

@EconML it looks like you are still using 1.0.0.post2 instead of 1.0.0.post3..

@antonyscerri I am running label studio on a remote ec2. I have setup traffic rules so that port 8080 is opened to me when I am on my company vpn. I am not running and ELB on this instance. Full disclosure, I had previously been using ls v0.8.0 for my annotation jobs without any issue. I actually just rolled back to 0.8.0 because my actual goal is to plugin the ml backend and these issues were blocking.

@makseq I could have sworn I verified with pip list after installing with setup.py. Maybe I copied the wrong .png. Let me doublecheck..

Check label-studio version, it must be the same:
Label Studio version: 1.0.0.post3

{
    "package": {
        "version": "1.0.0.post3",
        "short_version": "1.0",
        "latest_version_from_pypi": "1.0.0.post3",
        "latest_version_upload_time": "2021-03-22T13:00:56",
        "current_version_is_outdated": false
    },
    "backend": {
        "message": "Fix manifest for dm",
        "commit": "5e2883013290dc6c93f40c2d473bb845e8744c4a",
        "date": "2021-03-22 15:41:55 +0300",
        "branch": "master",
        "version": "1.0.0+55.g5e288301"
    },
    "label-studio-frontend": {
        "message": "Fix brushes to always get the current stage",
        "commit": "099282da1bab181f02c92107af1a260481f16d32",
        "branch": "master",
        "date": "2021-03-19T16:20:46Z"
    },
    "dm2": {
        "message": "Build for UMD",
        "commit": "4966e206259ce8c5d43ff82c2d0ed6bfa5f712e6",
        "branch": "master",
        "date": "2021-03-19T13:25:47Z"
    }
}

@makseq it seems you were right! After pulling down post3, verifying, and starting ls I am no longer having the 404 and MIME type. However, my tasks won't sync, getting 500 (this is a different issue obviously).

@makseq Is there anything you need that would help debug @antonyscerri continued issues?

For now i may stick with post0 as it let's me try most of what I wanted to explore with the basic UI pieces. I was trying some of the ML pieces but things seem to be in flux right now and the examples, ML backend and various documents don't appear to match exactly so i may wait till thing stabilise.

@antonyscerri Do you mean that post0 is working?
@nicholasrq Could you make a diff between post0 and post3?

@makseq I know this is unrelated but since we're already on the thread can you point in the direction of some resources/tutorials for custom/dummy model ml backend on v0.8.0? Otherwise i can post new issue/slack.

@makseq post0 is fine as long as i launch with HOST="" i can reload pages and have been working through testing out various workflow ideas and not run into an issue. post2 looked like the css just wasnt working and post3 has the issue reloading the project data page.

@EconML It's better to have such a question on slack.
Check this: https://labelstud.io/tutorials/dummy_model.html


refactor: Use new Qdrant client

Description
Updates the Qdrant integration to use the new https://github.com/qdrant/go-client SDK.
Resolves #1006

@Anush008 can you address the lint issue?

Done.

Hey @tmc. Just bumping this PR.


Allow users to specify initial_states for recurrent layers

Specifying the initial hidden state of a recurrent layer is necessary for sequence to sequence models, and probably for other architectures as well.

@fchollet it would be very helpful if one can init the hidden states of rnn, there are a lot of NLP models (machine translation, text generation) use the sequence to sequence model, which is mentioned by @lobachevzky . Basically it's an encoder-decoder model, we need the hidden states of encoder to be the init states of decoder :)

Is this PR going to be fixed or will the development of the feature be continued in #3947 ?

Closing outdated PR. If you still care about the content of the PR, please submit a new PR to master, updated for the Keras 2.0 API.


inconsistent resources order returned by get-pipeline command

fly version: 3.14.1
There will always be at least one team pipeline whose config when returned by fly get-pipeline command will have varying order of its resources. For example, first run of fly get-pipeline -p mypipeline returns:
...
resources:
- name: a
  type: git
- name: b
  type: docker-image
- name: c
  type: git
...

The next run may return:
...
resources:
- name: c
  type: git
- name: a
  type: git
- name: b
  type: docker-image
...

Affects concourse-pipeline-resource check command (concourse/concourse-pipeline-resource#38)

I have this same issue. Verified with script that collects all pipelines between 10minutes. After diffing directories, I can confirm that definitions differ randomly.

Verified issue can be reproduced on concourse v4.2.1


How to Enable Custom Meeting UI for  flutter_zoom_plugin

How to Enable Custom Meeting UI for  flutter_zoom_plugin? ...Is it possible? if possible can you tell me here step be stepl ...Thank you

@ramsubramani no its not possible, you would need to modify the underlying zoom sdk assets directly. We are working on a command line to install the zoom sdk from a custom location. So that will help your usecase.

Hi @kevinbayes , I am sorry if my question is not clear. Let me put it straight here, can we resize the zoom meeting screen layout (From full screen to half screen)? does zoom sdk support this for flutter?


Update Linux tests to work on GitHub

What does this PR do?
Update Linux tests to work on GitHub
What issues does this PR fix or reference?
Fixes: https://github.com/saltstack/salt-vmtools/issues/3
New Behavior
Running improvements to get testing working with GitHub actions for Linux after migration from GitLab

Merging this to get changes in before attempting to add Linux packages for 3006.8, 3006.9 and 3007.1


Update UploadHandler.php

the options presented in the form of a multidimensional array of arrays, and simple addition leads to loss of default settings such as thumbnails

Thanks for your contribution.
Like I said in your previous pull request (#3409):
This behaviour is by design, as else you wouldn't be able to disable settings in nested arrays


On ARM build, getting error -> node: can't resolve symbol 'backtrace'

This is using openwrt arm linux. I added the compile flag -ggdb3 because I thought that might work, but it didn't.

@ralphtheninja if you have a minute and are still openwrt (ing) would you mind doing a quick npm install segfault-handler to get some output.

@No9 Not sure how to reproduce this and what the environment looks like. All I have is openwrt running on a router. I don't have node installed on that one.

Thanks @ralphtheninja just thought I would ask.

Thanks @ralphtheninja just thought I would ask.

:+1:


s3_backup: add namespace into storage path

fix https://github.com/coreos/etcd-operator/issues/946

@xiang90 @hasbro17

After second thought, this breaks backward compatibility.
I'm closing this. We need more work to maintain backward compatibility.


Automate translations of fields value

The idea is to find a way to not oblige users to add both french and english values to a field when they fill the form. They would instead only have to fill the form in their current language (english OR french). We'd still give them the option to do both if they're familiar with both languages. However, if it could be great if we could find a solution for creating an automatic translation when it's not the case.

I'm not sure about any requirements for this solution, either being open-source and/or being free?

From my preliminary research, what I found wasn't really conclusive. Most open source solutions seems to be only free up to a certain amount of character translated.

@smellems @imadeDev @BassamAjam @j-rewerts Any thoughts?

Some of the solution I found:

Google Translate Api
Microsoft Translator Text API
Yandex translator
Serge.io
Systran

But none of them seems to meet our requirements

I imagine we keep both fields (en-fr) but have a button to do an automatic translation to the other language.
We could use Termium if it have an API.  I think that's what GCconnex is using.
https://www.btb.termiumplus.gc.ca/tpv2alpha/alpha-eng.html

Possibly related: we set up automated translated for open data metadata that was federated from the Alberta open data portal using deepl.com. Internally and via API all our language metadata is tagged with BCP-47 labels so we used its extension to indicate "translated fields" i.e. fr-t-en for French text machine translated from English vs. fr for original French text.
On the web site we indicate these translations with little icons on the titles, descriptions and keywords, e.g. https://ouvert.canada.ca/data/fr/dataset/18801116-2014-43df-84fd-408bc2382051

@wardi I've look at the API and it would seem like a solution we could adopt. However, I'd like to know if there's already a setup for the API for Canada or do you only have your personal/Alberta setup?

Do you mean the deepl API? We use a few simple scripts https://github.com/open-data/ckanext-canada/tree/master/bin/harvest

I guess my question is could we use it for our project to automatically translate fields after a user submit a form?


L7 policy is not enforced after a L4 connection is made

To replicate follow the instructions in http://cilium.readthedocs.io/en/latest/gettingstarted/minikube/
On http://cilium.readthedocs.io/en/latest/gettingstarted/minikube/#step-4-apply-an-l3-l4-policy the L7 policy is not enforced.
The L7 policy enforcement works if the l3_l4_l7 policy is deleted and then created.
Reported-by: @JrCs

Since this PR was merged, the e2e test needs to be revisited https://github.com/cilium/cilium/pull/4152

I attempted this using Cilium v1.0.3 and did not observe the issue:
$ k8s-cilium-exec.sh cilium version
Unable to use a TTY - input is not a terminal or the right kind of file
Client: 1.0.3 a2ebe00a5 2018-05-16T19:13:52+00:00 go version go1.9 linux/amd64
Daemon: 1.0.3 a2ebe00a5 2018-05-16T19:13:52+00:00 go version go1.9 linux/amd64

$ kubectl get pods
kubNAME                          READY     STATUS    RESTARTS   AGE
deathstar-76995f4687-6bgtw    1/1       Running   0          1m
deathstar-76995f4687-xzsw9    1/1       Running   0          1m
etcd-cilium-0                 1/1       Running   2          3d
tiefighter-68c6cb4b4b-zz8mx   1/1       Running   0          1m
xwing-cc65988f5-bn8cj         1/1       Running   0          1m

$ kubectl exec xwing-cc65988f5-bn8cj -- curl -s -XPOST deathstar.default.svc.cluster.local/v1/request-landing
^C

$ k8s-cilium-exec cilium policy get
Unable to use a TTY - input is not a terminal or the right kind of file
[
  {
    "endpointSelector": {
      "matchLabels": {
        "any:class": "deathstar",
        "any:org": "empire",
        "k8s:io.kubernetes.pod.namespace": "default"
      }
    },
    "ingress": [
      {
        "fromEndpoints": [
          {
            "matchLabels": {
              "any:org": "empire",
              "k8s:io.kubernetes.pod.namespace": "default"
            }
          }
        ],
        "toPorts": [
          {
            "ports": [
              {
                "port": "80",
                "protocol": "TCP"
              }
            ]
          }
        ]
      }
    ],
    "labels": [
      {
        "key": "io.cilium.k8s.policy.name",
        "value": "rule1",
        "source": "unspec"
      },
      {
        "key": "io.cilium.k8s.policy.namespace",
        "value": "default",
        "source": "unspec"
      }
    ]
  }
]
Revision: 7

$ kubectl get cnp rule1 -o yaml
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  clusterName: ""
  creationTimestamp: 2018-05-18T17:24:12Z
  generation: 0
  name: rule1
  namespace: default
  resourceVersion: "16584"
  selfLink: /apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/rule1
  uid: 48349465-5ac0-11e8-9206-080027a0bf67
spec:
  endpointSelector:
    matchLabels:
      any:class: deathstar
      any:org: empire
  ingress:
  - fromEndpoints:
    - matchLabels:
        any:org: empire
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
status:
  nodes:
    minikube:
      enforcing: true
      lastUpdated: 2018-05-18T17:32:24.899495028Z
      localPolicyRevision: 2
      ok: true

$ TIEFIGHTER=$(kubectl get pod | grep tie | sed 's/^\([^ ]*\).*/\1/g')
$ kubectl exec $TIEFIGHTER -- curl -s -XPUT deathstar.default.svc.cluster.local/v1/exhaust-port
Panic: deathstar exploded

goroutine 1 [running]:
main.HandleGarbage(0x2080c3f50, 0x2, 0x4, 0x425c0, 0x5, 0xa)
        /code/src/github.com/empire/deathstar/
        temp/main.go:9 +0x64
main.main()
        /code/src/github.com/empire/deathstar/
        temp/main.go:5 +0x85

$ kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/HEAD/examples/minikube/sw_l3_l4_l7_policy.yaml
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
ciliumnetworkpolicy.cilium.io "rule1" configured

kind: CiliumNetworkPolicy
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"cilium.io/v2","description":"L7 policy to restrict access to specific HTTP call","kind":"CiliumNetworkPolicy","metadata":{"annotations":{},"name":"rule1","namespace":"default"},"spec":{"endpointSelector":{"matchLabels":{"class":"deathstar","org":"empire"}},"ingress":[{"fromEndpoints":[{"matchLabels":{"org":"empire"}}],"toPorts":[{"ports":[{"port":"80","protocol":"TCP"}],"rules":{"http":[{"method":"POST","path":"/v1/request-landing"}]}}]}]}}
  clusterName: ""
  creationTimestamp: 2018-05-18T17:24:12Z
  generation: 0
  name: rule1
  namespace: default
  resourceVersion: "17233"
  selfLink: /apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/rule1
  uid: 48349465-5ac0-11e8-9206-080027a0bf67
spec:
  endpointSelector:
    matchLabels:
      any:class: deathstar
      any:org: empire
  ingress:
  - fromEndpoints:
    - matchLabels:
        any:org: empire
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
      rules:
        http:
        - method: POST
          path: /v1/request-landing
status:
  nodes:
    minikube:
      enforcing: true
      lastUpdated: 2018-05-18T17:41:46.513668378Z
      localPolicyRevision: 9
      ok: true

$ k8s-cilium-exec cilium policy get
Unable to use a TTY - input is not a terminal or the right kind of file
[
  {
    "endpointSelector": {
      "matchLabels": {
        "any:class": "deathstar",
        "any:org": "empire",
        "k8s:io.kubernetes.pod.namespace": "default"
      }
    },
    "ingress": [
      {
        "fromEndpoints": [
          {
            "matchLabels": {
              "any:org": "empire",
              "k8s:io.kubernetes.pod.namespace": "default"
            }
          }
        ],
        "toPorts": [
          {
            "ports": [
              {
                "port": "80",
                "protocol": "TCP"
              }
            ],
            "rules": {
              "http": [
                {
                  "path": "/v1/request-landing",
                  "method": "POST"
                }
              ]
            }
          }
        ]
      }
    ],
    "labels": [
      {
        "key": "io.cilium.k8s.policy.name",
        "value": "rule1",
        "source": "unspec"
      },
      {
        "key": "io.cilium.k8s.policy.namespace",
        "value": "default",
        "source": "unspec"
      }
    ]
  }
]
Revision: 9

$ kubectl exec $TIEFIGHTER -- curl -s -XPUT deathstar.default.svc.cluster.local/v1/exhaust-port
Access denied

$ kubectl exec $TIEFIGHTER -- curl -s -XPOST deathstar.default.svc.cluster.local/v1/request-landing
Ship landed

Reproduced with latest tag.

$ k8s-cilium-exec cilium endpoint log 173
Unable to use a TTY - input is not a terminal or the right kind of file
Timestamp              Status    State                   Message
2018-05-18T17:56:49Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:54:48Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:54:48Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:53:08Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:52:49Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:51:49Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:51:44Z   OK        ready                   Endpoint policy update skipped because no changes were needed
2018-05-18T17:51:42Z   OK        ready                   Successfully regenerated endpoint program due to syncing state to host
2018-05-18T17:51:42Z   OK        ready                   Completed endpoint regeneration with no pending regeneration requests
2018-05-18T17:51:40Z   Warning   regenerating            Unable to open CT map /sys/fs/bpf/tc/globals/cilium_ct4_global: Unable to get object /sys/fs/bpf/tc/globals/cilium_ct4_global: no such file or directory
2018-05-18T17:51:40Z   Warning   regenerating            Unable to open CT map /sys/fs/bpf/tc/globals/cilium_ct6_global: Unable to get object /sys/fs/bpf/tc/globals/cilium_ct6_global: no such file or directory
2018-05-18T17:51:40Z   OK        regenerating            Regenerating Endpoint BPF: syncing state to host
2018-05-18T17:51:40Z   OK        waiting-to-regenerate   Triggering synchronous endpoint regeneration while syncing state to host
2018-05-18T17:51:40Z   OK        restoring               Synchronizing endpoint labels with KVStore
2018-05-18T17:51:40Z   OK        restoring               Restoring endpoint from previous cilium instance

This is the entirety of the Cilium logs for the period when the kubectl apply put the L7 policy in place:
2018-05-18T17:54:48.58355308Z level=info msg="Deleted CiliumNetworkPolicy" ciliumNetworkPolicyName=rule1 k8sApiVersion= k8sNamespace=default
2018-05-18T17:54:48.583604414Z level=info msg="Policy imported via API, recalculating..." policyRevision=10
2018-05-18T17:54:48.583613554Z level=info msg="Imported CiliumNetworkPolicy" ciliumNetworkPolicyName=rule1 k8sApiVersion= k8sNamespace=default


TypeError: Data must be a string or a buffer

Using the latest 2.2.0 release, although the error was on rc.4 before I updated too.
crypto.js:73
  this._handle.update(data, encoding);
               ^

TypeError: Data must be a string or a buffer
    at TypeError (native)
    at Hash.update (crypto.js:73:16)
    at HarmonyExportImportedSpecifierDependency.updateHash (/Users/kuchumovn/work/webapp/frontend/node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js:144:8)
    at /Users/kuchumovn/work/webapp/frontend/node_modules/webpack/lib/DependenciesBlock.js:33:5
    at Array.forEach (native)
    at NormalModule.DependenciesBlock.updateHash (/Users/kuchumovn/work/webapp/frontend/node_modules/webpack/lib/DependenciesBlock.js:32:20)
    at NormalModule.Module.updateHash (/Users/kuchumovn/work/webapp/frontend/node_modules/webpack/lib/Module.js:162:41)
    at NormalModule.updateHash (/Users/kuchumovn/work/webapp/frontend/node_modules/webpack/lib/NormalModule.js:327:30)
    at modules.forEach.m (/Users/kuchumovn/work/webapp/frontend/node_modules/webpack/lib/Chunk.js:253:31)
    at Array.forEach (native)

I supposse it's computing a hash for a file, and a file is empty (?) or non-existent or something like that.
Anyway no clue on the real error in this error message.

the same error with me.

Can you provide a small project showing the error? The issue could be debugged that way.

@bebraw
https://github.com/rguanghui/webpack-updatehash-error
this is the project to debug. hope useful :)

node version: 6.0.0
system: mac OS Sierra 10.12.2

by the way, this error comes after i update my system ( from 10.12.1 to 10.12.2 )

Looks like this is a null issue. That's why it errors like that. I wonder if it should fail earlier, though.
I did the following change:
diff --git a/src/shopview/index.js b/src/shopview/index.js
index 505c1b1..f9c5046 100644
--- a/src/shopview/index.js
+++ b/src/shopview/index.js
@@ -3,5 +3,5 @@ import ShopRate from './shopinfo/shoprate'
 // import ShopInfo from './shopinfo/shopinfo'
 // import ShopHeader from './shopheader/shopheader'

-export { ShopHeader, ShopRate, ShopInfo, ShopView }
+//export { ShopRate, ShopView }
 export default ShopView

This made the error disappear (gives another error, but that's perhaps expected). That earlier export referred to code that doesn't exist so that might explain those nulls. I'm guessing webpack needs to be stricter in this case.

In my case it was this line:
export { default as navigator }      from './navigator'

I deleted the ./navigator file but apparently webpack doesn't check if the file exists, then reads it, gets null or undefined, then feeds the crypto hash generator with this non-existent value and then explodes.

Yup. It's missing a check. Or even if it skips an explicit check, it should fail in a way that allows the user to fix the problem.

It should do a check for dep.module and emit a webpack missing module error code. Somebody wants to do a PR? See other Dependencies for example i. e. CommonJsRequireDependency

@bebraw @sokra Got the same error today:

webpack version: 2.2.0
webpack-dev-server version: 2.2.0

Hi, I was looking into this to see if I could submit a PR, but I wanted to verify this current dep.module check in the HarmonyImportDependency.js could I emit an error module code from here?  	if(!dep.module) { 		const stringifiedError = JSON.stringify(`Cannot find module "${dep.request}"`); 		return `throw new Error(${stringifiedError});${newline}`; 	}

I got the same error after making a bunch of changes to the code and now it's very hard to pinpoint exactly what change is causing the issue. Is there any way to know what file/module is making trouble?

Anyone else having this issue while transpiling from Typescript to Babel to ES5?
I believe I resolved the issue by changing jsx from preserve to react in my tsconfig.json:

I had the same problem. Upgrading node from 6.9.4 to 7.4.0 solved the problem for me.

Just hit the same problem here. Upgrading to Node 7.4.0 did not resolve the issue for me.

Same problem.

Darwin 16.4.0 (Sierra 10.2.3)
node v7.5.0
npm  v4.1.2

I get that problem when I try to import not existing class from file, for example
import { ManageUsersService, UserPermissionsService } from './services';
when UserPermissionsService does not exist.
I get it, its a problem with code, but I would appreciate better error message instead of:
86% hashingTypeError: Data must be a string or a buffer     at Hash.update (crypto.js:74:16)     at HarmonyExportImportedSpecifierDependency.updateHash .../node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js:144:8)     at .../node_modules/webpack/lib/DependenciesBlock.js:33:5     at Array.forEach (native)

The problems occurs when trying to export a file not present on the disk.
While import error show a clear error message:
import { MissingFile } from './MissingFile';

ERROR in /app/src/app/components/somecomponent/index.ts (6,29): Cannot find module './MissingFile'.)
webpack: Failed to compile.

The error during export does not help :
export { MissingFile } from './MissingFile';

webpack: Compiling...
 86% hashingcrypto.js:74
  this._handle.update(data, encoding);
               ^

TypeError: Data must be a string or a buffer
    at TypeError (native)
    at Hash.update (crypto.js:74:16)
    at HarmonyExportImportedSpecifierDependency.updateHash (/app/node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js:144:8)
    at /app/node_modules/webpack/lib/DependenciesBlock.js:33:5
    at Array.forEach (native)
    at NormalModule.DependenciesBlock.updateHash (/app/node_modules/webpack/lib/DependenciesBlock.js:32:20)
    at NormalModule.Module.updateHash (/app/node_modules/webpack/lib/Module.js:162:41)
    at NormalModule.updateHash (/app/node_modules/webpack/lib/NormalModule.js:327:30)
    at modules.forEach.m (/app/node_modules/webpack/lib/Chunk.js:253:31)
    at Array.forEach (native)
    at Chunk.updateHash (/app/node_modules/webpack/lib/Chunk.js:253:16)
    at Compilation.createHash (/app/node_modules/webpack/lib/Compilation.js:989:10)
    at sealPart2 (/app/node_modules/webpack/lib/Compilation.js:580:9)
    at next (/app/node_modules/tapable/lib/Tapable.js:138:11)
    at Compilation.<anonymous> (/app/node_modules/webpack/lib/ProgressPlugin.js:110:5)
    at next (/app/node_modules/tapable/lib/Tapable.js:140:14)
    at ExtractTextPlugin.<anonymous> (/app/node_modules/extract-text-webpack-plugin/index.js:297:5)
    at /app/node_modules/async/dist/async.js:356:16
    at iteratorCallback (/app/node_modules/async/dist/async.js:936:13)
    at /app/node_modules/async/dist/async.js:840:16
    at /app/node_modules/extract-text-webpack-plugin/index.js:281:6
    at /app/node_modules/async/dist/async.js:356:16
    at iteratorCallback (/app/node_modules/async/dist/async.js:936:13)
    at /app/node_modules/async/dist/async.js:840:16
    at /app/node_modules/extract-text-webpack-plugin/index.js:278:13
    at /app/node_modules/async/dist/async.js:3025:16
    at eachOfArrayLike (/app/node_modules/async/dist/async.js:941:9)
    at eachOf (/app/node_modules/async/dist/async.js:991:5)
    at Object.eachLimit (/app/node_modules/async/dist/async.js:3089:3)
    at /app/node_modules/extract-text-webpack-plugin/index.js:252:11
    at /app/node_modules/async/dist/async.js:3025:16
    at eachOfArrayLike (/app/node_modules/async/dist/async.js:941:9)
    at eachOf (/app/node_modules/async/dist/async.js:991:5)
    at Object.eachLimit (/app/node_modules/async/dist/async.js:3089:3)
    at ExtractTextPlugin.<anonymous> (/app/node_modules/extract-text-webpack-plugin/index.js:249:10)
    at Compilation.applyPluginsAsyncSeries (/app/node_modules/tapable/lib/Tapable.js:142:13)
    at Compilation.seal (/app/node_modules/webpack/lib/Compilation.js:545:8)
    at /app/node_modules/webpack/lib/Compiler.js:474:16
    at /app/node_modules/tapable/lib/Tapable.js:225:11
    at _addModuleChain (/app/node_modules/webpack/lib/Compilation.js:452:11)
    at processModuleDependencies.err (/app/node_modules/webpack/lib/Compilation.js:423:13)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Do we have a resolution on this issue? I'm getting the same error and I gave no idea what export statement(s) are causing this problem.

We have also the same error!!! With Version 2 from Webpack we have only problems!

Another case to watch out for is if you override resolve.extensions to not include .js (because I don't have any javascript!) and are importing an es2015 module supporting package from node_modules, like react-redux.

I had the same issue because of
export { default } from 'Progress';
export { default as ProgressBar } from 'ProgressBar';

instead of
export { default } from './Progress';
export { default as ProgressBar } from './ProgressBar';

I think the error wasn't very clear but your comments help me.

Here is a workaround to help you to find the wrong import.
Let's say you have some wrong import somewhere in your code:
export { Some } from './missing-file';

You can improve the error message by manually editing the following file: node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js and insert some log at line 144:
   updateHash(hash) {
      super.updateHash(hash);
      const hashValue = this.getHashValue(this.importDependency.module);

      if (this.importDependency.module != null){
         // console.log('Module resource: ', this.importDependency.module.resource);
      }else{
         console.log('\nFile not found: ', this.importDependency);
      }

      hash.update(hashValue);
   }

So you get this more explicit message:
 86% hashing
File not found:  HarmonyImportDependency {
  module: null,
  request: './missing-file',
  userRequest: './missing-file',
  range: [ 562, 600 ],
  importedVar: '__WEBPACK_IMPORTED_MODULE_8__missing_file__',
  loc: SourceLocation { index: -1 } }
crypto.js:74
  this._handle.update(data, encoding);
               ^

TypeError: Data must be a string or a buffer
    at TypeError (native)
    at Hash.update (crypto.js:74:16)
    at HarmonyExportImportedSpecifierDependency.updateHash (/app/node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js:149:6)

Finally, search for './missing-file' string in your project to find which file contains the wrong import.

Thx @Toub - saved me!

For me is fail to configure resolve.extensions  cause this error. Add the missing .vue extensions solve the problem. FYI:
resolve: {
  extensions: ['...', '.vue']
}

Thx @Toub you help figure this out!

For me, I was trying to use postcss-loader but didn't declare it in package.json. When node_modules was deleted and recreated, @Toub's answer helped me discover that a CSS file wasn't being loaded. I tried adding transform-es2015-modules-commonjs to .babelrc, and then the error message changed to: Module not found: Error: Can't resolve 'postcss-loader'. MUCH more clear. Adding the Babel modules transform may be another good way to improve the error message for now.

Maybe adding an error message a la @Toub's would make sense? Not everyone will by their own figure out to do that.

👍  Agree! The way it's showing the error now is very unclear & misleading.

This happened to me after an npm update. Followed @Toub advice said I was missing ./serializers/serializer' which I didn't know what to do with.  I deleted my node_modules and did an npm update, and was back in working order.  Hope that helps!

Using webpack 2 with docker cause this error.
Dockerfile
FROM node

RUN npm i webpack -g

WORKDIR /tmp
ADD . /tmp
RUN npm install
CMD webpack

Excute
$ docker build -t test
$ docker run -it --rm test

Suggestion from @Toub saved me several hours.
Should be part added to web pack.

+1

Should be part added to web pack.

I had the same issue when I've changed the extension from .js -> .jsx.
The config param resolve: { extensions: ['.js', '.jsx'] } is fixed the build.
It should be ['.', '.js', '.jsx'] for webpack 1.x.
Suggestion from @Toub saved my day.

The same issue. I used the Toub  method.
I suggest it will be good to add this handler into core because without this error message it's really hard to find where is an issue.
My issue was  an incorrect export path.
export * from "serverError.actions";
instead
export * from "./serverError.actions";

@Toub  You saved my day. Really thanks (y)

Thanks all, for my case is I missed add 'node_modules' in resolve.modules

thanks for all the hints - in my case it was a wrong export path.

I've meet the same issue when replacing react-router with react-router-dom. And finally figured out what happened.
Steps to reproduce this issue:

npm i react-router --save
npm i react-router-dom --save
npm uninstall react-router --save
build with webpack

This is because react-router-dom also use react-router as dependency in code below
export { Redirect as default } from 'react-router'

when you uninstall react-router, npm just naively remove it without check if it's other module's dependency.

I'm getting the same issue and I follow the suggestion proposed by @Toub But I found a file that I didn't touch at all
File not found:  HarmonyImportDependency {
  module: null,
  request: 'rxjs/Observable',
  userRequest: 'rxjs/Observable',
  range: [ 501, 546 ],
  importedVar: '__WEBPACK_IMPORTED_MODULE_1_rxjs_Observable__',
  loc: SourceLocation { index: -1 } }

Could someone have face the same problem? There's any clue to solve this one?

@luizfilipe Are you sure that rxjs is installed?

@n-sviridenko I'm not using rxjs on my project... this should be a dependency...

@luizfilipe yes, I mean make sure that it's present in node_modules.

Yeah it's not installed there...

I am a newbie here and I falled into the same error after doing an update. I added the extra lines as suggested by @Toub  to node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js:144 but the extra lines wasn't executed!!
updateHash(hash) {
	super.updateHash(hash);

	// extra 1: not executed
      if (this.importDependency.module != null){
          // console.log('Module resource: ',
			// this.importDependency.module.resource);
       }else{
          console.log('\nFile not found: ', this.importDependency);
       }

	const hashValue = this.getHashValue(this.importDependency.module);

	// extra 2: not executed neither
      if (this.importDependency.module != null){
          // console.log('Module resource: ',
			// this.importDependency.module.resource);
       }else{
          console.log('\nFile not found: ', this.importDependency);
       }
	hash.update(hashValue);
}

My questions are: (1) why my changes got ignored? (2) where is the console log generated? (3) Why not making explicit error message a permanent feature of HarmonyExportImportedSpecifierDependency.js ?
Desperately seeking your helps ! Great stuffs by the way.
ng serve --host <IP_ADDRESS> --proxy-config proxy.conf.json
As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
which will only support Node 6.9 and greater. This package will be officially deprecated
shortly after.
To disable this warning use "ng set --global warnings.packageDeprecation=false".
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
** NG Live Development Server is running on http://<IP_ADDRESS>:4200. **
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
** NG Live Development Server is running on http://<IP_ADDRESS>:4200. **
86% hashingcrypto.js:74
this._handle.update(data, encoding);
^
TypeError: Data must be a string or a buffer
at Hash.update (crypto.js:74:16)
at HarmonyExportImportedSpecifierDependency.updateHash (C:\Projects\GIT\ai_engine\AssetComputationEngine\webapp\frontend\node_modules\angular-cli\node_modules\webpack\lib\dependencies\HarmonyExportImportedSpecifierDependency.js:144:8)
at C:\Projects\GIT\ai_engine\AssetComputationEngine\webapp\frontend\node_modules\angular-cli\node_modules\webpack\lib\DependenciesBlock.js:33:5
at Array.forEach (native)
at NormalModule.Dependenci
Robert

Grrrr... this occurs due to exports for files that no longer exist. In my case I was exporting an interface from a barrel (index.ts). I previously deleted the file, but forgot to remove it from the barrel.

I'm using only ts and tsx source files so I had resolve.extensions = ['.ts', '.tsx']. When I changed it to resolve.extensions = ['.js', '.ts', '.tsx'] it worked. I think this is because I'm depending on 3rd party js modules.

To figure out what file is causing you problems, just find node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js
then method:
updateHash(hash)
and wrap:
hash.update(hashValue);
into try {} catch {}
This way you will see similar error like I had:
ERROR in ./src/components/index.js Module not found: Error: Can't resolve './Hello' in ...

Was getting this error also:
86% hashingcrypto.js:74
  this._handle.update(data, encoding);
               ^

TypeError: Data must be a string or a buffer

I removed the following line of code from an index.ts because the file location had changed:
export { CounterService } from './counter/counter.service';
Then got a new error:
"ERROR in C:/git/demo/src/app/app.module.ts (22,32): File 'C:/git/demo/src/app/shared/services/index.ts' is not a module."
This was easy to solve in app.module.ts by changing the reference to import { CounterService } from './counter/services/counter.service';
rather than import { CounterService } from './shared/services'; which no longer existed

@Toub you've saved the day!

Ran into this when updating graphql-tag to v2. After troubleshooting I realized I had to add graphql as it was no longer bundled. Thanks @Toub!

For anyone landing on this from a Mac, my issue was pathname case-sensitivity when running a project created on OSX that I tried to run on a Linux box.  Installing https://github.com/Urthen/case-sensitive-paths-webpack-plugin helped me replicate the issue on OSX.

You might have this issue as well if you're both importing a module A and another module B which re-export the first one.

I'm running Ubuntu 16 on Cloud 9 with NVM running Node 6.9.0 and I'm working my way through the Thinkster Angular 2 tutorial and having a problem that seems to be this issue:
ERROR in<EMAIL_ADDRESS>(12,56): Property 'VIEW_ENCAPSULATION_VALUES' does not exist on type '{ isDefaultChangeDetectionStrategy: (changeDetectionStrategy: ChangeDetectionStrategy) => boolean...'.
ERROR in AppModule is not an NgModule
What is the status of this?  I'm checking out code from this Github so I don't think I've missed an export:
https://github.com/gothinkster/angular2-realworld-example-app/

I'm using node v4.8.0 (npm v3.10.10), blocked by this error. What is the final resolution for this error?

@prashathsenthil
For me, I followed @Toub solution and added the extra lines to HarmonyExportImportedSpecifierDependency.js. However, be careful to modify the correct js file (i changed the wrong file initially :). In my case, it turned out to be a typo mistake and a dependency could not be found. Fixing the dependency typo error fixed my issue.  IMHO, @Toub solution should somehow be added permanently to HarmonyExportImportedSpecifierDependency.js. Good luck.

🙄 The issue is closed. If you scroll up to where this issue was closed, you will see commit 1ccf8ddcbee279b8e8ed0c04efb45fb7e4b434f9. If you look, github shows that it's earliest including tag is 2.3.0. Demonstrating this fixes it:
> yarn add<EMAIL_ADDRESS>...
> cat foo.js
export { name } from "does-not-exist";
> cat bar.js
import { name } from './foo';

name();
> yarn webpack ./bar out
yarn webpack v0.23.2
$ "/mnt/c/code/tests/webpack-4072/node_modules/.bin/webpack" ./bar out
crypto.js:74
  this._handle.update(data, encoding);
               ^

TypeError: Data must be a string or a buffer
    at TypeError (native)
    at Hash.update (crypto.js:74:16)
    at HarmonyExportImportedSpecifierDependency.updateHash (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/dependencies/HarmonyExportImportedSpecifierDependency.js:144:8)
    at /mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/DependenciesBlock.js:33:5
    at Array.forEach (native)
    at NormalModule.DependenciesBlock.updateHash (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/DependenciesBlock.js:32:20)
    at NormalModule.Module.updateHash (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Module.js:162:41)
    at NormalModule.updateHash (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/NormalModule.js:327:30)
    at modules.forEach.m (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Chunk.js:253:31)
    at Array.forEach (native)
    at Chunk.updateHash (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Chunk.js:253:16)
    at Compilation.createHash (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Compilation.js:1121:10)
    at sealPart2 (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Compilation.js:605:9)
    at Compilation.applyPluginsAsyncSeries (/mnt/c/code/tests/webpack-4072/node_modules/tapable/lib/Tapable.js:131:46)
    at Compilation.seal (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Compilation.js:570:8)
    at /mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Compiler.js:474:16
    at /mnt/c/code/tests/webpack-4072/node_modules/tapable/lib/Tapable.js:225:11
    at _addModuleChain (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Compilation.js:472:11)
    at processModuleDependencies.err (/mnt/c/code/tests/webpack-4072/node_modules/webpack/lib/Compilation.js:443:13)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
error Command failed with exit code 1.
> yarn upgrade<EMAIL_ADDRESS>...
> yarn webpack ./bar out
yarn webpack v0.23.2
$ "/mnt/c/code/tests/webpack-4072/node_modules/.bin/webpack" ./bar out
Hash: 6e9cd5e5a655964f3273
Version: webpack 2.3.3
Time: 107ms
Asset     Size  Chunks             Chunk Names
  out  3.31 kB       0  [emitted]  main
   [0] ./foo.js 40 bytes {0} [built]
   [1] ./bar.js 40 bytes {0} [built]

ERROR in ./foo.js
Module not found: Error: Can't resolve 'does-not-exist' in '/mnt/c/code/tests/webpack-4072'
 @ ./foo.js 1:0-38
 @ ./bar.js
error Command failed with exit code 2.

@biblelogosthegame  why would you think that's the same issue? It looks totally different.

@Toub nice solution saved me!

Thanks @Toub This was killing me! And thanks @carlosvillademor for pointing me to this post!

Why @Toub solution isnt embedded in by default? (P.S. for me, webpack coldnt find wrong export in index.ts)
Webpack 2.2.1 (yarn lock)

Because it was a bug, that was fixed in 2.3.
On Tue, 30 May 2017, 04:25 bjornmelgaard<EMAIL_ADDRESS>wrote:

Why @Toub https://github.com/toub solution isnt embedded in by default?
(P.S. for me, webpack coldnt find wrong export in index.ts
https://github.com/BjornMelgaard/ngrx-todolist/blob/3bc088c93ff36b0f16cd5e2f2e8ec09ecd90272d/frontend/src/app/core/index.ts#L3
)
Webpack 2.2.1 (yarn lock
https://github.com/BjornMelgaard/ngrx-todolist/blob/3bc088c93ff36b0f16cd5e2f2e8ec09ecd90272d/frontend/yarn.lock#L5016
)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/4072#issuecomment-304696340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwVo11ljDzbs-YEpknXNAEgaVDdpSQgks5r-vFtgaJpZM4Lp5SW
.

My problem was that I was exporting from a file that doesn't exist in my code:
export { postsReducer } from './posts'
Try to check if there any dependency with wrong name.

@herlon214 , this bug is fixed indeed, I was getting this error because yarn install maximum satisfying version of webpack (2.2.1) and I resolved this by adding webpack to dependencies explicitly, now it updates to maximum available

Thank you, @Toub!!!!

@Toub  Thanks very much!

Using CLI you can use 'ng build -aot' and it will give the exact file / error causing the issue.

@Toub Thanks so much :+1:  !!!

For those using @angular/material, we got this error using the latest release of the master branch.
https://github.com/angular/material2/issues/5320
Having "@angular/material": "2.0.0-beta.7" in our package.json file fixed the compilation error.

In my case it was a file exported by an barrel that didn't exists.
Would be easier if VSCode have had shown me the error before angular's compilers.
:stuck_out_tongue_winking_eye:

Is there a way to activate some more logs to see what's missing without changing code ? I'm on Docker and on Win 7, there is no way for me to launch an interactive bash to change the code of webpack without having my container running. But as it's building the app via 'ng serve', it's failing because of this error. And I'm out of my container.

Retested this morning, with "@angular/material": "2.0.0-beta.7" as suggested by @michaelz . It worked nice. Also, yesterday, there was a problem with npm registry when trying to fecth latest angular packages. Now resolved.

Like @michaelz  and @dargoan I had an issue with @angular/material package.
Be sure to have "@angular/material": "2.0.0-beta.7" and not "@angular/material": "^2.0.0-beta.7".
After cleaning node_modules, then npm install all is working fine.

Thank you @Toub - saved me!
I spent few hours, Finally found you@Toub thank you sooo much.

@angular/cdk was missing on my case.

@Toub Someone give this guy a medal. Thank you Lord!

@thatisuday @G-Pandey What have you done afterwards? I'm missing cdk too. Am I supposed to install it manually?

Yes. Install @angular/cdk
On 11-Jul-2017 6:48 PM, "Kai"<EMAIL_ADDRESS>wrote:

@thatisuday https://github.com/thatisuday @G-Pandey
https://github.com/g-pandey What have you done afterwards? I'm missing
cdk too. Am I supposed to install it manually?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/4072#issuecomment-314440344,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFcnzQfH16IUQzt92moEoZVt22DJRBBFks5sM3YVgaJpZM4Lp5SW
.

for anyone using angular material2 in their project, here's the fix:
npm install --@angular/cdk --save
this is because material 2 now uses cdk as a dependency. CDK is the short form of component dev kit. This signifies that these are general-purpose tools for building components that are not coupled to Material Design
Ref: https://github.com/angular/material2/blob/master/guides/getting-started.md#step-1-install-angular-material-and-angular-cdk

@Toub , my missing file is @angular/cdk. then i checked there's 20677 files have import this modoul..
I dont know how to fix this

my missing file is "@angular/cdk". and there's 2600+ file have imported this.. idk wut to do

Please ignore my above comment.
for anyone using angular material2 in their project, here's the fix:
npm install -- --save @angular/cdk
this is because material 2 now uses cdk as a dependency. CDK is the short form of component dev kit. This signifies that these are general-purpose tools for building components that are not coupled to Material Design
Ref: https://github.com/angular/material2/blob/master/guides/getting-started.md#step-1-install-angular-material-and-angular-cdk

Yes. Install @angular/cdk
@Toub thanks.

For me it was exporting member from uninstalled node module.. but nothing in error even in node debug log pointed me to the problem. It was just reading this thread for hints and analysing git log history.
I see that it should be fixed by this merge: https://github.com/webpack/webpack/pull/4368
But I dont know how to find out the release version containing that merge.
I am using webpack v2.6.1, I dont want to risk changing major version due to project stage. Thanks ;)

I had its same issue in an Angular project and i added on  devDependencies the package "@ngtools/webpack":"1.4.0". (we have increased the version wich angular choose to install as his dependency) and this generic erros gone away and the project import/exports erros was shown

@Toub,
I put your script in my file but I still just get the same error message no more information:
HarmonyExportImportedSpecifierDependency.js shown below
`
updateHash(hash) {
super.updateHash(hash);
const hashValue = this.getHashValue(this.importDependency.module);
//debugging code ADS
	if (this.importDependency.module != null){
		// console.log('Module resource: ', this.importDependency.module.resource);
	 }else{
		console.log('\nFile not found: ', this.importDependency);
	 }
	 //debugging end
	hash.update(hashValue);

}

`
Error message from console:
` 86% hashingcrypto.js:74
this._handle.update(data, encoding);
^
TypeError: Data must be a string or a buffer
at TypeError (native)
at Hash.update (crypto.js:74:16)
at HarmonyExportImportedSpecifierDependency.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli
\node_modules\webpack\lib\dependencies\HarmonyExportImportedSpecifierDependency.js:144:8)
at C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\DependenciesBlock.js:33:5
at Array.forEach (native)
at NormalModule.DependenciesBlock.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modu
les\webpack\lib\DependenciesBlock.js:32:20)
at NormalModule.Module.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack
\lib\Module.js:162:41)
at NormalModule.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\No
rmalModule.js:327:30)
at modules.forEach.m (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Chunk.js
:253:31)
at Array.forEach (native)
at Chunk.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Chunk.js:
253:16)
at Compilation.createHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Com
pilation.js:989:10)
at sealPart2 (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilation.js:5
80:9)
at next (C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:202:11)
at Compilation. (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Pr
ogressPlugin.js:110:5)
at next (C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:204:14)
at ExtractTextPlugin. (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index
.js:317:5)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:421
:16
at iteratorCallback (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async
\dist\async.js:998:13)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:906
:16
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:301:6
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:421
:16
at iteratorCallback (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async
\dist\async.js:998:13)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:906
:16
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:298:13
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:308
3:16
at eachOfArrayLike (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async
dist\async.js:1003:9)
at eachOf (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\asyn
c.js:1051:5)
at Object.eachLimit (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async
\dist\async.js:3145:5)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:271:11
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:308
3:16
at eachOfArrayLike (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async
dist\async.js:1003:9)
at eachOf (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\asyn
c.js:1051:5)
at Object.eachLimit (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async
\dist\async.js:3145:5)
at ExtractTextPlugin. (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index
.js:268:10)
at Compilation.applyPluginsAsyncSeries (C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:206:
13)
at Compilation.seal (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilati
on.js:545:8)
at C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compiler.js:474:16
at C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:289:11
at _addModuleChain (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilatio
n.js:452:11)
at processModuleDependencies.err (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack
lib\Compilation.js:423:13)
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)
PS C:\wamp\www\nationalgrid\public_cli>
`
Further advice would be appreciated
Thanks

@Toub
I tried your debugging code but get nothing back below is the error and my edit to the file you specified
`** NG Live Development Server is running on http://localhost:4200. **
86% hashingcrypto.js:74
this._handle.update(data, encoding);
^
TypeError: Data must be a string or a buffer
at TypeError (native)
at Hash.update (crypto.js:74:16)
at HarmonyExportImportedSpecifierDependency.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\dependencies\HarmonyExportImportedSpecifierD
ependency.js:144:8)
at C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\DependenciesBlock.js:33:5
at Array.forEach (native)
at NormalModule.DependenciesBlock.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\DependenciesBlock.js:32:20)
at NormalModule.Module.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Module.js:162:41)
at NormalModule.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\NormalModule.js:327:30)
at modules.forEach.m (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Chunk.js:253:31)
at Array.forEach (native)
at Chunk.updateHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Chunk.js:253:16)
at Compilation.createHash (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilation.js:989:10)
at sealPart2 (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilation.js:580:9)
at next (C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:202:11)
at Compilation. (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\ProgressPlugin.js:110:5)
at next (C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:204:14)
at ExtractTextPlugin. (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:317:5)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:421:16
at iteratorCallback (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:998:13)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:906:16
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:301:6
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:421:16
at iteratorCallback (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:998:13)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:906:16
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:298:13
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3083:16
at eachOfArrayLike (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:1003:9)
at eachOf (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:1051:5)
at Object.eachLimit (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3145:5)
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:271:11
at C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3083:16
at eachOfArrayLike (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:1003:9)
at eachOf (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:1051:5)
at Object.eachLimit (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3145:5)
at ExtractTextPlugin. (C:\wamp\www\nationalgrid\public_cli\node_modules\extract-text-webpack-plugin\index.js:268:10)
at Compilation.applyPluginsAsyncSeries (C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:206:13)
at Compilation.seal (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilation.js:545:8)
at C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compiler.js:474:16
at C:\wamp\www\nationalgrid\public_cli\node_modules\tapable\lib\Tapable.js:289:11
at _addModuleChain (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilation.js:452:11)
at processModuleDependencies.err (C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\Compilation.js:423:13)
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)`
	updateHash(hash) { 		super.updateHash(hash); 		const hashValue = this.getHashValue(this.importDependency.module); 		if (this.importDependency.module != null){ 			// console.log('Module resource: ', this.importDependency.module.resource); 		 }else{ 			console.log('\nFile not found: ', this.importDependency); 		 } 		hash.update(hashValue); 	}

@stephenad are you sure to edit the right file?
Your stack trace is still at line 144, so you probably edited an other version of this file.
Try again with C:\wamp\www\nationalgrid\public_cli\node_modules\angular-cli\node_modules\webpack\lib\dependencies\HarmonyExportImportedSpecifierDependency.js

Received the same error due to some package update, can't specify exactly which package caused it but I resolved it by removing all node modules packages and a little tweaking up with the versions of @angular modules. Try to use these package versions (you may remove the unnecessary one's)
"devDependencies": {
"@angular/cli": "^1.3.0",
"@angular/common": "^4.0.0",
"@angular/compiler": "^4.0.0",
"@angular/core": "^4.0.0",
"@angular/forms": "^4.0.0",
"@angular/http": "^4.0.0",
"@angular/platform-browser": "^4.0.0",
"@angular/platform-browser-dynamic": "^4.0.0",
"@angular/router": "^4.0.0",
"@types/node": "^6.0.73",
"core-js": "^2.4.1",
"eslint": "3.19.0",
"eslint-config-google": "0.7.1",
"node-sass": "^4.5.3",
"rollup": "^0.41.6",
"rollup-plugin-commonjs": "^8.0.2",
"rollup-plugin-node-resolve": "^3.0.0",
"rollup-plugin-uglify": "^1.0.2",
"rxjs": "^5.1.0",
"zone.js": "^0.8.14"
},
"directories": {
"test": "test"
},
"dependencies": {
"@angular/animations": "^5.0.0-beta.4",
"@angular/cdk": "^2.0.0-beta.8",
"@angular/common": "^5.0.0-beta.4",
"@angular/compiler": "^5.0.0-beta.4",
"@angular/compiler-cli": "^4.1.2",
"@angular/core": "^5.0.0-beta.4",
"@angular/forms": "^5.0.0-beta.4",
"@angular/http": "^5.0.0-beta.4",
"@angular/material": "^2.0.0-beta.8",
"@angular/platform-browser": "^5.0.0-beta.4",
"@angular/platform-browser-dynamic": "^5.0.0-beta.4",
"@angular/platform-server": "^5.0.0-beta.4",
"@angular/router": "^5.0.0-beta.4",
"@ng-bootstrap/ng-bootstrap": "^1.0.0-beta.1",
"@types/jasmine": "2.5.38",
"@types/lodash": "^4.14.64",
"@types/node": "^6.0.73",
"angular-material": "^1.1.4",
"b": "^2.0.1",
"body-parser": "1.17.1",
"bootstrap": "^4.0.0-alpha.6",
"codelyzer": "~2.0.0",
"cookie-parser": "1.4.3",
"ejs": "2.5.6",
"eslint": "3.19.0",
"eslint-config-google": "0.7.1",
"express": "4.15.2",
"express-session": "1.15.3",
"express-validator": "3.2.0",
"font-awesome": "^4.7.0",
"jasmine-core": "~2.5.2",
"jasmine-spec-reporter": "~3.2.0",
"jquery": "^3.2.1",
"jsonwebtoken": "7.4.1",
"karma": "~1.4.1",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^0.2.0",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"mongoose": "4.10.1",
"morgan": "1.8.1",
"multer": "^1.3.0",
"passport": "0.3.2",
"passport-jwt": "2.2.1",
"passport-local": "1.0.0",
"protractor": "~5.1.0",
"stylus": "0.54.5",
"temp": "0.8.3",
"ts-node": "~2.0.0",
"tslint": "~4.5.0",
"typescript": "^2.4.2",
"uuid": "3.0.1",
"winston": "2.3.1"
}

thanks @Toub

My stack trace was happening because I was using the DllReferencePlugin, and hadn't upgraded my dll webpack config file and re-ran it.

in my case, after check, it was null.

var word = "s3cr3t";
crypto.createHash('sha256').update(word.toString()).digest('base64').toString();

@Toub there's no importDependency in my HarmonyExportImportedSpecifierDependency.js :(

@stupidprog my workaround was for webpack 2.2.0, so I guess you are using a more recent version

so how i solve this ? :(
`88% hashinginternal/crypto/hash.js:58
throw new ERR_INVALID_ARG_TYPE('data',
^
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be one of type string, TypedArray, or DataView. Received type undefined
at Hash.update (internal/crypto/hash.js:58:11)
at BulkUpdateDecorator.update (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\util\createHash.js:35:14)
at CssModule.updateHash (D:\Intan\workspace\belisada-seller\node_modules\mini-css-extract-plugin\dist\index.js:105:10)
at Compilation.createHash (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\Compilation.js:2296:11)
at hooks.optimizeTree.callAsync.err (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\Compilation.js:1288:9)
at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:32:10), :9:1)
at AsyncSeriesHook.lazyCompileHook (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\Hook.js:154:20)
at Compilation.seal (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\Compilation.js:1244:27)
at hooks.make.callAsync.err (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:624:17)
at _done (eval at create (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:32:10), :9:1)
at _err2 (eval at create (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:32:10), :44:22)
at _addModuleChain (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\Compilation.js:1095:12)
at processModuleDependencies.err (C:\Users\Intan\AppData\Roaming\npm\node_modules\webpack\lib\Compilation.js:1007:9)
at process._tickCallback (internal/process/next_tick.js:61:11)`

Sorry I am not a webpack expert, please open a ticket on Stackoverflow.

In my case it was some problem with yarn.lock, I deleted it and run yarn and problem was gone

I got this, how to get rid of it then
Seed: [object Promise]
mnemonic:
crypto.js:97
  this._handle.update(data, encoding);
               ^

TypeError: Data must be a string or a buffer
    at Hmac.update (crypto.js:97:16)
    at Function.HDKey.fromMasterSeed (/home/locpv/node_modules/hdkey/lib/hdkey.js:177:54)
    at Object.<anonymous> (/home/locpv/orig.js:13:20)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Function.Module.runMain (module.js:605:10)
    at startup (bootstrap_node.js:158:16)


Gauge Returns Exit Code 0 When It Fails To Run

Expected behavior

When attempting to run tests ("Gauge run...") in a folder that does not contain a Gauge project file, the Exit Code should be non-zero to denote that the run did not complete successfully.
When attempting to run tests in a folder that contains a Gauge project file but you do not point Gauge to a valid spec file or folder containing specs (e.g. "Gauge run adsfasfa" where there's no folder adsfasfa), the Exit Code should be non-zero to denote that the run did not complete successfully.

Actual behavior
Exit Code 0 is returned.
Steps to reproduce

Open up a command or Powershell window (only tested on Windows) to a directory that does not contain a Gauge project file.
Run "Gauge run specs"
Check the exit code using either "echo %errorlevel%" (CMD) or "$LASTEXITCODE" (Powershell)

Open up a command or Powershell window (only tested on Windows) to a directory that does contain a Gauge project file.
Run "Gauge run " where  is a string that does not correspond to a folder in the current directory.
Check the exit code using either "echo %errorlevel%" (CMD) or "$LASTEXITCODE" (Powershell)

Gauge version
Gauge version: 1.0.3
Commit Hash: ff6c0c3
Plugins
csharp (0.10.5)
dotnet (0.1.1)
html-report (4.0.6)
screenshot (0.0.1)

fix should be available in nightly >= 23/5/2019

I am able to replicate the second excepted behaviour.
Tested version: 1.0.6.nightly-2019-05-27

Hi! When will the next Gauge version be released? Is there a schedule?

Hello, This issue is making it tough for me to trouble shoot our gauge implementation using powershell/azure devops.  Is this still going to be addressed?

Gauge 1.0.7 is out. Can you please check if this is an issue?
I tried on Linux as well as Windows 10. Running gauge run in an empty directory or passing a non existent folder (ex. gauge run nodir) both return exit code 1 for me on both the operating system.

Current behavior of gauge run command

When run inside a non Gauge project directory.
Exits with exit code 1

When run inside a Gauge project directory but the specs directory does not exists.
Exits with exit code 0

When run inside a Gauge project directory but the specs directory is empty.
Exits with exit code 0

When run inside a Gauge project directory but no specs are found after applying tags filter.
Exits with exit code 0

Purposed behavior for gauge run command

When run inside a non Gauge project directory.
Exits with exit code 1

When run inside a Gauge project directory but the specs directory does not exists.
Exits with exit code 1

When run inside a Gauge project directory but the specs directory is empty.
Exits with exit code 1

When run inside a Gauge project directory but no specs are found after applying tags filter.
Exits with exit code 0


!owns should check subID's too.

Well just a copy of russian locale Steam chat with bot:
15:00 - KazeZlat: !owns 50167
14:59 - bot:
<bot> Не имеет: 50167
15:01 - KazeZlat: HFIEX-*****-*****
15:01 - bot:
<bot> Ключ: HFIEX-*****-***** | Состояние: AlreadyOwned | Предметы: [50167, DiRT 3 Complete Edition]
<anotherbot> Ключ: HFIEX-*****-***** | Состояние: OK | Предметы: [50167, DiRT 3 Complete Edition]

It will be great if we could check subIDs too, so dumb people like me won't be fooled like this :D
P.S. I understand this requires to check DLCs, where false positive/negative can happen, but maybe we can make it work when there are no DLCs or only one appID in subID package at least?

P.S. If you want to avoid forwarding then you have !redeem^ for that.
This is still valid idea, since we record PackageIDs already, but even if I add support for this, then it might not result in solving your particular issue. Steam is a gigantic mess, I've already seen many situations in which subIDs do not match, or Steam doesn't report given subID as owned, so !owns can still lie regardless.


Python: Rough implementation of the planner in python

NOTE: this is work in progress. There are some bugs I need to fix/cleanup (e.g. the plane creation always uses all registered functions), but I'd be eager to get some initial feedback as I'm aware of the refactoring/active development currently ongoing in the C# SK implementation.
Motivation and Context
Many Python developers want to start building more powerful intent based AI applications. One of the key components is still missing: The Planner (see issue: #232). This is a (not complete) reimplementation of the C# Planner implementation with deviations where needed (e.g. Python doesn't have a notion of extensions).
Description
I have tried to follow the C# Planner implementation as much as possible. I have added two tests which demonstrate how to create a plan and execute a plan. Note (again) that these tests are not properly implemented (yet) and act as a way to demonstrate it's working.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

@Sruinard this is awesome! I think a bunch of things RE planning are changing, as you point out, but it might be nice to get this merged in and at least have something to build off of (even as things change).
I will take a deeper look at this soon, we have a planning meeting tomorrow and a few PRs that will (unfortunately) cause a bunch of conflicts here, but that's okay. We can work through that!
Also, if you want to add me to your SK fork I'd be happy to help w/ syncing with the recent changes we've made (once those PRs get merged)!

FYI: Python PRs on hold while we stage to merge /python into main. See https://github.com/microsoft/semantic-kernel/pull/423


Sometimes there is no response.

I had to make this change to make the code work for me.  Awesome client, I get about 20x less CPU than  https://github.com/dpkp/kafka-python.git (we use a gevent based framework, no threads, high-ish volume).

Seems to have some issues interoperating with gevent, I'm going to start diving into the guts.  Will do a PR or maybe just fork and rename it.

To be specific:  I'm getting concurrency related errors like:
10533:22/16:45:56.605460 /X/HOME/SHERLOCK/SYSLOGMON/SYSLOGMON/INFRA/LL (170760848/10533):kafka Could not send request ['\x00\x00\x00;\x00\x03\x00\x00\x00\x00\x01\xf9\x00\x0ckafka-python\x00\x00\x00\x01\x00\x1fgps.logging.akamailogs.api.prod'] to server <kafka.connection.KafkaConnectionPool object at 0x000000000b14b018>, trying next server: This socket is already used by another greenlet: <bound method Waiter.switch of <gevent.hub.Waiter object at 0x000000000f192410>>
(I just changed the files to import gevent.socket instead of import socket)

Also:  10133:22/16:45:56.383719 /X/HOME/SHERLOCK/SYSLOGMON/SYSLOGMON/INFRA/LL (191858256/10133):kafka Could not send request ['\x00\x00\x00;\x00\x03\x00\x00\x00\x00\x05h\x00\x0ckafka-p
ython\x00\x00\x00\x01\x00\x1fgps.logging.akamailogs.web.prod'] to server <kafka.connection.KafkaConnectionPool object at 0x000000000b14ae20>, trying next server: This socket is
already used by another greenlet: <bound method Waiter.switch of <gevent.hub.Waiter object at 0x000000000b2c9fa0>>
10133:22/16:45:56.387067 /X/HOME/SHERLOCK/SYSLOGMON/SYSLOGMON/INFRA/LL (172250688/10133):kafka Could not send request ['\x00\x00\x00;\x00\x03\x00\x00\x00\x00\x05g\x00\x0ckafka-p
ython\x00\x00\x00\x01\x00\x1fgps.logging.akamailogs.web.prod'] to server <kafka.connection.KafkaConnectionPool object at 0x000000000b14ae20>, trying next server: [Errno 9] File
descriptor was closed in another greenlet


tokenization issue for code

Does this still a bug for tokenization? I want to use this for code. Thanks!

If you are talking about the fast encoder, it was fixed in the main branch of transformers. AFAIK it hasn't been tagged as a release, yet.

Probably a duplicate of #40?

Check out our OpenLLaMA v2 model, which has a new tokenizer and is pretrained with a lot of code. The official release of that will happen very soon.

can we use the old models or how does this work? We just load the old model with the new tokenizer?
Brando Miranda
Ph.D. Student
Computer Science, Stanford University
EDGE Scholar, Stanford University
@.***
website: https://brando90.github.io/brandomiranda/home.html
mentorship opportunities: https://brando90.github.io/brandomiranda/prospective-collaborations.html
On Jul 7, 2023, at 12:52 AM, Xinyang (Young) Geng @.***> wrote:
Check out our OpenLLaMA v2 modelhttps://huggingface.co/openlm-research/open_llama_7b_v2, which has a new tokenizer and is pretrained with a lot of code. The official release of that will happen very soon.
—
Reply to this email directly, view it on GitHubhttps://github.com/openlm-research/open_llama/issues/61#issuecomment-1624940429, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOE6LRSBDRPTWUHHJTCYHDXO654DANCNFSM6AAAAAAZWCI5DE.
You are receiving this because you authored the thread.Message ID: @.***>

@brando90 The v2 model is a completely different one trained on a new mixture of dataset, so you'll need to load the new weights too.

Got it. Thanks!
I will assume v1 open llama is basically unusable for code gen (what I want) and use only v2.
Thanks!
Brando Miranda
Ph.D. Student
Computer Science, Stanford University
EDGE Scholar, Stanford University
@.***
website: https://brando90.github.io/brandomiranda/home.html
mentorship opportunities: https://brando90.github.io/brandomiranda/prospective-collaborations.html
On Jul 7, 2023, at 11:55 AM, Xinyang (Young) Geng @.***> wrote:
@brando90https://github.com/brando90 The v2 model is a completely different one trained on a new mixture of dataset, so you'll need to load the new weights too.
—
Reply to this email directly, view it on GitHubhttps://github.com/openlm-research/open_llama/issues/61#issuecomment-1625894602, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOE6LTTBRYD5CYUEVWXAGDXPBLQXANCNFSM6AAAAAAZWCI5DE.
You are receiving this because you were mentioned.Message ID: @.***>

@brando90 Yeah. I imagine you probably want to use v2 almost always since it is a better model overall.


Fixes Issue-52 Added feature to override the ToStringStyle used by the overloaded toString() methods

Fixes Issue-52 - Added feature to override the ToStringStyle used by the overloaded toString() methods. There is now a
public static ToStringStyle TO_STRING_BUILDER_STYLE
located in the Constants class that defaults to the current SHORT_PREFIX_STYLE but can be replaced with another one like JSON_STYLE. I also added a new package for utils and started a CommonUtils class. Here I added a few static prettyPrintJson helper methods. I also created a test class for that file.

@gizmochief7 can you remove gson? We already have jackson in the classpath.

@joaopsilva I removed the GSON dependancy, Removed the prettyPrintJson Util method as its not really needed and its test case, added a new test case for the Constant change only. Here is my commit changes Removed GSON dependancy

Thanks, I've merged it, please note that this might be removed in the future if the PR of Project Lombok is merged. As a general rule of thumb, clients should not rely on the toString method for application-specific logic.


Unused shader inputs are getting eliminated since the latest release

Somewhere between the rust-gpu .alpha.11 and .alpha.12 releases, it started entirely eliminating inputs like this:
#[spirv(push_constant)] _material: &Material,

if they are unused in the shader. This seems to be a bug.

This was likely caused (or rather, exposed) by #715 - however, inlining would've likely caused a similar issue.
My best guess is that DCE doesn't consider the OpEntryPoint interface variable list as a "root" that can keep its elements alive - I'm not sure having globals there without ever mentioning them inside functions will work, but we should try it at least.


add react-sticky-state

Nice component, thanks!

To add a component / library, add an entry at devarchy.com/react-components.

Is there a reason you did a PR instead?

@brillout yes github authorization failed. server did not respond. I will try again

Thanks for letting me know.
There was a problem with authentication for a subset of GitHub users. It's fixed now.
PRs are not convenient to manage, please add the entry to devarchy instead.

devarchy.com/react-components worked now


Added IAM:PassRole to the CreateBranch and DeleteBranch functions to …

…fix an issue with build/delete on branch
Issue #, if available:
Not tracked yet, but was receiving the following:
[ERROR]	2022-08-28T23:50:47.300Z	e2b85c4b-0586-4f82-a7fa-ec4d9a6fe72a	An error occurred (AccessDeniedException) when calling the CreateProject operation: User: arn:aws:sts::XX:assumed-role/cdk-pipelines-multi-branc-IAMPipelineLambdaCreateB-ZSTRO2FYNUZ8/LambdaTriggerCreateBranch is not authorized to perform: iam:PassRole on resource: arn:aws:iam::XX:role/cdk-pipelines-multi-branc-IAMPipelineCodeBuildExec-YJBU17LTTQ0G because no identity-based policy allows the iam:PassRole action
Description of changes:

Added grant_pass_role() to both the create_branch_role and delete_branch_role

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Yes

After instituting the above change, I am now seeing:
[INFO]	2022-08-29T00:41:17.139Z	e7ff532b-7452-4af4-b8fe-c24a6be8ae7e	{'version': '0', 'id': '73a98029-8f68-5a0b-9fef-91fa3cce3717', 'detail-type': 'CodeCommit Repository State Change', 'source': 'aws.codecommit', 'account': 'XX', 'time': '2022-08-29T00:41:16Z', 'region': 'us-east-1', 'resources': ['arn:aws:codecommit:us-east-1:550767824695:cdk-pipelines-multi-branch'], 'detail': {'callerUserArn': 'arn:aws:iam::XX:user/XX', 'commitId': 'XXXXX', 'event': 'referenceCreated', 'referenceFullName': 'refs/heads/test5', 'referenceName': 'test5', 'referenceType': 'branch', 'repositoryId': 'f2758b79-fda5-4a33-9230-b9a90b96987f', 'repositoryName': 'cdk-pipelines-multi-branch'}}
and feature branches are now building as expected.


middleware on routes resource ignored

here's my routes.php (part of it)
Route::resource('/api/v1/message.', 'MessagingController',
                [
                    'only' => ['store'],
                    'middleware' => 'errors'
                ]);

Here's a copy of my artisa route:list
 ./artisan route:list
+--------+----------+--------------------------+-----------------------+---------------------------------------------------+------------+
| Domain | Method   | URI                      | Name                  | Action                                            | Middleware |
+--------+----------+--------------------------+-----------------------+---------------------------------------------------+------------+
|        | GET|HEAD | authenticate             |                       | App\Http\Controllers\AuthenticationService@create | farda      |
|        | GET|HEAD | send                     |                       | App\Http\Controllers\SendEmail@create             | farda      |
|        | GET|HEAD | xouid                    |                       | App\Http\Controllers\OrgunitService@create        | farda      |
|        | POST     | api/v1/message/{message} | api.v1.message..store | App\Http\Controllers\MessagingController@store    |            |
+--------+----------+--------------------------+-----------------------+---------------------------------------------------+------------+

notice the last line, there is no middleware registered as 'errors' and there is no exception or warning of sorts raised.
This is laravel 5.0

Take a look at the two answers to this question on SO

Laravel 5.0 is not supported.


Option-clicking checkbox doesn't work as expected.

In most OS X apps when you option click on a checkbox in a list, it will check or uncheck all the contents. Tried doing that in catalogs and it didn't work.

True, will add at some point. In the meantime, you can right-click anywhere on the packages list (in Catalogs view) and select enable all.


The file of modeling_options.yaml and analysis_options.yaml

Hi, everyone.
I copied modeling_options.yaml and analysis_options.yaml from IEA-15-240-RWT. I tried to run wisdem for IEA-22-280-RWT. An error occurred as listed.
Traceback (most recent call last):
File "G:\15MW\OpenFAST3.5.0\IEA-15-240-RWT-1.1.6\IEA-22-280-RWT-main\WISDEM\TestIEA-Driver001.py", line 31, in
wt_opt, analysis_options, opt_options = run_wisdem(fname_wt_input, fname_modeling_options, fname_analysis_options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "G:\Anaconda3\all\envs\wisdem-env\Lib\site-packages\wisdem\glue_code\runWISDEM.py", line 125, in run_wisdem
wt_opt = yaml2openmdao(wt_opt, modeling_options, wt_init, opt_options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "G:\Anaconda3\all\envs\wisdem-env\Lib\site-packages\wisdem\glue_code\gc_WT_InitModel.py", line 40, in yaml2openmdao
wt_opt = assign_airfoil_values(wt_opt, modeling_options, airfoils)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "G:\Anaconda3\all\envs\wisdem-env\Lib\site-packages\wisdem\glue_code\gc_WT_InitModel.py", line 1421, in assign_airfoil_values
cl[i, :, j_Re[j], k] = PchipInterpolator(
^^^^^^^^^^^^^^^^^^
File "G:\Anaconda3\all\envs\wisdem-env\Lib\site-packages\scipy\interpolate_cubic.py", line 234, in init
x, _, y, axis, _ = prepare_input(x, y, axis)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "G:\Anaconda3\all\envs\wisdem-env\Lib\site-packages\scipy\interpolate_cubic.py", line 48, in prepare_input
raise ValueError("The length of y along axis={0} doesn't "
ValueError: The length of y along axis=0 doesn't match the length of x
Could anyone please provide the right file of modeling_options.yaml and analysis_options.yaml for IEA-22-280-RWT? Thanks a lot.

Dear @fzahle,
I appreciate your reply sincerely.
It would be better if you can share the right geometry file of IEA-22-280-RWT. Since I tried to manually modify the original file, another error still occurs.

We would like to keep the three airfoil polars options in there, since these are needed for comparison to higher fidelity  aerodynamics codes, so if that didn't fix it for you I'm afraid I can't help much more. I know @ptrbortolotti has run it through WISDEM, so he can probably assist you with either a code fix in WISDEM or needed changes in the yaml.

Hello,
fzahle is right, WISDEM doesn't know what set of polars to load from the yaml because they all have the same Re number, and it errors out.
If you comment out the extra polar sets, WISDEM runs.
Try running the files below, they should work
issue19_iea22.zip

Hi @ptrbortolotti and @fzahle.
A million thanks to you. The files shared by you can be run by WISDEM. I appreciate your help, again.
It would be so kind if you can continue to answer my question. Whether the configuration of IEA-22-280 is optimized. WISDEM has the function of optimization, like towards the whole turbine or tower and monopile.

The tower and monopile of the IEA22 have been optimized to meet frequency, stresses, and buckling constraints. In addition, the diameter to thickness ratio is constrained between 90 and 150. Does this answer your question?
I am not sure what you mean with "running time". In WISDEM? Or in OpenFAST?

Hi, @ptrbortolotti.
Thanks for your help. I understand that IEA22 has been optimized.
I mean the run time in WISDEM. The time when I run IEA22 in WISDEM is about 33 seconds, while the run time of IEA15 is about 150 seconds. I am just curious about the difference.

Hello Sangwon,
the model has now settled. Is this still an active issue?
Best regards

Dear @ptrbortolotti
I confirmed steady-state analysis is normal.
I really appreciate your and other members efforts to develop this model.
Best regards,
Sangwon