From c807880f7ac73f813b2660ea81a00f7712a4e793 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 29 Aug 2016 12:39:49 +0200 Subject: Add old mailing list archives --- archives/extend/2013-September/000227.html | 104 +++++++++++ archives/extend/2013-September/000228.html | 133 ++++++++++++++ archives/extend/2013-September/000229.html | 143 +++++++++++++++ archives/extend/2013-September/000230.html | 76 ++++++++ archives/extend/2013-September/000231.html | 85 +++++++++ archives/extend/2013-September/000232.html | 99 ++++++++++ archives/extend/2013-September/000233.html | 116 ++++++++++++ archives/extend/2013-September/000234.html | 77 ++++++++ archives/extend/2013-September/000235.html | 97 ++++++++++ archives/extend/2013-September/000236.html | 109 +++++++++++ archives/extend/2013-September/000237.html | 84 +++++++++ archives/extend/2013-September/000238.html | 105 +++++++++++ archives/extend/2013-September/000239.html | 124 +++++++++++++ archives/extend/2013-September/000240.html | 140 +++++++++++++++ archives/extend/2013-September/000241.html | 163 +++++++++++++++++ archives/extend/2013-September/000242.html | 191 ++++++++++++++++++++ archives/extend/2013-September/000243.html | 66 +++++++ archives/extend/2013-September/000244.html | 99 ++++++++++ archives/extend/2013-September/000245.html | 117 ++++++++++++ archives/extend/2013-September/000246.html | 117 ++++++++++++ archives/extend/2013-September/000247.html | 134 ++++++++++++++ archives/extend/2013-September/000248.html | 141 +++++++++++++++ archives/extend/2013-September/000249.html | 72 ++++++++ archives/extend/2013-September/000250.html | 155 ++++++++++++++++ archives/extend/2013-September/000251.html | 212 ++++++++++++++++++++++ archives/extend/2013-September/000252.html | 188 +++++++++++++++++++ archives/extend/2013-September/000253.html | 210 ++++++++++++++++++++++ archives/extend/2013-September/000254.html | 269 ++++++++++++++++++++++++++++ archives/extend/2013-September/author.html | 187 +++++++++++++++++++ archives/extend/2013-September/date.html | 187 +++++++++++++++++++ archives/extend/2013-September/index.html | 243 +++++++++++++++++++++++++ archives/extend/2013-September/subject.html | 187 +++++++++++++++++++ archives/extend/2013-September/thread.html | 243 +++++++++++++++++++++++++ 33 files changed, 4673 insertions(+) create mode 100644 archives/extend/2013-September/000227.html create mode 100644 archives/extend/2013-September/000228.html create mode 100644 archives/extend/2013-September/000229.html create mode 100644 archives/extend/2013-September/000230.html create mode 100644 archives/extend/2013-September/000231.html create mode 100644 archives/extend/2013-September/000232.html create mode 100644 archives/extend/2013-September/000233.html create mode 100644 archives/extend/2013-September/000234.html create mode 100644 archives/extend/2013-September/000235.html create mode 100644 archives/extend/2013-September/000236.html create mode 100644 archives/extend/2013-September/000237.html create mode 100644 archives/extend/2013-September/000238.html create mode 100644 archives/extend/2013-September/000239.html create mode 100644 archives/extend/2013-September/000240.html create mode 100644 archives/extend/2013-September/000241.html create mode 100644 archives/extend/2013-September/000242.html create mode 100644 archives/extend/2013-September/000243.html create mode 100644 archives/extend/2013-September/000244.html create mode 100644 archives/extend/2013-September/000245.html create mode 100644 archives/extend/2013-September/000246.html create mode 100644 archives/extend/2013-September/000247.html create mode 100644 archives/extend/2013-September/000248.html create mode 100644 archives/extend/2013-September/000249.html create mode 100644 archives/extend/2013-September/000250.html create mode 100644 archives/extend/2013-September/000251.html create mode 100644 archives/extend/2013-September/000252.html create mode 100644 archives/extend/2013-September/000253.html create mode 100644 archives/extend/2013-September/000254.html create mode 100644 archives/extend/2013-September/author.html create mode 100644 archives/extend/2013-September/date.html create mode 100644 archives/extend/2013-September/index.html create mode 100644 archives/extend/2013-September/subject.html create mode 100644 archives/extend/2013-September/thread.html (limited to 'archives/extend/2013-September') diff --git a/archives/extend/2013-September/000227.html b/archives/extend/2013-September/000227.html new file mode 100644 index 00000000..9863b688 --- /dev/null +++ b/archives/extend/2013-September/000227.html @@ -0,0 +1,104 @@ + + + + [99s-extend] Cowboy load test + + + + + + + + + + +

[99s-extend] Cowboy load test

+ Joe Freeman + joe.freeman at bitroot.com +
+ Sun Sep 15 19:01:30 CEST 2013 +

+
+ +
Hi,
+
+I've started work on a project using Clojure, but I was wondering whether
+(and secretly hoping that) Erlang would be a better fit, so I've been load
+testing a few web server frameworks. I'm particularly interested in how the
+server can handle a large number of concurrent WebSocket connections, and
+the test I've been running is similar to Eric Moritz's [1].
+
+I've setup a simple Cowboy 'echo' server running on an EC2 instance
+(m1.medium, as in Eric's test) which could comfortably handle 10k
+concurrent WebSocket requests (as in Eric's results), while echoing about
+200 messages/second. The CPU usage of the VM at this point is about 99%,
+but the server continues to handle up to 40k concurrent connections with a
+consistent average response time (<30ms). Pushing the test beyond this
+number results in a spike in response times and lots of connection timeouts.
+
+40k connections seems pretty good, but when comparing this to the same test
+against a couple of Clojure/JVM-based frameworks (specifically Aleph/Netty
+and http-kit) I find I can get higher numbers of concurrent connections
+with slightly better average response times (100k connections, <10ms
+response time) using much less CPU (~20%). In fact, memory seems to be the
+limiting factor.
+
+So I have two questions:
+
+1) Should I be concerned about the CPU usage in the Erlang/Cowboy test? I
+have limited experience with Erlang so far, but 100% CPU feels like a bad
+thing.
+
+2) Is there any way to increase the performance of the cowboy server? Are
+there any Erlang VM parameters I can change? The fact that the Clojure/JVM
+tests (on the same machine) have managed to get to 100k connections
+suggests that the limitation isn't being imposed by the operating system
+(I've applied changes various changes to sysctl and ulimit).
+
+(Perhaps an echo server isn't the best way to compare HTTP servers, but it
+feels like a good starting point.)
+
+Thanks for any help.
+
+[1] https://github.com/ericmoritz/wsdemo/blob/results-v1/results.md - the
+GitHub repo actually contains code for an Aleph server, but results from
+this aren't included in the summary here.
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130915/c9a5340e/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000228.html b/archives/extend/2013-September/000228.html new file mode 100644 index 00000000..88282495 --- /dev/null +++ b/archives/extend/2013-September/000228.html @@ -0,0 +1,133 @@ + + + + [99s-extend] Cowboy load test + + + + + + + + + + +

[99s-extend] Cowboy load test

+ Loïc Hoguin + essen at ninenines.eu +
+ Sun Sep 15 21:02:35 CEST 2013 +

+
+ +
This sounds like you have too many timers, or something else is using 
+the CPU. 40k connections is literally nothing. Also make sure the 
+clients are on a separate VM/machine.
+
+Either way 99% CPU for 10k sounds high, I've had that with 0 CPU (though 
+on real hardware).
+
+Someone a couple years back got above 1 million after fixing 'too many 
+timers issues' but I don't think it was on a medium instance.
+
+On 09/15/2013 07:01 PM, Joe Freeman wrote:
+> Hi,
+>
+> I've started work on a project using Clojure, but I was wondering
+> whether (and secretly hoping that) Erlang would be a better fit, so I've
+> been load testing a few web server frameworks. I'm particularly
+> interested in how the server can handle a large number of concurrent
+> WebSocket connections, and the test I've been running is similar to Eric
+> Moritz's [1].
+>
+> I've setup a simple Cowboy 'echo' server running on an EC2 instance
+> (m1.medium, as in Eric's test) which could comfortably handle 10k
+> concurrent WebSocket requests (as in Eric's results), while echoing
+> about 200 messages/second. The CPU usage of the VM at this point is
+> about 99%, but the server continues to handle up to 40k concurrent
+> connections with a consistent average response time (<30ms). Pushing the
+> test beyond this number results in a spike in response times and lots of
+> connection timeouts.
+>
+> 40k connections seems pretty good, but when comparing this to the same
+> test against a couple of Clojure/JVM-based frameworks (specifically
+> Aleph/Netty and http-kit) I find I can get higher numbers of concurrent
+> connections with slightly better average response times (100k
+> connections, <10ms response time) using much less CPU (~20%). In fact,
+> memory seems to be the limiting factor.
+>
+> So I have two questions:
+>
+> 1) Should I be concerned about the CPU usage in the Erlang/Cowboy test?
+> I have limited experience with Erlang so far, but 100% CPU feels like a
+> bad thing.
+>
+> 2) Is there any way to increase the performance of the cowboy server?
+> Are there any Erlang VM parameters I can change? The fact that the
+> Clojure/JVM tests (on the same machine) have managed to get to 100k
+> connections suggests that the limitation isn't being imposed by the
+> operating system (I've applied changes various changes to sysctl and
+> ulimit).
+>
+> (Perhaps an echo server isn't the best way to compare HTTP servers, but
+> it feels like a good starting point.)
+>
+> Thanks for any help.
+>
+> [1] https://github.com/ericmoritz/wsdemo/blob/results-v1/results.md -
+> the GitHub repo actually contains code for an Aleph server, but results
+> from this aren't included in the summary here.
+>
+>
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/listinfo/extend
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000229.html b/archives/extend/2013-September/000229.html new file mode 100644 index 00000000..3b7176d5 --- /dev/null +++ b/archives/extend/2013-September/000229.html @@ -0,0 +1,143 @@ + + + + [99s-extend] Cowboy load test + + + + + + + + + + +

