From 952f541311db96b855bd5f9d5c6d5551d3296a5e Mon Sep 17 00:00:00 2001
From: Abhishek Lolage <abhisheklolage@gmail.com>
Date: Sat, 11 Feb 2017 19:43:40 +0000
Subject: [PATCH] Added itp bug number, long description and changed to
experimental version
---
debian/changelog | 5 ++---
debian/control | 7 +++++--
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 14a0af7..27c7db2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,5 @@
-node-max-timeout (1.0.0-1) UNRELEASED; urgency=low
+node-max-timeout (1.0.0-1) experimental; urgency=low
- * Initial release (Closes: #nnnn)
- * New upstream release
+ * Initial release (Closes: #854560)
-- Abhishek Lolage <abhisheklolage@gmail.com> Wed, 08 Feb 2017 11:28:19 +0000
diff --git a/debian/control b/debian/control
index f21411a..77d697c 100644
--- a/debian/control
+++ b/debian/control
@@ -17,7 +17,10 @@ Architecture: all
Depends:
${misc:Depends}
, nodejs
-Description: The max amount of milliseconds you can pass to `setTimeout()`
- FIX_ME long description
+Description: Max amount of milliseconds that can be passed to `setTimeout()`
+ Values larger than the one returned from this module, 2147483647 (~25 days),
+ are too big to fit into a signed 32-bit integer,
+ which is how JS engines store it, and will cause overflow,
+ resulting in the timeout being scheduled immediately.
.
Node.js is an event-based server-side JavaScript engine.
--
GitLab