[Bug] [Node.js] Strange timeout fixed with a simple console.log (weird)

Using :

• Azure Function : ~0.4 (and ~0.5)
• Node.js : 5.9.1 (and 6.4.0)

I’ve been using Azure Function with Node.js without any problem. Then I decided to transpil my code with Babel.js to make use of await/async. A strange bug appeared… an Azure Function timeout. I tried many things and after only adding logging, the timeout disappeared…

Here is the transpiled code with the console.log line… If I remove this single line, my Azure Function will timeout.

Index.js

"use strict";

module.exports = require("./lib/handle");

lib/handle.js

"use strict";

Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.default = handle;

var _EndPoint = require("./EndPoint");

var _EndPoint2 = _interopRequireDefault(_EndPoint);

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

// endPoint may be reused for many requests
const endPoint = new _EndPoint2.default();

/**
 * Basic Azure Function handle
 *
 * @param {Object} context Context object
 * @param {Object} req Request object
 */
function handle() {

  /* eslint no-console: 1 */
  // TODO: Next line is a hack to avoid timeout on Azure
  console.log("Starting...");

  endPoint.handle(...arguments);
}
module.exports = exports["default"];

Microsoft Support : I can give you my Azure Function URL in private

[mamaso]

@yvele @mathewc I ran a scenario with the _asyncToGenerator(fn) and it works after adding the #664 fix. Without #664 we encounter the hang. This should be working in release 0.6.

[yvele]

PS: I confirm it’s working with 0.6