[99s-extend] Cowboy load test

+ Loïc Hoguin + essen at ninenines.eu +
+ Sun Sep 15 21:05:02 CEST 2013 +

+
+ +
This just hit me after hitting send.
+
+Another possibility is that you are using text frames which are required 
+to be valid UTF-8. Cowboy checks that (as required by the RFC), and it's 
+fairly expensive, while most other servers don't. Try with binary frames 
+instead.
+
+On 09/15/2013 09:02 PM, Loïc Hoguin wrote:
+> This sounds like you have too many timers, or something else is using
+> the CPU. 40k connections is literally nothing. Also make sure the
+> clients are on a separate VM/machine.
+>
+> Either way 99% CPU for 10k sounds high, I've had that with 0 CPU (though
+> on real hardware).
+>
+> Someone a couple years back got above 1 million after fixing 'too many
+> timers issues' but I don't think it was on a medium instance.
+>
+> On 09/15/2013 07:01 PM, Joe Freeman wrote:
+>> Hi,
+>>
+>> I've started work on a project using Clojure, but I was wondering
+>> whether (and secretly hoping that) Erlang would be a better fit, so I've
+>> been load testing a few web server frameworks. I'm particularly
+>> interested in how the server can handle a large number of concurrent
+>> WebSocket connections, and the test I've been running is similar to Eric
+>> Moritz's [1].
+>>
+>> I've setup a simple Cowboy 'echo' server running on an EC2 instance
+>> (m1.medium, as in Eric's test) which could comfortably handle 10k
+>> concurrent WebSocket requests (as in Eric's results), while echoing
+>> about 200 messages/second. The CPU usage of the VM at this point is
+>> about 99%, but the server continues to handle up to 40k concurrent
+>> connections with a consistent average response time (<30ms). Pushing the
+>> test beyond this number results in a spike in response times and lots of
+>> connection timeouts.
+>>
+>> 40k connections seems pretty good, but when comparing this to the same
+>> test against a couple of Clojure/JVM-based frameworks (specifically
+>> Aleph/Netty and http-kit) I find I can get higher numbers of concurrent
+>> connections with slightly better average response times (100k
+>> connections, <10ms response time) using much less CPU (~20%). In fact,
+>> memory seems to be the limiting factor.
+>>
+>> So I have two questions:
+>>
+>> 1) Should I be concerned about the CPU usage in the Erlang/Cowboy test?
+>> I have limited experience with Erlang so far, but 100% CPU feels like a
+>> bad thing.
+>>
+>> 2) Is there any way to increase the performance of the cowboy server?
+>> Are there any Erlang VM parameters I can change? The fact that the
+>> Clojure/JVM tests (on the same machine) have managed to get to 100k
+>> connections suggests that the limitation isn't being imposed by the
+>> operating system (I've applied changes various changes to sysctl and
+>> ulimit).
+>>
+>> (Perhaps an echo server isn't the best way to compare HTTP servers, but
+>> it feels like a good starting point.)
+>>
+>> Thanks for any help.
+>>
+>> [1] https://github.com/ericmoritz/wsdemo/blob/results-v1/results.md -
+>> the GitHub repo actually contains code for an Aleph server, but results
+>> from this aren't included in the summary here.
+>>
+>>
+>>
+>> _______________________________________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> http://lists.ninenines.eu:81/listinfo/extend
+>>
+>
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000230.html b/archives/extend/2013-September/000230.html new file mode 100644 index 00000000..365029b4 --- /dev/null +++ b/archives/extend/2013-September/000230.html @@ -0,0 +1,76 @@ + + + + [99s-extend] how to send a message to all connections in cowboy + + + + + + + + + + +

[99s-extend] how to send a message to all connections in cowboy

+ akonsu + akonsu at gmail.com +
+ Mon Sep 16 15:50:22 CEST 2013 +

+
+ +
Hello,
+
+this is somewhat similar to what someone else has asked:
+http://lists.ninenines.eu:81/archives/extend/2013-August/000224.html
+
+I am new to cowboy, I have a process that runs alongside a cowboy server
+and this process needs to periodically send text to all http clients
+connected to the cowboy server. My goal is to have a streaming connection
+for each http client so that I could stream text to them from my process.
+how is this done?
+
+Thanks!
+Konstantin
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130916/dedbf486/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000231.html b/archives/extend/2013-September/000231.html new file mode 100644 index 00000000..aa0fe981 --- /dev/null +++ b/archives/extend/2013-September/000231.html @@ -0,0 +1,85 @@ + + + + [99s-extend] how to send a message to all connections in cowboy + + + + + + + + + + +

[99s-extend] how to send a message to all connections in cowboy

+ Loïc Hoguin + essen at ninenines.eu +
+ Mon Sep 16 19:06:32 CEST 2013 +

+
+ +
On 09/16/2013 03:50 PM, akonsu wrote:
+> Hello,
+>
+> this is somewhat similar to what someone else has asked:
+> http://lists.ninenines.eu:81/archives/extend/2013-August/000224.html
+>
+> I am new to cowboy, I have a process that runs alongside a cowboy server
+> and this process needs to periodically send text to all http clients
+> connected to the cowboy server. My goal is to have a streaming
+> connection for each http client so that I could stream text to them from
+> my process. how is this done?
+
+Same answer really. You need some kind of process registry, like gproc 
+properties for example, that will store all Pids and allow you to send a 
+message to all of them.
+
+On init, register the process, and then handle the incoming message when 
+it arrives.
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000232.html b/archives/extend/2013-September/000232.html new file mode 100644 index 00000000..623d57ed --- /dev/null +++ b/archives/extend/2013-September/000232.html @@ -0,0 +1,99 @@ + + + + [99s-extend] how to send a message to all connections in cowboy + + + + + + + + + + +

[99s-extend] how to send a message to all connections in cowboy

+ akonsu + akonsu at gmail.com +
+ Mon Sep 16 19:14:24 CEST 2013 +

+
+ +
thanks. Suppose my external process is registered and has a name, so I can
+discover it by name from my cowboy request handler. when my cowboy handler
+is invoked, can I just send the handler's process ID to the external
+process? the question is then how does the external process know that the
+http client has disconnected so that it can stop sending data to it.
+
+
+2013/9/16 Loïc Hoguin <essen at ninenines.eu>
+
+> On 09/16/2013 03:50 PM, akonsu wrote:
+>
+>> Hello,
+>>
+>> this is somewhat similar to what someone else has asked:
+>> http://lists.ninenines.eu:81/**archives/extend/2013-August/**000224.html<http://lists.ninenines.eu:81/archives/extend/2013-August/000224.html>
+>>
+>> I am new to cowboy, I have a process that runs alongside a cowboy server
+>> and this process needs to periodically send text to all http clients
+>> connected to the cowboy server. My goal is to have a streaming
+>> connection for each http client so that I could stream text to them from
+>> my process. how is this done?
+>>
+>
+> Same answer really. You need some kind of process registry, like gproc
+> properties for example, that will store all Pids and allow you to send a
+> message to all of them.
+>
+> On init, register the process, and then handle the incoming message when
+> it arrives.
+>
+> --
+> Loďc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130916/f55d10f5/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000233.html b/archives/extend/2013-September/000233.html new file mode 100644 index 00000000..1ac511fd --- /dev/null +++ b/archives/extend/2013-September/000233.html @@ -0,0 +1,116 @@ + + + + [99s-extend] how to send a message to all connections in cowboy + + + + + + + + + + +

[99s-extend] how to send a message to all connections in cowboy

+ Loïc Hoguin + essen at ninenines.eu +
+ Mon Sep 16 19:19:59 CEST 2013 +

+
+ +
Monitors.
+
+But really gproc does all that for you and is already well tested.
+
+https://github.com/esl/gproc
+
+On 09/16/2013 07:14 PM, akonsu wrote:
+> thanks. Suppose my external process is registered and has a name, so I
+> can discover it by name from my cowboy request handler. when my cowboy
+> handler is invoked, can I just send the handler's process ID to the
+> external process? the question is then how does the external process
+> know that the http client has disconnected so that it can stop sending
+> data to it.
+>
+>
+> 2013/9/16 Loïc Hoguin <essen at ninenines.eu <mailto:essen at ninenines.eu>>
+>
+>     On 09/16/2013 03:50 PM, akonsu wrote:
+>
+>         Hello,
+>
+>         this is somewhat similar to what someone else has asked:
+>         http://lists.ninenines.eu:81/__archives/extend/2013-August/__000224.html
+>         <http://lists.ninenines.eu:81/archives/extend/2013-August/000224.html>
+>
+>         I am new to cowboy, I have a process that runs alongside a
+>         cowboy server
+>         and this process needs to periodically send text to all http clients
+>         connected to the cowboy server. My goal is to have a streaming
+>         connection for each http client so that I could stream text to
+>         them from
+>         my process. how is this done?
+>
+>
+>     Same answer really. You need some kind of process registry, like
+>     gproc properties for example, that will store all Pids and allow you
+>     to send a message to all of them.
+>
+>     On init, register the process, and then handle the incoming message
+>     when it arrives.
+>
+>     --
+>     Loďc Hoguin
+>     Erlang Cowboy
+>     Nine Nines
+>     http://ninenines.eu
+>
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000234.html b/archives/extend/2013-September/000234.html new file mode 100644 index 00000000..b282a715 --- /dev/null +++ b/archives/extend/2013-September/000234.html @@ -0,0 +1,77 @@ + + + + [99s-extend] cowboy_loop_handler + + + + + + + + + + +

