Re: [akka-user] HTTP server performance

[Mike Nielsen]

Did you try it on a new instance of the same size?

At my work we occasionally see EC2 instances start getting really poor
performance.

When we replace them with a new instance (same instance type) performance
comes back.

On Mon, Feb 19, 2018 at 5:30 PM, Mirek Suk  wrote:

> Hi everyone.
>
> AKKA 2.5.9 / HTTP 10.0.11
>
> As part of prototyping architecture, I ran some benchmarks (including
> http) few months ago.
> A simple hello world (request handler is completed with result
> immediately) had nice performance ~2.7m requests/minute. with 1,6m r/m when
> response included ask to sharded actor.
>
> Recently I re-did those benchmarks to find out around ~9x performance drop
> on original test system.
> Rolled prototype back to point of original test with similar result.
> Built scala http sample with similar result.
> Reinstalled JVM with similar result.
> Randomly got performance back, until system restart (yeah like what ?)
>
> On EC2-T2.medium I can do ~7k req/s to "hello world" page with 100% CPU
> usage (2 cores).
> No akka.http configuration is changed and system does no background
> processing.
> Default dispatcher is unchanged (only due to clustering throughput = 10).
>
> Is this kind of performance expected ?
> Is there something I can try ?
>
> Thanks,
> M.
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] New Documentation

[Mike Nielsen]

I'm sure it is for all but those of us like me who are intensely lazy.

I just thought it would be handy to have the nav header version in the
reference link to the API docs.

No biggie, really.

Again, let me congratulate you on the new site.  I think it's outstanding,
and I am very excited about the possibility that there may be more runnable
examples using ScalaFiddle!

Well done and thank you for taking the time on a Sunday to reply!

Warm regards,

Mike

On Sun, May 28, 2017 at 9:33 AM, Patrik Nordwall <patrik.nordw...@gmail.com>
wrote:

> Thanks. Our thinking was that http://akka.io/docs/ would be the landing
> page for all docs including such links. Not enough?
>
> /Patrik
> sön 28 maj 2017 kl. 15:26 skrev Mike Nielsen <mnielsen...@gmail.com>:
>
>> Congratulations, team, on the new Akka documentation site.  It looks good!
>>
>> By way of a minor enhancement, would it be possible to put a link to the
>> API documentation in an easy-to-find place so that those of us with poor
>> memories may find it more easily?
>>
>> Thanks!
>>
>> --
>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
>> current/additional/faq.html
>> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to akka-user+unsubscr...@googlegroups.com.
>> To post to this group, send email to akka-user@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>>>>>>>>>  Read the docs: http://akka.io/docs/
>>>>>>>>>>  Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: New Documentation

[Mike Nielsen]

I should have qualified my request -- I meant specifically from the
Reference.  It would be nice to have a link on the reference page to the
API docs.

Once you're into the "reference" you have to go back to the top-level
documentation to find the link to the API docs.

I know, I'm lazy...

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] New Documentation

[Mike Nielsen]

Congratulations, team, on the new Akka documentation site.  It looks good!

By way of a minor enhancement, would it be possible to put a link to the
API documentation in an easy-to-find place so that those of us with poor
memories may find it more easily?

Thanks!

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: I'm a freshman to Akka, please recommend me some useful learning material... Thanks a lot.

[Mike Nielsen]

If I may be permitted to chime in here with my $0.02, some observations as
an Akka bootstrapper:

Everybody has their own learning style -- some people I know can read even
a fairly dense API spec and start writing code.  Personally, I need to get
started on a problem-solving basis so in the early days:  I'm more of a
monkey-see-monkey-do person, taking existing code and trying to shape it to
fit my particular use-case.

For learners like me some of the examples of code are a little terse --
they don't show enough context.  Looking at them in retrospect, they are
adequate, but in prospect they can be a little obscure.

While I haven't yet the skill to construct them myself (I'm an akka
hobbyist, not a professional), what might be useful is to draw the code
examples from a working code-base so they can be seen in the context of a
project the student can build and run.  Many of the official Java tutorials
do this reasonably well.  I know there are some good Activator samples
available, but they don't correspond to the examples in the Akka
documentation and their internal documentation can be rather sparse.

The Activator samples, once you understand them, are very clever, but the
cleverness can obscure the basics.  An analogy: I love a good proof in
mathematics and can appreciate the elegance and beauty therein, but
understanding a proof and gleaning generalizable skill from it can be two
different things. What makes the proof a good learning tool (for people
like me) is an explanation of the motivation and methods that went into its
derivation.  Something similar for code samples would be very helpful.

Also, in some of the examples it can be a little hard to distinguish
between those aspects of the code that are essential to the point being
made and those that are not but nonetheless required to make compilable
code -- detailed explanations of the examples would go a long way to
enhancing their illustrative value.

