This is not

Like what you see? Install OctoLinker now!

Skip to content


Here are 3,193 public repositories matching this topic...

slikts commented Sep 12, 2018

Chapter in question:

The suggestion seems to be that the template literals would be all about strings; there's only examples that result in strings, and phrases like "final string value" and "generating the string from the literal" are used in what should be a general context, but the tag function

moon0326 commented Aug 29, 2018

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.

read Chinese and English documentation

  1. What did you expect to see?

I expected to find best practice for production usage

  1. What did you see instead?


  1. What version of Swoole are you using (php --ri swoole)?


pawamoy commented Dec 4, 2019

Is your feature request related to a problem

A docs problem, yes 😛

I want to use HTTPS for my API. The docs suggest to use a Docker Swarm with Traefik and Let's Encrypt. I can't (it's for work). We use a Kubernetes cluster and our own SSL certificates. Then there is a link to the FastAPI project generator, but there are a lot of files in there. I'm not sure to even understand which of

sellmair commented Jan 15, 2020

The awaitClose function currently throws a JobCancellationException if the job was canceled before calling the function.

I would have personally expected that the block passed to awaitClose { } gets executed without throwing this exception.

Sample code:

internal fun SensorManager.consumeValuesAsFlow(
    sensor: Sensor,
    measureInterval: Duration = 20L with TimeUni
saschpe commented Aug 28, 2019


Is your feature request related to a problem? Please describe.
When writing a multiplatform frontend (i.e. Android, iOS) using ktor-client, one has to use strings for get() / update() / delete() calls to a (Ktor-based) backend. This is tedious and error-prone and replicates what had to tbe done for the backend.

Describe the solution you'd like

danieldaeschle commented Jul 15, 2018

We have a nice gitbook site which explains how to use various methods of this library.
What about documentation about the code itself? I dont' always want to read the code.

Isn't it good to write python docstrings and render a sphinx doc site additionally to the "Getting Started Documentation"?

denesb commented Dec 16, 2019

Memory management in a seastar application is a very important topic, as seastar applications are usually long running server applications that want to maximize the usage of memory as well as be resilient to memory fragmentation.
Add a section on this to the docs/ based on the lessons we learned at ScyllaDB. In a nutshell: when large buffers are needed prefer storing data in a chunke

CodiMech25 commented Jul 26, 2018

So, in the last 3-4 hours i was searching for a memory leak in my app. After a complete code-review of my application code i decided to make a new simple app built on Ratchet WS server and see, if the problem persists. And it did!

The problem was, that whenever i created a WS connection, the connection class instances built in the background of the Ratchet were not destroyed! So on every ne

adamchainz commented Dec 20, 2019

The "routing" docs page doesn't mention that Route() is for HTTP only and WebSocketRoute() is required for websocket endpoints. I found WebSocketRoute through examples on other pages but it woudl be good if it was fully described on the "routing" page.

abelsromero commented Nov 30, 2019

I am struggling to test a verticle isolated and all documentation and examples found only show how to test rest endpoints.

Something as simple as this, always fails with timeout

    public RunTestOnContext rule = new RunTestOnContext();

    public Timeout timeout = Timeout.seconds(5L);

    public void should_run_verticle(TestContext context) {
Bilge commented Mar 24, 2018

Trying to learn Amp is difficult for someone new to coroutines and async in the context of PHP. Although I appreciate the work that has been done on the documentation so far, I still find it lacking for giving good background to the topic and its use.

For me, it has been helpful to start thinking about the "async context". It seems to me that in Amp, in order to do anything with async you must

Improve this page

Add a description, image, and links to the async topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the async topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.