[99s-extend] cowboy_loop_handler

+ akonsu + akonsu at gmail.com +
+ Thu Sep 19 06:30:57 CEST 2013 +

+
+ +
Hello,
+
+from the documentation:
+
+info(Info, Req, State) -> {ok, Req, State} | {loop, Req, State} | {loop,
+Req, State, hibernate}
+
+
+in case my handler receives a lot of messages, and they come very often,
+does a response of the latter form {loop, Req, State, hibernate} save
+anything? Can hibernating in this case actually hinder performance?
+
+thanks
+Konstantin
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130919/9614ef5e/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000235.html b/archives/extend/2013-September/000235.html new file mode 100644 index 00000000..cb8fdc7b --- /dev/null +++ b/archives/extend/2013-September/000235.html @@ -0,0 +1,97 @@ + + + + [99s-extend] cowboy_loop_handler + + + + + + + + + + +

[99s-extend] cowboy_loop_handler

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Sep 19 11:03:02 CEST 2013 +

+
+ +
How much is a lot of messages?
+
+Hibernating is a bit more expensive on the CPU but better for saving 
+memory. It's generally fine to use except when you have a really busy 
+system. Do note that it also means your responses will be slightly 
+slower (though that is generally not noticeable).
+
+On 09/19/2013 06:30 AM, akonsu wrote:
+> Hello,
+>
+> from the documentation:
+>
+> info(Info, Req, State) -> {ok, Req, State} | {loop, Req, State}| {loop,
+> Req, State, hibernate}
+>
+>
+> in case my handler receives a lot of messages, and they come very often,
+> does a response of the latter form {loop, Req, State, hibernate} save
+> anything? Can hibernating in this case actually hinder performance?
+>
+> thanks
+> Konstantin
+>
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/listinfo/extend
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000236.html b/archives/extend/2013-September/000236.html new file mode 100644 index 00000000..c45f3491 --- /dev/null +++ b/archives/extend/2013-September/000236.html @@ -0,0 +1,109 @@ + + + + [99s-extend] cowboy_loop_handler + + + + + + + + + + +

[99s-extend] cowboy_loop_handler

+ akonsu + akonsu at gmail.com +
+ Thu Sep 19 13:37:58 CEST 2013 +

+
+ +
my http handler receives messages carrying json parts obtained from a
+twitter stream by a separate process. the twitter stream is the stream of
+all public tweets, (they call it "firehose") so there are a lot.
+
+
+2013/9/19 Loïc Hoguin <essen at ninenines.eu>
+
+> How much is a lot of messages?
+>
+> Hibernating is a bit more expensive on the CPU but better for saving
+> memory. It's generally fine to use except when you have a really busy
+> system. Do note that it also means your responses will be slightly slower
+> (though that is generally not noticeable).
+>
+>
+> On 09/19/2013 06:30 AM, akonsu wrote:
+>
+>> Hello,
+>>
+>> from the documentation:
+>>
+>> info(Info, Req, State) -> {ok, Req, State} | {loop, Req, State}| {loop,
+>> Req, State, hibernate}
+>>
+>>
+>> in case my handler receives a lot of messages, and they come very often,
+>> does a response of the latter form {loop, Req, State, hibernate} save
+>> anything? Can hibernating in this case actually hinder performance?
+>>
+>> thanks
+>> Konstantin
+>>
+>>
+>> ______________________________**_________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend>
+>>
+>>
+>
+> --
+> Loďc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130919/0a4bcb6c/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000237.html b/archives/extend/2013-September/000237.html new file mode 100644 index 00000000..68c95fbb --- /dev/null +++ b/archives/extend/2013-September/000237.html @@ -0,0 +1,84 @@ + + + + [99s-extend] timeouts and slow clients in cowboy loop handler + + + + + + + + + + +

[99s-extend] timeouts and slow clients in cowboy loop handler

+ akonsu + akonsu at gmail.com +
+ Fri Sep 20 20:47:54 CEST 2013 +

+
+ +
Hi,
+
+I am using loop handler and I stream from it:
+
+info({stream, Part}, Req, S) ->
+    ok = cowboy_req:chunk(Part, Req),
+    {loop, Req, S, hibernate};
+
+I have two questions:
+
+1. on timeouts cowboy sends 204 No Content. In my case it is not the right
+response because I may have already sent some data. Is there a way to send
+a custom response?
+
+2. how to check if the client is too slow and is not reading the response
+stream fast enough? If this happens, then I need to disconnect.
+
+I can live without 1. but I need to figure out 2. Please help.
+
+thank you!
+Konstantin
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130920/6e3fa036/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000238.html b/archives/extend/2013-September/000238.html new file mode 100644 index 00000000..9a244158 --- /dev/null +++ b/archives/extend/2013-September/000238.html @@ -0,0 +1,105 @@ + + + + [99s-extend] timeouts and slow clients in cowboy loop handler + + + + + + + + + + +

[99s-extend] timeouts and slow clients in cowboy loop handler

+ Loïc Hoguin + essen at ninenines.eu +
+ Fri Sep 20 20:50:57 CEST 2013 +

+
+ +
Loop handlers close after a while regardless of what you send, it only 
+checks what the client sends. The best way for you would be to disable 
+that timeout and handle it manually.
+
+As for the second question, I'm still reading the thread on 
+erlang-questions but I've seen some good ideas about timestamps so far.
+
+On 09/20/2013 08:47 PM, akonsu wrote:
+> Hi,
+>
+> I am using loop handler and I stream from it:
+>
+> info({stream, Part}, Req, S) ->
+>      ok = cowboy_req:chunk(Part, Req),
+>      {loop, Req, S, hibernate};
+>
+> I have two questions:
+>
+> 1. on timeouts cowboy sends 204 No Content. In my case it is not the
+> right response because I may have already sent some data. Is there a way
+> to send a custom response?
+>
+> 2. how to check if the client is too slow and is not reading the
+> response stream fast enough? If this happens, then I need to disconnect.
+>
+> I can live without 1. but I need to figure out 2. Please help.
+>
+> thank you!
+> Konstantin
+>
+>
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/listinfo/extend
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000239.html b/archives/extend/2013-September/000239.html new file mode 100644 index 00000000..e9bb837c --- /dev/null +++ b/archives/extend/2013-September/000239.html @@ -0,0 +1,124 @@ + + + + [99s-extend] timeouts and slow clients in cowboy loop handler + + + + + + + + + + +

[99s-extend] timeouts and slow clients in cowboy loop handler

+ akonsu + akonsu at gmail.com +
+ Fri Sep 20 20:54:56 CEST 2013 +

+
+ +
thanks!
+
+how to implement timeout callback manually? if I had receive then I would
+just use timeout clause there, but with the handler I do not know...
+
+I have doubts about validity of my question on the erlang list.  I later
+realised that there is no problem receiving messages in my handler from my
+upstream process, I can do it fast enough and shove everything to the
+response. my real problem is to determine if the http client is reading
+fast enough from the response...
+
+
+2013/9/20 Loïc Hoguin <essen at ninenines.eu>
+
+> Loop handlers close after a while regardless of what you send, it only
+> checks what the client sends. The best way for you would be to disable that
+> timeout and handle it manually.
+>
+> As for the second question, I'm still reading the thread on
+> erlang-questions but I've seen some good ideas about timestamps so far.
+>
+>
+> On 09/20/2013 08:47 PM, akonsu wrote:
+>
+>> Hi,
+>>
+>> I am using loop handler and I stream from it:
+>>
+>> info({stream, Part}, Req, S) ->
+>>      ok = cowboy_req:chunk(Part, Req),
+>>      {loop, Req, S, hibernate};
+>>
+>> I have two questions:
+>>
+>> 1. on timeouts cowboy sends 204 No Content. In my case it is not the
+>> right response because I may have already sent some data. Is there a way
+>> to send a custom response?
+>>
+>> 2. how to check if the client is too slow and is not reading the
+>> response stream fast enough? If this happens, then I need to disconnect.
+>>
+>> I can live without 1. but I need to figure out 2. Please help.
+>>
+>> thank you!
+>> Konstantin
+>>
+>>
+>>
+>> ______________________________**_________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend>
+>>
+>>
+>
+> --
+> Loďc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130920/32352505/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000240.html b/archives/extend/2013-September/000240.html new file mode 100644 index 00000000..a5c5c8b3 --- /dev/null +++ b/archives/extend/2013-September/000240.html @@ -0,0 +1,140 @@ + + + + [99s-extend] timeouts and slow clients in cowboy loop handler + + + + + + + + + + +

[99s-extend] timeouts and slow clients in cowboy loop handler

+ Loïc Hoguin + essen at ninenines.eu +
+ Fri Sep 20 20:56:31 CEST 2013 +