I feel bad suggesting work for others to do, and my suggestions might be
out of the scope of what's intended for the documentation, but I hope you
can sympathize with my position: I'm not yet sufficiently knowledgable to
be writing books or tutorials, and offer my comments in response to your
interest in improving the Akka experience for novices.

Thank you for your patience in reading this.

Regards,

Mike

On Thu, Jan 19, 2017 at 3:07 PM, Josep Prat  wrote:

> As former participant of that course, I think they would be a great
> addition to the current documentation assets. But I'm still interested in
> what the OP thinks it would improve a freshman experience.
>
> Best,
> Josep
>
> On Thursday, January 19, 2017 at 8:59:53 PM UTC+1, rkuhn wrote:
>>
>> While “terrible” is pretty strong wording I think it is fair to say that
>> Akka has very good reference documentation but its initial learning
>> experience can be improved. Would it help if some of the video courses were
>> available (for free, of course) that were part of Principles of Reactive
>> Programming?
>>
>> Regards, Roland
>>
>> Sent from my iPhone
>>
>> On 19 Jan 2017, at 20:41, Josep Prat  wrote:
>>
>> Welcome to Akka!
>> As Lutz already said, I would recommend "Akka in Action". The only catch
>> is that the code is mainly in Scala.
>> I have a question though, why do you say the official documentation is
>> terrible? I personally find Akka docs quite good. What would you change/add
>> to the current ones?
>>
>> Best,
>> Josep
>>
>> On Thursday, January 19, 2017 at 2:34:29 PM UTC+1, Qian Liu wrote:
>>>
>>> Hello everybody,
>>>
>>> I'm new-comer to Akka, the official documents for Akka learning is
>>> terrible. not very well structured. Beginners will soon feel lost with
>>> these official documents. Do you know any better resources to learn? I'm a
>>> java developer.
>>>
>>> Thanks a lot.
>>>
>>> Best regards,
>>>
>>> Qian Liu
>>>
>> --
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: http://doc.akka.io/docs/akka/c
>> urrent/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to akka-user+...@googlegroups.com.
>> To post to this group, send email to akka...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 

Re: [akka-user] Line count of each file in a given directory efficiently using akka

[Mike Nielsen]

While I'm far from an expert, and have never deployed Akka in production
(so take my advice with a grain of salt, and please don't hear this as any
criticism of what you've done) I use routers for a few of reasons:

   1. I can control the minimum and maximum numbers of them via
   configuration, and there are some pool configurations that are sensitive to
   workload on the node, so you won't whack the compute node(s) too hard;
   2. You can configure worker instances to be run remotely, which means
   that it's easier to scale horizontally if need be;
   3. In my view, it's worthwhile to have explicit management of actors (as
   opposed to just spinning them up willy-nilly): I can foresee a risk in
   writing a large system where execution contexts become a mixed-bag of
   actors with a broad spectrum of performance characteristics.  Trolling
   through the code later to try to tune performance by partitioning execution
   contexts is harder than having these designed up-front.  In your
   application, this may not be such a big deal, but, for reasons of personal
   preference, I try to avoid coding in a way that boxes me in scale-wise.
   Admittedly it's more work, but my thinking is that while I'm learning, I
   may as well learn it to the max.  Your mileage, of course, may vary.
   4. In a larger application, it also seems to me to be a risk that
   business logic might become sprayed over actors in a way that makes the
   code a pain to maintain.  I'm not sure I have a complete answer on managing
   that, but it seems that a central manifest of actors (in the form of router
   configurations) in your configuration files might be of benefit.

In terms of whether it's OK to have a single actor per file, that seems to
be a tacit design decision that says I/O throughput is going to be the
factor that limits your application throughput.  If that's always going to
be the case, then fine, but if you are going to want to get a high degree
of scalability, that may not be a correct assumption: if you have massive
files and a distributed filesystem in which I/O throughput scales with the
number of compute nodes, then it may be better to work out how to partition
work on a single file over multiple nodes.

As one beginner to another, I have found a couple of features of Akka that
are worthwhile:

   1. While not directly related to your questions, FSM's are amazingly
   helpful in writing correct code, and therein may lie the answer to your
   third query;
   2. I found streams a little tricker to get the hang of than vanilla
   actors, but worth the investment of time.

I hope you find these comments useful.

On Wed, Nov 23, 2016 at 5:25 AM, kk k  wrote:

