(Solved) Dead loop with polymer 1.0


#1

Hello,

I am playing with polymer 1.0 and after adding few lines to header, it started to end up in dead loop.
On client it is just waiting for localhost.

Server is still running, but when I kill it, it could not start again with errors where I can see that it has issues run netstat -ano

So I run it myself and can see like all ports being used, it drops after some time.

TCP 127.0.0.1:62632 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62633 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62634 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62635 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62636 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62637 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62638 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62639 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62640 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62641 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62642 127.0.0.1:26261 TIME_WAIT 0
TCP 127.0.0.1:62643 127.0.0.1:26261 TIME_WAIT 0

Could I be hitting some limit of open files or such…

<head>
  <title>testimport</title>
  <script src="bower_components/webcomponentsjs/webcomponents-lite.min.js"></script>
  <link rel="import" href="bower_components/paper-input/paper-input.html">
  <link rel="import" href="bower_components/paper-tabs/paper-tabs.html">
  <link rel="import" href="bower_components/paper-checkbox/paper-checkbox.html">
  <link rel="import" href="bower_components/paper-header-panel/paper-header-panel.html">
  <link rel="import" href="bower_components/paper-toolbar/paper-toolbar.html">
  <link rel="import" href="bower_components/iron-flex-layout/iron-flex-layout">
</head>

Any more imports than this and it is crashing on me. Just tested this and by removing and adding last import it depends if it will run or fail.

Error after killing and trying to rerun

C:\workspace\meteor\testimport>meteor
[[[[[ C:\workspace\meteor\testimport ]]]]]

=> Started proxy.

C:\Users\shock\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.windows.x8
6_32\dev_bundle\lib\node_modules\fibers\future.js:278
                                                throw(ex);
                                                      ^
Error: Couldn't run netstat -ano: {}
    at Object.Future.wait (C:\Users\shock\AppData\Local\.meteor\packages\meteor-
tool\1.1.3\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fibers\future.js:398
:15)
    at findMongoPids (C:\Users\shock\AppData\Local\.meteor\packages\meteor-tool\
1.1.3\mt-os.windows.x86_32\tools\run-mongo.js:120:16)
    at findMongoAndKillItDead (C:\Users\shock\AppData\Local\.meteor\packages\met
eor-tool\1.1.3\mt-os.windows.x86_32\tools\run-mongo.js:236:14)
    at launchOneMongoAndWaitForReadyForInitiate (C:\Users\shock\AppData\Local\.m
eteor\packages\meteor-tool\1.1.3\mt-os.windows.x86_32\tools\run-mongo.js:360:7)
    at launchMongo (C:\Users\shock\AppData\Local\.meteor\packages\meteor-tool\1.
1.3\mt-os.windows.x86_32\tools\run-mongo.js:612:7)
    at [object Object]._.extend._startOrRestart (C:\Users\shock\AppData\Local\.m
eteor\packages\meteor-tool\1.1.3\mt-os.windows.x86_32\tools\run-mongo.js:712:19)

    at [object Object]._.extend.start (C:\Users\shock\AppData\Local\.meteor\pack
ages\meteor-tool\1.1.3\mt-os.windows.x86_32\tools\run-mongo.js:670:10)
    at C:\Users\shock\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.win
dows.x86_32\tools\run-all.js:199:26
    - - - - -
    at C:\Users\shock\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.win
dows.x86_32\tools\run-mongo.js:89:28
    at ChildProcess.exithandler (child_process.js:654:7)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:766:16)
    at Process.ChildProcess._handle.onexit (child_process.js:833:5)

C:\workspace\meteor\testimport>

I tested with xampp and when opening as standard html it is not having this behaviour.
Seems like some deadloop in these components which require/import each other by meteor.
I am pulling all iron and paper polymer elements into public folder using bower.

{
  "name": "testimport",
  "version": "0.0.0",
  "authors": [
    "xyz"
  ],
  "license": "MIT",
  "ignore": [
    "**/.*",
    "node_modules",
    "bower_components",
    "test",
    "tests"
  ],
  "dependencies": {
    "polymer": "Polymer/polymer#1.0.0",
    "iron-elements": "PolymerElements/iron-elements#~1.0.0",
    "paper-elements": "PolymerElements/paper-elements#~1.0.1"
  }
}

Seems that also Meteor official hosting is displaying same behaviour, sorry for causing issues there if I affected too many ports or so if not correctly secured.

PS: differential:vulcanize does not help

Regards
Robert


Web components support
#2

I am stupid, forgot .html in importing that iron-flex-layout :smiley: