Live CDs/USBs, netbooted PCs and in some cases discardable VMs and containers, usually have a read only base image and an overlayfs/tmpfs/cow filesystem on top of them.

There, we want some services not to run, like package manager upgrades, certain cron-like jobs etc.

It would be awesome if upstream systemd documented what "constitutes a live mode", e.g. the presence of a /run/live directory

There should be a documentation site focused on scenarios similar to this https://gowebexamples.com/.

I'm also thinking about integrating samples from https://github.com/dodyg/practical-aspnetcore.

cc @dodyg

This comes up semi-frequently and I give the same spiel every time but that's rather unscalable.

The spiel is along these lines:

the absolute max is slightly south of 65535 bytes (the maximum size of a UDP datagram)
but this is generally indicative of something going wrong
the batching is done at the level of a server span. if this is in request, that means there's a lot going on in

Current Behavior

README.md doesn't say that a service is removed by default and the --remove flag example doesn't use the flag.

Expected Behavior

The docs should show an example with the non-default behavior, and it should be explained that services are removed by default.

Description:
We have provided JMS proxy level throttling implementation as an update (6378) for EI 6.4.0. We need to update the documentation [1] with the relevant details.
We have already updated the documentation for EI 6.1.0 [2] on the JMS proxy level throttling.

[1] https://docs.wso2.com/display/EI640/Tuning+the+JMS+Transport
[2] https://docs.wso2.com/display/EI610/Tuning+the+JMS+Tr

People suggested to add some inline documentation because they have problems to understand how the library works. This should be fixed.

We should not use the data of a transaction to read the hash of a resource as the behavior might be totally different from transaction that contains multiple messages. It is still manageable if all the messages are the same but if we send different messages that will be a mess.

I suggest reading this information directly from the logs of the result (the events emitted) and not the data and remo

Description:

In connector documentation, we have an overview page [1]. There, we need to point the section Write your own custom connector to document [2]. I think it is originated from [3] and verified with WSO2 MI.

[1]. https://ei.docs.wso2.com/en/latest/micro-integrator/references/connectors/connectors-overview/
[2]. https://ei.docs.wso2.com/en/latest/micro-integrator/develop/cu

Using current Maven 3.6.1 / Openjdk 11.0.3 / Ubuntu 18.04 results in:

>cd devday-service
>mvn javadoc:javadoc
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.1.0:javadoc (default-cli) on project devday-service: An error has occurred in Javadoc report generation: 
[ERROR] Exit code: 1 - error: module not found: de.consol.devday.service

Same when using O