>
> This is my first program in akka so I wanted to know if the below program
> is efficient and is using the advantages of actor model.
>
> --
>
> The program's purpose is to scan a given directory for any files and print
> the number of lines in each file.
>
> 1. The main `Application` class will create the actor system and send a
> Scan message to a `FileScanner` actor.
> 2. The `FileScanner` actor will scan the given directory, and for each
> file it will create a new `FileParser` actor and send a Parse message.
> Also, all the fileparser actors are passed the same Aggregator actor
> Reference.
> 3. The `FileParser` actor will parse the given file, and for each line it
> will send a Line message to the Aggregator Actor.
> 4. The `Aggregator` actor will maintain a count of the number of lines for
> each file in an instance hashmap and will print the line count for each
> "End" message it receives. Once all files are processed, it will shutdown
> the actor system.
>
> --
>
> A few points which I need help on:
>
> 1. There is a separate `FileParser` actor for each file. Is this fine?
> What is the benefit of using a router which routes to FileParser actor?
> Will its use only help in controlling the number of fileparser actors and
> also how load is distributed among these actors?
>
> 2. There is a single Aggregator actor which counts the number of lines for
> each file. It's using an instance `HashMap` and I hope this is fine. Or
> will a separate aggregator actor for each file improve performance?
>
> 3. Also, I am passing the number of files to Aggregator actor while it's
> created so that I can shutdown the actor system once all files are
> processed. If I have a separate Aggregator for each file, I'm not sure how
> to shutdown.
>
> 4. Each file is only sequentially processed i.e a `FileParser` actor is
> reading the file sequentially and and then invoking aggregator for each
> line. Is this fine or can it be improved.
>
> --
>
> **Application**
>
> /**
> * The Application program bootstraps the actorsystem for parsing files in a
> * given directory and finding their linecount
> *
> * @author
> * @version 1.0
> */
> public class Application {
> public void start(String directoryPath) {
> ActorSystem 

Re: [akka-user] Failing to see router configuration when using context.ActorOf(FromConfig.props(Props[LogWorker]),"logWorker")

[Mike Nielsen]

The double-star failed anyway.

On Fri, Oct 28, 2016 at 11:50 AM, Patrik Nordwall  wrote:

> I'm not sure, but I think double-star is only supported at the end of the
> config path
>
> fre 28 okt. 2016 kl. 13:41 skrev Akka Team :
>
>> Hi,
>>
>> I think you need a double-star there (**), since the actor is deeper down
>> in the hierarchy.
>>
>> -Endre
>>
>> On Fri, Oct 21, 2016 at 3:38 PM,  wrote:
>>
>> I would be grateful for some help with this Akka configuration question.
>> This is probably something obvious, but I've been googling and looking at
>> for a day or two and have not yet come up with an answer.
>>
>> Checking the name of the ActorSystem at the top of RCStreamReceiver shows
>> that it is indeed the expected "fubar".
>>
>> My `ActorSystem` is created thus:
>>
>>
>>  val config = ConfigFactory.load("akka.conf")
>>  implicit val system = ActorSystem("fubar", config)
>>
>>
>> The classloader sees my configuration file since changes to logging
>> levels take effect.
>>
>> After creating the `ActorSystem`, my code does the following:
>>
>>
>>val mpr = system.actorOf(Props[ProcessingFlow])
>>
>>
>> In the `ProcessingFlow` the following:
>>
>>val actorSink: Sink[PackedRecord, ActorRef] = Sink.actorSubscriber(
>> Props[RCStreamReceiver])
>>
>>
>> In `RCStreamReceiver` the following:
>>
>>  val logWorkers = context.actorOf(FromConfig.props(Props[LogWorker]),
>> "logWorker")
>>
>>
>> Yet, I get the following:
>>
>>
>>Configuration missing for router [akka://fubar/user/$a/
>> StreamSupervisor-0/flow-3-2-actorSubscriberSink/logWorker] in
>> 'akka.actor.deployment' section.
>>
>>
>>
>> This in spite of my config file looking like this:
>>
>> akka {
>>   loggers = ["akka.event.slf4j.Slf4jLogger"]
>>   loglevel = "WARNING"
>>   logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"
>>   logger-startup-timeout = 15s
>>   actor {
>> provider = "akka.cluster.ClusterActorRefProvider"
>> debug {
>>   log-config-on-start = off
>>   autoreceive = off
>>   lifecycle = off
>>   unhandled = on
>>   event-stream = off
>> }
>> deployment {
>>   default-dispatcher {
>> fork-join-executor {
>>   parallelism-min = 8
>> }
>>   }
>>
>>   /"*"/logWorker = {
>> router = balancing-pool
>> nr-of-instances = 5
>> executor = "thread-pool-executor"
>> thread-pool-executor {
>>   core-pool-size-min = 5
>>   core-pool-size-max = 5
>> }
>>   }
>>
>>
>>   /"*"/editWorker = {
>> router = balancing-pool
>> nr-of-instances = 5
>> routees.paths = ["/foo/editWorker"]
>>   }
>>
>>
>>   /"*"/unknownWorker = {
>> router = balancing-pool
>> nr-of-instances = 5
>> routees.paths = ["/foo/unknownWorker"]
>>   }
>> }
>>   }
>> }
>>
>>
>>
>> --
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: http://doc.akka.io/docs/akka/
>> current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to akka-user+unsubscr...@googlegroups.com.
>> To post to this group, send email to akka-user@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> Akka Team
>> Lightbend  - Reactive apps on the JVM
>> Twitter: @akkateam
>>
>> --
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: http://doc.akka.io/docs/akka/
>> current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to akka-user+unsubscr...@googlegroups.com.
>> To post to this group, send email to akka-user@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 

Re: [akka-user] Re: Trouble understanding Streams doc for Scala: new user question

[Mike Nielsen]

Thanks Tal.

On Thu, Oct 6, 2016 at 2:50 AM, Tal Pressman  wrote:

> Hi,
>
> The type provided to Source.actorRef is the type of the messages emitted
> from the Actor (WorkResult in your case). Success messages can be *sent
> to the actor* in order to cause the stream to complete, but they are
> handled separately and aren't actually emitted to the stream.
>
> As for Map/Collect/Filter/etc., there is actually a stage for it
> (akka.stream.impl.fusing.Map) although I'm not sure they're intended for
> public use (then again, they are public, so...)
>
> Hope this helps,
> Tal
>
>
> On Wednesday, October 5, 2016 at 8:38:26 PM UTC+3, mniel...@gmail.com
> wrote:
>>
>> I'm having a couple of problems understanding the Streams documentation,
>>  in particular, the Overview of built-in stages
>> .
>>
>> My objective is to build, using the GraphDSL, a flow that uses, among
>> others, a Source.actorRef
>>
>>
>> Flow.fromGraph(GraphDSL.create() { implicit b =>
>>
>>   import GraphDSL.Implicits._
>>
>>   val src = b.add(Source.actorRef[Any](bufferSize, OverflowStrategy.
>> fail).mapMaterializedValue(workerSupervisor ! SetWorkRecipient(_)))
>>
>> ...
>>
>> I've used Source.actorRef[Any]because my workerSupervisor (the actor
>> that provides the messages for the source) wants to return a result of type
>> WorkResult
>>
>> However, the documentation says that this stage completes when it
>> receives akka.actor.Status.Success
>>
>> So if I use Source.actorRef[WorkResult] I run into trouble once the work
>> is complete and the  worker wants to signal success, because, of course,
>> the success message is of the wrong type.
>>
>> How can I work around this? I need my stream to emit WorkResult, not Any ;
>> It's not clear from the documentation how to achieve it.
>>
>> Also, the documentation lists the following stages (for example)
>>
>> broadcast, which I add as b.add(Broadcast[T](2)) for example.
>>
>> and
>>
>> map & collect, which can't be added in the same way (i.e. no
>> b.add(Map[T]))
>>
>> yet there is no notation in the documentation that suggests that these
>> stages might be different or used differently.  My thought was to convert
>> the Any  from the Source.actorRef using collect, yet, I'm struggling
>> with doing that.
>>
>> So my 2nd question is, how do I apply map or collect to the output of a
>> Broadcast[T] within the context of a GraphDSL and provide the mapped output
>> as part of the resulting FlowShape?
>>
>> Would you kindly show an example using GraphDSL?
>>
>> Thank you!
>>
>> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: Documentation questions: akka-http

[Mike Nielsen]

Thank you!  I have opened a case with IntelliJ.

On Thu, Sep 15, 2016 at 3:14 PM, Johan Andrén 
wrote:

> Hi,
>
> The format: ON/OFF are directives to our code auto-formatter to not touch
> the code inside of that, for example when we have carefully laid it out to
> be a nice and readable sample.
>
> All the samples are compiled as a part of our ci setup, and again when we
> make a release so if it didn't compile we wouldn't have been able to
> compile it.
> Note that for example the latest IntelliJ seems to have problems resolving
> the implicit conversion needed for it to work, so even though it compiles
> IntelliJ may show a squiggly red line and warning about type mismatch.
>
> --
> Johan
> Akka Team
>
> On Thursday, September 15, 2016 at 8:56:42 PM UTC+2, mniel...@gmail.com
> wrote:
>>
>> In the "spray" documentation (http://doc.akka.io/docs/akka/
>> 2.4/scala/http/common/json-support.html#akka-http-spray-json) a couple
>> of the examples show the following:
>>
>> // format:  OFF
>>
>> followed by
>>
>> //format:  ON
>>
>> What are those comments intended to convey?
>>
>> I keep worrying that I'm missing something significant.
>>
>> Also, on http://doc.akka.io/docs/akka/2.4/scala/http/introduction.html an
>> example shows the following code, which doesn't compile:
>>
>>  case None   => complete(StatusCodes.NotFound)
>>
>> The following change allows it to compile:
>>
>>  case None   => complete((StatusCodes.NotFound,"Too bad"))
>>
>>
>>
>>
>> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.