+
+ +
chunk only returns when the client has received the chunk, so the 
+timestamps solution should work.
+
+As for the timeout, you can simply use erlang:send_after or something 
+like usual and the message will arrive in info/3.
+
+On 09/20/2013 08:54 PM, akonsu wrote:
+> thanks!
+>
+> how to implement timeout callback manually? if I had receive then I
+> would just use timeout clause there, but with the handler I do not know...
+>
+> I have doubts about validity of my question on the erlang list.  I later
+> realised that there is no problem receiving messages in my handler from
+> my upstream process, I can do it fast enough and shove everything to the
+> response. my real problem is to determine if the http client is reading
+> fast enough from the response...
+>
+>
+> 2013/9/20 Loïc Hoguin <essen at ninenines.eu <mailto:essen at ninenines.eu>>
+>
+>     Loop handlers close after a while regardless of what you send, it
+>     only checks what the client sends. The best way for you would be to
+>     disable that timeout and handle it manually.
+>
+>     As for the second question, I'm still reading the thread on
+>     erlang-questions but I've seen some good ideas about timestamps so far.
+>
+>
+>     On 09/20/2013 08:47 PM, akonsu wrote:
+>
+>         Hi,
+>
+>         I am using loop handler and I stream from it:
+>
+>         info({stream, Part}, Req, S) ->
+>               ok = cowboy_req:chunk(Part, Req),
+>               {loop, Req, S, hibernate};
+>
+>         I have two questions:
+>
+>         1. on timeouts cowboy sends 204 No Content. In my case it is not the
+>         right response because I may have already sent some data. Is
+>         there a way
+>         to send a custom response?
+>
+>         2. how to check if the client is too slow and is not reading the
+>         response stream fast enough? If this happens, then I need to
+>         disconnect.
+>
+>         I can live without 1. but I need to figure out 2. Please help.
+>
+>         thank you!
+>         Konstantin
+>
+>
+>
+>         _________________________________________________
+>         Extend mailing list
+>         Extend at lists.ninenines.eu <mailto:Extend at lists.ninenines.eu>
+>         http://lists.ninenines.eu:81/__listinfo/extend
+>         <http://lists.ninenines.eu:81/listinfo/extend>
+>
+>
+>
+>     --
+>     Loďc Hoguin
+>     Erlang Cowboy
+>     Nine Nines
+>     http://ninenines.eu
+>
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000241.html b/archives/extend/2013-September/000241.html new file mode 100644 index 00000000..da555d9a --- /dev/null +++ b/archives/extend/2013-September/000241.html @@ -0,0 +1,163 @@ + + + + [99s-extend] timeouts and slow clients in cowboy loop handler + + + + + + + + + + +

[99s-extend] timeouts and slow clients in cowboy loop handler

+ akonsu + akonsu at gmail.com +
+ Fri Sep 20 20:59:46 CEST 2013 +

+
+ +
Understand about chunks being synchronous. that helps me tremendously to
+understand how it works.
+
+would you give me a sketchy example of how to use send_after in a loop
+handler? (sorry I am new to erlang)
+
+Konstantin
+
+
+2013/9/20 Loïc Hoguin <essen at ninenines.eu>
+
+> chunk only returns when the client has received the chunk, so the
+> timestamps solution should work.
+>
+> As for the timeout, you can simply use erlang:send_after or something like
+> usual and the message will arrive in info/3.
+>
+>
+> On 09/20/2013 08:54 PM, akonsu wrote:
+>
+>> thanks!
+>>
+>> how to implement timeout callback manually? if I had receive then I
+>> would just use timeout clause there, but with the handler I do not know...
+>>
+>> I have doubts about validity of my question on the erlang list.  I later
+>> realised that there is no problem receiving messages in my handler from
+>> my upstream process, I can do it fast enough and shove everything to the
+>> response. my real problem is to determine if the http client is reading
+>> fast enough from the response...
+>>
+>>
+>> 2013/9/20 Loïc Hoguin <essen at ninenines.eu <mailto:essen at ninenines.eu>>
+>>
+>>
+>>     Loop handlers close after a while regardless of what you send, it
+>>     only checks what the client sends. The best way for you would be to
+>>     disable that timeout and handle it manually.
+>>
+>>     As for the second question, I'm still reading the thread on
+>>     erlang-questions but I've seen some good ideas about timestamps so
+>> far.
+>>
+>>
+>>     On 09/20/2013 08:47 PM, akonsu wrote:
+>>
+>>         Hi,
+>>
+>>         I am using loop handler and I stream from it:
+>>
+>>         info({stream, Part}, Req, S) ->
+>>               ok = cowboy_req:chunk(Part, Req),
+>>               {loop, Req, S, hibernate};
+>>
+>>         I have two questions:
+>>
+>>         1. on timeouts cowboy sends 204 No Content. In my case it is not
+>> the
+>>         right response because I may have already sent some data. Is
+>>         there a way
+>>         to send a custom response?
+>>
+>>         2. how to check if the client is too slow and is not reading the
+>>         response stream fast enough? If this happens, then I need to
+>>         disconnect.
+>>
+>>         I can live without 1. but I need to figure out 2. Please help.
+>>
+>>         thank you!
+>>         Konstantin
+>>
+>>
+>>
+>>         ______________________________**___________________
+>>         Extend mailing list
+>>         Extend at lists.ninenines.eu <mailto:Extend at lists.**ninenines.eu<Extend at lists.ninenines.eu>
+>> >
+>>         http://lists.ninenines.eu:81/_**_listinfo/extend<http://lists.ninenines.eu:81/__listinfo/extend>
+>>
+>>         <http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend>
+>> >
+>>
+>>
+>>
+>>     --
+>>     Loďc Hoguin
+>>     Erlang Cowboy
+>>     Nine Nines
+>>     http://ninenines.eu
+>>
+>>
+>>
+>
+> --
+> Loïc Hoguin
+>
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130920/4c005881/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000242.html b/archives/extend/2013-September/000242.html new file mode 100644 index 00000000..a9e2c705 --- /dev/null +++ b/archives/extend/2013-September/000242.html @@ -0,0 +1,191 @@ + + + + [99s-extend] timeouts and slow clients in cowboy loop handler + + + + + + + + + + +

[99s-extend] timeouts and slow clients in cowboy loop handler

+ Loïc Hoguin + essen at ninenines.eu +
+ Fri Sep 20 21:04:34 CEST 2013 +

+
+ +
send_after sends an Erlang message to a Pid after N milliseconds. It's 
+the same as Pid ! Message, except it's sent later. Send it to self().
+
+But if you're going to use timestamps then you probably don't need this 
+timeout, just check the timestamps and close when too slow.
+
+On 09/20/2013 08:59 PM, akonsu wrote:
+> Understand about chunks being synchronous. that helps me tremendously to
+> understand how it works.
+>
+> would you give me a sketchy example of how to use send_after in a loop
+> handler? (sorry I am new to erlang)
+>
+> Konstantin
+>
+>
+> 2013/9/20 Loïc Hoguin <essen at ninenines.eu <mailto:essen at ninenines.eu>>
+>
+>     chunk only returns when the client has received the chunk, so the
+>     timestamps solution should work.
+>
+>     As for the timeout, you can simply use erlang:send_after or
+>     something like usual and the message will arrive in info/3.
+>
+>
+>     On 09/20/2013 08:54 PM, akonsu wrote:
+>
+>         thanks!
+>
+>         how to implement timeout callback manually? if I had receive then I
+>         would just use timeout clause there, but with the handler I do
+>         not know...
+>
+>         I have doubts about validity of my question on the erlang list.
+>           I later
+>         realised that there is no problem receiving messages in my
+>         handler from
+>         my upstream process, I can do it fast enough and shove
+>         everything to the
+>         response. my real problem is to determine if the http client is
+>         reading
+>         fast enough from the response...
+>
+>
+>         2013/9/20 Loïc Hoguin <essen at ninenines.eu
+>         <mailto:essen at ninenines.eu> <mailto:essen at ninenines.eu
+>         <mailto:essen at ninenines.eu>>>
+>
+>
+>              Loop handlers close after a while regardless of what you
+>         send, it
+>              only checks what the client sends. The best way for you
+>         would be to
+>              disable that timeout and handle it manually.
+>
+>              As for the second question, I'm still reading the thread on
+>              erlang-questions but I've seen some good ideas about
+>         timestamps so far.
+>
+>
+>              On 09/20/2013 08:47 PM, akonsu wrote:
+>
+>                  Hi,
+>
+>                  I am using loop handler and I stream from it:
+>
+>                  info({stream, Part}, Req, S) ->
+>                        ok = cowboy_req:chunk(Part, Req),
+>                        {loop, Req, S, hibernate};
+>
+>                  I have two questions:
+>
+>                  1. on timeouts cowboy sends 204 No Content. In my case
+>         it is not the
+>                  right response because I may have already sent some
+>         data. Is
+>                  there a way
+>                  to send a custom response?
+>
+>                  2. how to check if the client is too slow and is not
+>         reading the
+>                  response stream fast enough? If this happens, then I
+>         need to
+>                  disconnect.
+>
+>                  I can live without 1. but I need to figure out 2.
+>         Please help.
+>
+>                  thank you!
+>                  Konstantin
+>
+>
+>
+>                  ___________________________________________________
+>                  Extend mailing list
+>         Extend at lists.ninenines.eu <mailto:Extend at lists.ninenines.eu>
+>         <mailto:Extend at lists.__ninenines.eu
+>         <mailto:Extend at lists.ninenines.eu>>
+>         http://lists.ninenines.eu:81/____listinfo/extend
+>         <http://lists.ninenines.eu:81/__listinfo/extend>
+>
+>                  <http://lists.ninenines.eu:81/__listinfo/extend
+>         <http://lists.ninenines.eu:81/listinfo/extend>>
+>
+>
+>
+>              --
+>              Loďc Hoguin
+>              Erlang Cowboy
+>              Nine Nines
+>         http://ninenines.eu
+>
+>
+>
+>
+>     --
+>     Loïc Hoguin
+>
+>     Erlang Cowboy
+>     Nine Nines
+>     http://ninenines.eu
+>
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000243.html b/archives/extend/2013-September/000243.html new file mode 100644 index 00000000..783433f9 --- /dev/null +++ b/archives/extend/2013-September/000243.html @@ -0,0 +1,66 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Matthew Hegarty + mrhegarty at gmail.com +
+ Sun Sep 22 22:55:31 CEST 2013 +

+
+ +
hi
+Just starting out so I've got latest versions of apps.
+in cowboy/examples/hello_world, running make fails with:
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130922/77e355ff/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000244.html b/archives/extend/2013-September/000244.html new file mode 100644 index 00000000..175e1b7a --- /dev/null +++ b/archives/extend/2013-September/000244.html @@ -0,0 +1,99 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Matthew Hegarty + mrhegarty at gmail.com +
+ Sun Sep 22 22:59:37 CEST 2013 +

+
+ +
hi
+Just starting out so I'm trying to run cowboy's helloworld
+in cowboy/examples/hello_world, running make fails with:
+
+===> Provider (rlx_prv_discover) failed with: {error,
+                                                      {rlx_app_discovery,
+                                                       [{missing_beam_file,
+                                                         hipe,
+
+<<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+                                                        {missing_beam_file,
+                                                         hipe,
+
+<<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+
+there is no hipe.beam in /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/, it is
+in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+I've tried passing the correct dir to relx using --lib-dir but I still get
+the same error.
+
+Any ideas what's going wrong?
+
+erl: Erlang R16B02 (erts-5.10.3)
+relx: 0.0.0+build.275.refca03701
+rebar: rebar 2.1.0-pre R16B02 20130922_191744 git 2.1.0-pre-46-g78fa8fc
+
+
+On 22 September 2013 21:55, Matthew Hegarty <mrhegarty at gmail.com> wrote:
+
+> hi
+> Just starting out so I've got latest versions of apps.
+> in cowboy/examples/hello_world, running make fails with:
+>
+>
+>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130922/6e925e9d/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000245.html b/archives/extend/2013-September/000245.html new file mode 100644 index 00000000..4912361a --- /dev/null +++ b/archives/extend/2013-September/000245.html @@ -0,0 +1,117 @@ + + + + [99s-extend] Cowboy: Having problems with Getting Started + + + + + + + + + + +

[99s-extend] Cowboy: Having problems with Getting Started

+ lloyd at writersglen.com + lloyd at writersglen.com +
+ Mon Sep 23 01:57:41 CEST 2013 +

+
+ +
Hello,
+
+Forgive my ignorance, but I'm having problems with the Getting Started chapter of the Cowboy Guide.
+
+Near the end I can download relx just fine. But there seems to be a hidden assumption shared, perhaps, by all Erlang cowboys but outside my understanding.
+
+When I get to $./relx, the following is returned:
+
+lloyd at Reliance:~/hello_erlang/relx$ ./relx
+===> Starting relx build process ...
+===> Resolving OTP Applications from directories:
+          /home/lloyd/hello_erlang/relx/ebin
+          /home/lloyd/hello_erlang/relx/deps
+          /usr/lib/erlang/lib
+
+===> Resolving available OTP Releases from directories:
+          /home/lloyd/hello_erlang/relx/ebin
+          /home/lloyd/hello_erlang/relx/deps
+          /usr/lib/erlang/lib
+
+Failed to solve release:
+ Dependency hello_erlang is specified as a dependency but is not reachable by the system.
+
+I've added all variations to .erlang that I can think of to put hello_erlang into the code path, but none seem to work. Can some kind soul let me in on the secret?
+
+Many thanks,
+
+Lloyd
+
+*********************************************
+My books:
+
+THE GOSPEL OF ASHES
+http://thegospelofashes.com
+
+Strength is not enough. Do they have the courage 
+and the cunning? Can they survive long enough to 
+save the lives of millions?  
+
+FREEIN' PANCHO
+http://freeinpancho.com
+
+A community of misfits help a troubled boy find his way 
+
+AYA TAKEO
+http://ayatakeo.com
+
+Star-crossed love, war and power in an alternative 
+universe
+
+Available through Amazon or by request from your 
+favorite bookstore
+
+
+**********************************************
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000246.html b/archives/extend/2013-September/000246.html new file mode 100644 index 00000000..90276dba --- /dev/null +++ b/archives/extend/2013-September/000246.html @@ -0,0 +1,117 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Loïc Hoguin + essen at ninenines.eu +
+ Wed Sep 25 17:09:16 CEST 2013 +

+
+ +
Why does it look for hipe at all to begin with?
+
+I'll ping tristan about it.
+
+On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+> hi
+> Just starting out so I'm trying to run cowboy's helloworld
+> in cowboy/examples/hello_world, running make fails with:
+>
+> ===> Provider (rlx_prv_discover) failed with: {error,
+>                                                        {rlx_app_discovery,
+>                                                         [{missing_beam_file,
+>                                                           hipe,
+>
+> <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+>                                                          {missing_beam_file,
+>                                                           hipe,
+>
+> <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+>
+> there is no hipe.beam in /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/, it
+> is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+> I've tried passing the correct dir to relx using --lib-dir but I still
+> get the same error.
+>
+> Any ideas what's going wrong?
+>
+> erl: Erlang R16B02 (erts-5.10.3)
+> relx: 0.0.0+build.275.refca03701
+> rebar: rebar 2.1.0-pre R16B02 20130922_191744 git 2.1.0-pre-46-g78fa8fc
+>
+>
+> On 22 September 2013 21:55, Matthew Hegarty <mrhegarty at gmail.com
+> <mailto:mrhegarty at gmail.com>> wrote:
+>
+>     hi
+>     Just starting out so I've got latest versions of apps.
+>     in cowboy/examples/hello_world, running make fails with:
+>
+>
+>
+>
+>
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/listinfo/extend
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000247.html b/archives/extend/2013-September/000247.html new file mode 100644 index 00000000..c5263d81 --- /dev/null +++ b/archives/extend/2013-September/000247.html @@ -0,0 +1,134 @@ + + + + [99s-extend] Cowboy: Having problems with Getting Started + + + + + + + + + + +

[99s-extend] Cowboy: Having problems with Getting Started

+ Loïc Hoguin + essen at ninenines.eu +
+ Wed Sep 25 17:10:01 CEST 2013 +

+
+ +
On 09/23/2013 01:57 AM, lloyd at writersglen.com wrote:
+> Hello,
+>
+> Forgive my ignorance, but I'm having problems with the Getting Started chapter of the Cowboy Guide.
+>
+> Near the end I can download relx just fine. But there seems to be a hidden assumption shared, perhaps, by all Erlang cowboys but outside my understanding.
+>
+> When I get to $./relx, the following is returned:
+>
+> lloyd at Reliance:~/hello_erlang/relx$ ./relx
+
+You're in hello_erlang/relx, I'm guessing you want to do that in 
+hello_erlang/ directly.
+
+> ===> Starting relx build process ...
+> ===> Resolving OTP Applications from directories:
+>            /home/lloyd/hello_erlang/relx/ebin
+>            /home/lloyd/hello_erlang/relx/deps
+>            /usr/lib/erlang/lib
+>
+> ===> Resolving available OTP Releases from directories:
+>            /home/lloyd/hello_erlang/relx/ebin
+>            /home/lloyd/hello_erlang/relx/deps
+>            /usr/lib/erlang/lib
+>
+> Failed to solve release:
+>   Dependency hello_erlang is specified as a dependency but is not reachable by the system.
+>
+> I've added all variations to .erlang that I can think of to put hello_erlang into the code path, but none seem to work. Can some kind soul let me in on the secret?
+>
+> Many thanks,
+>
+> Lloyd
+>
+> *********************************************
+> My books:
+>
+> THE GOSPEL OF ASHES
+> http://thegospelofashes.com
+>
+> Strength is not enough. Do they have the courage
+> and the cunning? Can they survive long enough to
+> save the lives of millions?
+>
+> FREEIN' PANCHO
+> http://freeinpancho.com
+>
+> A community of misfits help a troubled boy find his way
+>
+> AYA TAKEO
+> http://ayatakeo.com
+>
+> Star-crossed love, war and power in an alternative
+> universe
+>
+> Available through Amazon or by request from your
+> favorite bookstore
+>
+>
+> **********************************************
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/listinfo/extend
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000248.html b/archives/extend/2013-September/000248.html new file mode 100644 index 00000000..3d6dd723 --- /dev/null +++ b/archives/extend/2013-September/000248.html @@ -0,0 +1,141 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Tristan Sloughter + tristan.sloughter at gmail.com +
+ Wed Sep 25 18:25:04 CEST 2013 +

+
+ +
I ran into the same thing. I assume you installed Erlang from the Erlang
+Solutions repo?
+
+Install erlang-hipe package. Or remove
+/usr/local/lib/erlang/lib/hipe-3.10.2.1 entirely.
+
+Their packages install a broken hipe app, missing lots of beams, for
+some reason. But if you install the hipe package it'll install what is
+missing. I told them about this but I haven't heard back.
+
+-- 
+  Tristan Sloughter
+  tsloughter at fastmail.fm
+
+On Wed, Sep 25, 2013, at 08:09 AM, Loïc Hoguin wrote:
+> Why does it look for hipe at all to begin with?
+> 
+> I'll ping tristan about it.
+> 
+> On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+> > hi
+> > Just starting out so I'm trying to run cowboy's helloworld
+> > in cowboy/examples/hello_world, running make fails with:
+> >
+> > ===> Provider (rlx_prv_discover) failed with: {error,
+> >                                                        {rlx_app_discovery,
+> >                                                         [{missing_beam_file,
+> >                                                           hipe,
+> >
+> > <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+> >                                                          {missing_beam_file,
+> >                                                           hipe,
+> >
+> > <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+> >
+> > there is no hipe.beam in /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/, it
+> > is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+> > I've tried passing the correct dir to relx using --lib-dir but I still
+> > get the same error.
+> >
+> > Any ideas what's going wrong?
+> >
+> > erl: Erlang R16B02 (erts-5.10.3)
+> > relx: 0.0.0+build.275.refca03701
+> > rebar: rebar 2.1.0-pre R16B02 20130922_191744 git 2.1.0-pre-46-g78fa8fc
+> >
+> >
+> > On 22 September 2013 21:55, Matthew Hegarty <mrhegarty at gmail.com
+> > <mailto:mrhegarty at gmail.com>> wrote:
+> >
+> >     hi
+> >     Just starting out so I've got latest versions of apps.
+> >     in cowboy/examples/hello_world, running make fails with:
+> >
+> >
+> >
+> >
+> >
+> >
+> > _______________________________________________
+> > Extend mailing list
+> > Extend at lists.ninenines.eu
+> > http://lists.ninenines.eu:81/listinfo/extend
+> >
+> 
+> 
+> -- 
+> Loïc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/listinfo/extend
+
+
+-- 
+  Tristan Sloughter
+  tristan.sloughter at gmail.com
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000249.html b/archives/extend/2013-September/000249.html new file mode 100644 index 00000000..cc39f8fe --- /dev/null +++ b/archives/extend/2013-September/000249.html @@ -0,0 +1,72 @@ + + + + [99s-extend] Mailing lists maintenance 28th of September + + + + + + + + + + +

[99s-extend] Mailing lists maintenance 28th of September

+ Loïc Hoguin + essen at ninenines.eu +
+ Wed Sep 25 18:27:58 CEST 2013 +

+
+ +
Hello,
+
+Just a heads up, I will be moving the mailing lists to a new server 
+Saturday. As a result they might be unavailable for a couple hours/days 
+depending on how well I manage to do it.
+
+Thanks for your understanding!
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000250.html b/archives/extend/2013-September/000250.html new file mode 100644 index 00000000..75ceea7c --- /dev/null +++ b/archives/extend/2013-September/000250.html @@ -0,0 +1,155 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Matthew Hegarty + mrhegarty at gmail.com +
+ Thu Sep 26 21:03:06 CEST 2013 +

+
+ +
hi
+I compiled Erlang from source (downloaded from erlang.org)
+
+
+On 25 September 2013 17:25, Tristan Sloughter
+<tristan.sloughter at gmail.com>wrote:
+
+> I ran into the same thing. I assume you installed Erlang from the Erlang
+> Solutions repo?
+>
+> Install erlang-hipe package. Or remove
+> /usr/local/lib/erlang/lib/hipe-3.10.2.1 entirely.
+>
+> Their packages install a broken hipe app, missing lots of beams, for
+> some reason. But if you install the hipe package it'll install what is
+> missing. I told them about this but I haven't heard back.
+>
+> --
+>   Tristan Sloughter
+>   tsloughter at fastmail.fm
+>
+> On Wed, Sep 25, 2013, at 08:09 AM, Loïc Hoguin wrote:
+> > Why does it look for hipe at all to begin with?
+> >
+> > I'll ping tristan about it.
+> >
+> > On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+> > > hi
+> > > Just starting out so I'm trying to run cowboy's helloworld
+> > > in cowboy/examples/hello_world, running make fails with:
+> > >
+> > > ===> Provider (rlx_prv_discover) failed with: {error,
+> > >
+>  {rlx_app_discovery,
+> > >
+> [{missing_beam_file,
+> > >                                                           hipe,
+> > >
+> > > <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+> > >
+>  {missing_beam_file,
+> > >                                                           hipe,
+> > >
+> > > <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+> > >
+> > > there is no hipe.beam in /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/,
+> it
+> > > is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+> > > I've tried passing the correct dir to relx using --lib-dir but I still
+> > > get the same error.
+> > >
+> > > Any ideas what's going wrong?
+> > >
+> > > erl: Erlang R16B02 (erts-5.10.3)
+> > > relx: 0.0.0+build.275.refca03701
+> > > rebar: rebar 2.1.0-pre R16B02 20130922_191744 git 2.1.0-pre-46-g78fa8fc
+> > >
+> > >
+> > > On 22 September 2013 21:55, Matthew Hegarty <mrhegarty at gmail.com
+> > > <mailto:mrhegarty at gmail.com>> wrote:
+> > >
+> > >     hi
+> > >     Just starting out so I've got latest versions of apps.
+> > >     in cowboy/examples/hello_world, running make fails with:
+> > >
+> > >
+> > >
+> > >
+> > >
+> > >
+> > > _______________________________________________
+> > > Extend mailing list
+> > > Extend at lists.ninenines.eu
+> > > http://lists.ninenines.eu:81/listinfo/extend
+> > >
+> >
+> >
+> > --
+> > Loïc Hoguin
+> > Erlang Cowboy
+> > Nine Nines
+> > http://ninenines.eu
+> > _______________________________________________
+> > Extend mailing list
+> > Extend at lists.ninenines.eu
+> > http://lists.ninenines.eu:81/listinfo/extend
+>
+>
+> --
+>   Tristan Sloughter
+>   tristan.sloughter at gmail.com
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130926/d34b33e3/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000251.html b/archives/extend/2013-September/000251.html new file mode 100644 index 00000000..1bb672ae --- /dev/null +++ b/archives/extend/2013-September/000251.html @@ -0,0 +1,212 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Tristan Sloughter + tristan.sloughter at gmail.com +
+ Thu Sep 26 21:04:00 CEST 2013 +

+
+ +
Did you enable hipe when you compiled? Does
+/usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam exist?
+
+
+
+--
+Tristan Sloughter
+tristan.sloughter at gmail.com
+
+
+
+
+
+On Thu, Sep 26, 2013, at 12:03 PM, Matthew Hegarty wrote:
+
+hi
+
+I compiled Erlang from source (downloaded from [1]erlang.org)
+
+
+
+On 25 September 2013 17:25, Tristan Sloughter
+<[2]tristan.sloughter at gmail.com> wrote:
+
+I ran into the same thing. I assume you installed Erlang from the
+Erlang
+
+Solutions repo?
+
+
+
+Install erlang-hipe package. Or remove
+
+/usr/local/lib/erlang/lib/hipe-3.10.2.1 entirely.
+
+
+
+Their packages install a broken hipe app, missing lots of beams, for
+
+some reason. But if you install the hipe package it'll install what is
+
+missing. I told them about this but I haven't heard back.
+
+
+
+--
+
+  Tristan Sloughter
+
+  [3]tsloughter at fastmail.fm
+
+
+
+
+On Wed, Sep 25, 2013, at 08:09 AM, Loïc Hoguin wrote:
+> Why does it look for hipe at all to begin with?
+>
+> I'll ping tristan about it.
+>
+> On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+> > hi
+> > Just starting out so I'm trying to run cowboy's helloworld
+> > in cowboy/examples/hello_world, running make fails with:
+> >
+> > ===> Provider (rlx_prv_discover) failed with: {error,
+> >
+{rlx_app_discovery,
+> >
+[{missing_beam_file,
+> >                                                           hipe,
+> >
+> > <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+> >
+{missing_beam_file,
+> >                                                           hipe,
+> >
+> > <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+> >
+> > there is no hipe.beam in
+/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/, it
+> > is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+> > I've tried passing the correct dir to relx using --lib-dir but I
+still
+> > get the same error.
+> >
+> > Any ideas what's going wrong?
+> >
+> > erl: Erlang R16B02 (erts-5.10.3)
+> > relx: 0.0.0+build.275.refca03701
+> > rebar: rebar 2.1.0-pre R16B02 20130922_191744 git
+2.1.0-pre-46-g78fa8fc
+> >
+> >
+> > On 22 September 2013 21:55, Matthew Hegarty <[4]mrhegarty at gmail.com
+> > <mailto:[5]mrhegarty at gmail.com>> wrote:
+> >
+> >     hi
+> >     Just starting out so I've got latest versions of apps.
+> >     in cowboy/examples/hello_world, running make fails with:
+> >
+> >
+> >
+> >
+> >
+> >
+> > _______________________________________________
+> > Extend mailing list
+> > [6]Extend at lists.ninenines.eu
+> > [7]http://lists.ninenines.eu:81/listinfo/extend
+> >
+>
+>
+> --
+
+> Loïc Hoguin
+
+
+
+> Erlang Cowboy
+
+> Nine Nines
+
+> [8]http://ninenines.eu
+
+> _______________________________________________
+> Extend mailing list
+> [9]Extend at lists.ninenines.eu
+> [10]http://lists.ninenines.eu:81/listinfo/extend
+
+
+--
+
+  Tristan Sloughter
+
+  [11]tristan.sloughter at gmail.com
+
+References
+
+1. http://erlang.org/
+2. mailto:tristan.sloughter at gmail.com
+3. mailto:tsloughter at fastmail.fm
+4. mailto:mrhegarty at gmail.com
+5. mailto:mrhegarty at gmail.com
+6. mailto:Extend at lists.ninenines.eu
+7. http://lists.ninenines.eu:81/listinfo/extend
+8. http://ninenines.eu/
+9. mailto:Extend at lists.ninenines.eu
+  10. http://lists.ninenines.eu:81/listinfo/extend
+  11. mailto:tristan.sloughter at gmail.com
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130926/28d38e59/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000252.html b/archives/extend/2013-September/000252.html new file mode 100644 index 00000000..68aa9a1a --- /dev/null +++ b/archives/extend/2013-September/000252.html @@ -0,0 +1,188 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Matthew Hegarty + mrhegarty at gmail.com +
+ Thu Sep 26 22:36:03 CEST 2013 +

+
+ +
yes it exists.  I believe hipe is enabled by default when I compile.
+
+however there is no
+
+ /usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam
+ /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam
+
+which is what relx is apparently looking for.
+Do you know where does relx get these paths from?
+
+
+On 26 September 2013 20:04, Tristan Sloughter
+<tristan.sloughter at gmail.com>wrote:
+
+> **
+> Did you enable hipe when you compiled? Does
+> /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam exist?
+>
+> --
+>  Tristan Sloughter
+>  tristan.sloughter at gmail.com
+>
+>
+>
+> On Thu, Sep 26, 2013, at 12:03 PM, Matthew Hegarty wrote:
+>
+> hi
+> I compiled Erlang from source (downloaded from erlang.org)
+>
+>
+> On 25 September 2013 17:25, Tristan Sloughter <tristan.sloughter at gmail.com
+> > wrote:
+>
+>
+> I ran into the same thing. I assume you installed Erlang from the Erlang
+>  Solutions repo?
+>
+>  Install erlang-hipe package. Or remove
+>  /usr/local/lib/erlang/lib/hipe-3.10.2.1 entirely.
+>
+>  Their packages install a broken hipe app, missing lots of beams, for
+>  some reason. But if you install the hipe package it'll install what is
+>  missing. I told them about this but I haven't heard back.
+>
+>  --
+>    Tristan Sloughter
+>    tsloughter at fastmail.fm
+>
+>
+>  On Wed, Sep 25, 2013, at 08:09 AM, Loïc Hoguin wrote:
+>  > Why does it look for hipe at all to begin with?
+>  >
+>  > I'll ping tristan about it.
+>  >
+>  > On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+>  > > hi
+>  > > Just starting out so I'm trying to run cowboy's helloworld
+>  > > in cowboy/examples/hello_world, running make fails with:
+>  > >
+>  > > ===> Provider (rlx_prv_discover) failed with: {error,
+>  > >
+>  {rlx_app_discovery,
+>  > >
+> [{missing_beam_file,
+>  > >                                                           hipe,
+>  > >
+>  > > <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+>  > >
+>  {missing_beam_file,
+>  > >                                                           hipe,
+>  > >
+>  > > <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+>  > >
+>  > > there is no hipe.beam in /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/,
+> it
+>  > > is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+>  > > I've tried passing the correct dir to relx using --lib-dir but I still
+>  > > get the same error.
+>  > >
+>  > > Any ideas what's going wrong?
+>  > >
+>  > > erl: Erlang R16B02 (erts-5.10.3)
+>  > > relx: 0.0.0+build.275.refca03701
+>  > > rebar: rebar 2.1.0-pre R16B02 20130922_191744 git
+> 2.1.0-pre-46-g78fa8fc
+>  > >
+>  > >
+>  > > On 22 September 2013 21:55, Matthew Hegarty <mrhegarty at gmail.com
+>  > > <mailto:mrhegarty at gmail.com>> wrote:
+>  > >
+>  > >     hi
+>  > >     Just starting out so I've got latest versions of apps.
+>  > >     in cowboy/examples/hello_world, running make fails with:
+>  > >
+>  > >
+>  > >
+>  > >
+>  > >
+>  > >
+>  > > _______________________________________________
+>  > > Extend mailing list
+>  > > Extend at lists.ninenines.eu
+>  > > http://lists.ninenines.eu:81/listinfo/extend
+>  > >
+>  >
+>  >
+>  > --
+>  > Loïc Hoguin
+>
+> > Erlang Cowboy
+>  > Nine Nines
+>  > http://ninenines.eu
+> > _______________________________________________
+>  > Extend mailing list
+>  > Extend at lists.ninenines.eu
+>  > http://lists.ninenines.eu:81/listinfo/extend
+>
+>
+>  --
+>    Tristan Sloughter
+>    tristan.sloughter at gmail.com
+>
+>
+>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130926/3a77fe04/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000253.html b/archives/extend/2013-September/000253.html new file mode 100644 index 00000000..168be8bc --- /dev/null +++ b/archives/extend/2013-September/000253.html @@ -0,0 +1,210 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Matthew Hegarty + mrhegarty at gmail.com +
+ Sat Sep 28 22:41:16 CEST 2013 +

+
+ +
Got it to work.  I apparently had a few versions of hipe in my Erlang lib
+dir:
+
+$ /usr/local/lib/erlang/lib $ ll -ld hipe*
+drwxr-xr-x  9 root root 4096 Feb 11  2013 hipe-3.10/
+drwxr-xr-x  9 root root 4096 Mar  1  2013 hipe-3.10.1/
+drwxr-xr-x 10 root root 4096 Jul  2 11:31 hipe-3.10.2/
+drwxr-xr-x 10 root root 4096 Sep 21 17:36 hipe-3.10.2.1/
+
+They must have come from previous erlang installations (compilation from
+source).  The solution was to remove the older versions and leave only the
+latest one.  Maybe relx should be able to handle this?
+
+thanks for the responses
+
+Matt
+
+
+On 26 September 2013 21:36, Matthew Hegarty <mrhegarty at gmail.com> wrote:
+
+> yes it exists.  I believe hipe is enabled by default when I compile.
+>
+> however there is no
+>
+>  /usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam
+>  /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam
+>
+> which is what relx is apparently looking for.
+> Do you know where does relx get these paths from?
+>
+>
+> On 26 September 2013 20:04, Tristan Sloughter <tristan.sloughter at gmail.com
+> > wrote:
+>
+>> **
+>> Did you enable hipe when you compiled? Does
+>> /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam exist?
+>>
+>> --
+>>  Tristan Sloughter
+>>  tristan.sloughter at gmail.com
+>>
+>>
+>>
+>> On Thu, Sep 26, 2013, at 12:03 PM, Matthew Hegarty wrote:
+>>
+>> hi
+>> I compiled Erlang from source (downloaded from erlang.org)
+>>
+>>
+>> On 25 September 2013 17:25, Tristan Sloughter <
+>> tristan.sloughter at gmail.com> wrote:
+>>
+>>
+>> I ran into the same thing. I assume you installed Erlang from the Erlang
+>>  Solutions repo?
+>>
+>>  Install erlang-hipe package. Or remove
+>>  /usr/local/lib/erlang/lib/hipe-3.10.2.1 entirely.
+>>
+>>  Their packages install a broken hipe app, missing lots of beams, for
+>>  some reason. But if you install the hipe package it'll install what is
+>>  missing. I told them about this but I haven't heard back.
+>>
+>>  --
+>>    Tristan Sloughter
+>>    tsloughter at fastmail.fm
+>>
+>>
+>>  On Wed, Sep 25, 2013, at 08:09 AM, Loïc Hoguin wrote:
+>>  > Why does it look for hipe at all to begin with?
+>>  >
+>>  > I'll ping tristan about it.
+>>  >
+>>  > On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+>>  > > hi
+>>  > > Just starting out so I'm trying to run cowboy's helloworld
+>>  > > in cowboy/examples/hello_world, running make fails with:
+>>  > >
+>>  > > ===> Provider (rlx_prv_discover) failed with: {error,
+>>  > >
+>>  {rlx_app_discovery,
+>>  > >
+>> [{missing_beam_file,
+>>  > >                                                           hipe,
+>>  > >
+>>  > > <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+>>  > >
+>>  {missing_beam_file,
+>>  > >                                                           hipe,
+>>  > >
+>>  > > <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+>>  > >
+>>  > > there is no hipe.beam in
+>> /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/, it
+>>  > > is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+>>  > > I've tried passing the correct dir to relx using --lib-dir but I
+>> still
+>>  > > get the same error.
+>>  > >
+>>  > > Any ideas what's going wrong?
+>>  > >
+>>  > > erl: Erlang R16B02 (erts-5.10.3)
+>>  > > relx: 0.0.0+build.275.refca03701
+>>  > > rebar: rebar 2.1.0-pre R16B02 20130922_191744 git
+>> 2.1.0-pre-46-g78fa8fc
+>>  > >
+>>  > >
+>>  > > On 22 September 2013 21:55, Matthew Hegarty <mrhegarty at gmail.com
+>>  > > <mailto:mrhegarty at gmail.com>> wrote:
+>>  > >
+>>  > >     hi
+>>  > >     Just starting out so I've got latest versions of apps.
+>>  > >     in cowboy/examples/hello_world, running make fails with:
+>>  > >
+>>  > >
+>>  > >
+>>  > >
+>>  > >
+>>  > >
+>>  > > _______________________________________________
+>>  > > Extend mailing list
+>>  > > Extend at lists.ninenines.eu
+>>  > > http://lists.ninenines.eu:81/listinfo/extend
+>>  > >
+>>  >
+>>  >
+>>  > --
+>>  > Loïc Hoguin
+>>
+>> > Erlang Cowboy
+>>  > Nine Nines
+>>  > http://ninenines.eu
+>> > _______________________________________________
+>>  > Extend mailing list
+>>  > Extend at lists.ninenines.eu
+>>  > http://lists.ninenines.eu:81/listinfo/extend
+>>
+>>
+>>  --
+>>    Tristan Sloughter
+>>    tristan.sloughter at gmail.com
+>>
+>>
+>>
+>>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130928/b1333ac2/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/000254.html b/archives/extend/2013-September/000254.html new file mode 100644 index 00000000..9e3ffb6a --- /dev/null +++ b/archives/extend/2013-September/000254.html @@ -0,0 +1,269 @@ + + + + [99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe) + + + + + + + + + + +

[99s-extend] Cowboy helloworld make fails with missing_beam_file (hipe)

+ Tristan Sloughter + tristan.sloughter at gmail.com +
+ Sat Sep 28 22:43:25 CEST 2013 +

+
+ +
Yea, since I doubt the OTP team (or anyone) will fix the fact that it
+installs a broken hipe we've decided to just warn on broken apps during
+the discovery phase. So it'll only fail if the broken app is also
+suppose to be part of the release.
+
+
+
+Finishing up the relx patch right now.
+
+
+
+--
+Tristan Sloughter
+tristan.sloughter at gmail.com
+
+
+
+
+
+On Sat, Sep 28, 2013, at 01:41 PM, Matthew Hegarty wrote:
+
+Got it to work.  I apparently had a few versions of hipe in my Erlang
+lib dir:
+
+$ /usr/local/lib/erlang/lib $ ll -ld hipe*
+drwxr-xr-x  9 root root 4096 Feb 11  2013 hipe-3.10/
+drwxr-xr-x  9 root root 4096 Mar  1  2013 hipe-3.10.1/
+drwxr-xr-x 10 root root 4096 Jul  2 11:31 hipe-3.10.2/
+drwxr-xr-x 10 root root 4096 Sep 21 17:36 hipe-3.10.2.1/
+
+They must have come from previous erlang installations (compilation
+from source).  The solution was to remove the older versions and leave
+only the latest one.  Maybe relx should be able to handle this?
+
+thanks for the responses
+
+Matt
+
+
+
+On 26 September 2013 21:36, Matthew Hegarty <[1]mrhegarty at gmail.com>
+wrote:
+
+yes it exists.  I believe hipe is enabled by default when I compile.
+
+however there is no
+
+ /usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam
+ /usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam
+
+which is what relx is apparently looking for.
+Do you know where does relx get these paths from?
+
+
+
+On 26 September 2013 20:04, Tristan Sloughter
+<[2]tristan.sloughter at gmail.com> wrote:
+
+Did you enable hipe when you compiled? Does
+/usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam exist?
+
+--
+Tristan Sloughter
+[3]tristan.sloughter at gmail.com
+
+
+
+On Thu, Sep 26, 2013, at 12:03 PM, Matthew Hegarty wrote:
+
+hi
+
+I compiled Erlang from source (downloaded from [4]erlang.org)
+
+
+
+On 25 September 2013 17:25, Tristan Sloughter
+<[5]tristan.sloughter at gmail.com> wrote:
+
+I ran into the same thing. I assume you installed Erlang from the
+Erlang
+
+Solutions repo?
+
+
+
+Install erlang-hipe package. Or remove
+
+/usr/local/lib/erlang/lib/hipe-3.10.2.1 entirely.
+
+
+
+Their packages install a broken hipe app, missing lots of beams, for
+
+some reason. But if you install the hipe package it'll install what is
+
+missing. I told them about this but I haven't heard back.
+
+
+
+--
+
+  Tristan Sloughter
+
+  [6]tsloughter at fastmail.fm
+
+
+
+
+On Wed, Sep 25, 2013, at 08:09 AM, Loïc Hoguin wrote:
+> Why does it look for hipe at all to begin with?
+>
+> I'll ping tristan about it.
+>
+> On 09/22/2013 10:59 PM, Matthew Hegarty wrote:
+> > hi
+> > Just starting out so I'm trying to run cowboy's helloworld
+> > in cowboy/examples/hello_world, running make fails with:
+> >
+> > ===> Provider (rlx_prv_discover) failed with: {error,
+> >
+{rlx_app_discovery,
+> >
+[{missing_beam_file,
+> >                                                           hipe,
+> >
+> > <<"/usr/local/lib/erlang/lib/hipe-3.10/ebin/hipe.beam">>},
+> >
+{missing_beam_file,
+> >                                                           hipe,
+> >
+> > <<"/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/hipe.beam">>}]}}
+> >
+> > there is no hipe.beam in
+/usr/local/lib/erlang/lib/hipe-3.10.1/ebin/, it
+> > is in /usr/local/lib/erlang/lib/hipe-3.10.2.1/ebin/hipe.beam.
+> > I've tried passing the correct dir to relx using --lib-dir but I
+still
+> > get the same error.
+> >
+> > Any ideas what's going wrong?
+> >
+> > erl: Erlang R16B02 (erts-5.10.3)
+> > relx: 0.0.0+build.275.refca03701
+> > rebar: rebar 2.1.0-pre R16B02 20130922_191744 git
+2.1.0-pre-46-g78fa8fc
+> >
+> >
+> > On 22 September 2013 21:55, Matthew Hegarty <[7]mrhegarty at gmail.com
+> > <mailto:[8]mrhegarty at gmail.com>> wrote:
+> >
+> >     hi
+> >     Just starting out so I've got latest versions of apps.
+> >     in cowboy/examples/hello_world, running make fails with:
+> >
+> >
+> >
+> >
+> >
+> >
+> > _______________________________________________
+> > Extend mailing list
+> > [9]Extend at lists.ninenines.eu
+> > [10]http://lists.ninenines.eu:81/listinfo/extend
+> >
+>
+>
+> --
+
+> Loïc Hoguin
+
+
+
+> Erlang Cowboy
+
+> Nine Nines
+
+> [11]http://ninenines.eu
+
+> _______________________________________________
+> Extend mailing list
+> [12]Extend at lists.ninenines.eu
+> [13]http://lists.ninenines.eu:81/listinfo/extend
+
+
+--
+
+  Tristan Sloughter
+
+  [14]tristan.sloughter at gmail.com
+
+References
+
+1. mailto:mrhegarty at gmail.com
+2. mailto:tristan.sloughter at gmail.com
+3. mailto:tristan.sloughter at gmail.com
+4. http://erlang.org/
+5. mailto:tristan.sloughter at gmail.com
+6. mailto:tsloughter at fastmail.fm
+7. mailto:mrhegarty at gmail.com
+8. mailto:mrhegarty at gmail.com
+9. mailto:Extend at lists.ninenines.eu
+  10. http://lists.ninenines.eu:81/listinfo/extend
+  11. http://ninenines.eu/
+  12. mailto:Extend at lists.ninenines.eu
+  13. http://lists.ninenines.eu:81/listinfo/extend
+  14. mailto:tristan.sloughter at gmail.com
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130928/41b322fd/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-September/author.html b/archives/extend/2013-September/author.html new file mode 100644 index 00000000..97404d5d --- /dev/null +++ b/archives/extend/2013-September/author.html @@ -0,0 +1,187 @@ + + + + The Extend September 2013 Archive by author + + + + + +

September 2013 Archives by author

+ +

Starting: Sun Sep 15 19:01:30 CEST 2013
+ Ending: Sat Sep 28 22:43:25 CEST 2013
+ Messages: 28

+

+

+ Last message date: + Sat Sep 28 22:43:25 CEST 2013
+ Archived on: Wed May 28 18:41:45 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-September/date.html b/archives/extend/2013-September/date.html new file mode 100644 index 00000000..ccbd2574 --- /dev/null +++ b/archives/extend/2013-September/date.html @@ -0,0 +1,187 @@ + + + + The Extend September 2013 Archive by date + + + + + +

September 2013 Archives by date

+ +

Starting: Sun Sep 15 19:01:30 CEST 2013
+ Ending: Sat Sep 28 22:43:25 CEST 2013
+ Messages: 28

+

+

+ Last message date: + Sat Sep 28 22:43:25 CEST 2013
+ Archived on: Wed May 28 18:41:45 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-September/index.html b/archives/extend/2013-September/index.html new file mode 100644 index 00000000..8366d4d0 --- /dev/null +++ b/archives/extend/2013-September/index.html @@ -0,0 +1,243 @@ + + + + The Extend September 2013 Archive by thread + + + + + +

September 2013 Archives by thread

+ +

Starting: Sun Sep 15 19:01:30 CEST 2013
+ Ending: Sat Sep 28 22:43:25 CEST 2013
+ Messages: 28

+

+

+ Last message date: + Sat Sep 28 22:43:25 CEST 2013
+ Archived on: Wed May 28 18:41:45 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-September/subject.html b/archives/extend/2013-September/subject.html new file mode 100644 index 00000000..835ec2ec --- /dev/null +++ b/archives/extend/2013-September/subject.html @@ -0,0 +1,187 @@ + + + + The Extend September 2013 Archive by subject + + + + + +

September 2013 Archives by subject

+ +

Starting: Sun Sep 15 19:01:30 CEST 2013
+ Ending: Sat Sep 28 22:43:25 CEST 2013
+ Messages: 28

+

+

+ Last message date: + Sat Sep 28 22:43:25 CEST 2013
+ Archived on: Wed May 28 18:41:45 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-September/thread.html b/archives/extend/2013-September/thread.html new file mode 100644 index 00000000..8366d4d0 --- /dev/null +++ b/archives/extend/2013-September/thread.html @@ -0,0 +1,243 @@ + + + + The Extend September 2013 Archive by thread + + + + + +

September 2013 Archives by thread

+ +

Starting: Sun Sep 15 19:01:30 CEST 2013
+ Ending: Sat Sep 28 22:43:25 CEST 2013
+ Messages: 28

+

+

+ Last message date: + Sat Sep 28 22:43:25 CEST 2013
+ Archived on: Wed May 28 18:41:45 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.3