Are you looking for help?

No.

Play Version

2.6 to 2.8

API

Java / Scala

Expected Behavior

The instructions at https://www.playframework.com/documentation/2.8.x/Deploying-CloudFoundry work.

As it stands (see https://stackoverflow.com/a/62506207/4432837 and cloudfoundry/java-test-applications#20) those instructions are no longer applic

Quite a few operator factory methods use d: java.time.Duration in the stream Java APIs for some reason. Given that the parameter names are not important for bin/source compatibility in Java perhaps we could change those to a clear name without problems?

This is to fix: Nozbe/WatermelonDB#186

Right now, deleting records is not very efficient in WatermelonDB.

Say you have models like this: Blog has_many Post has_many Comment. If you want to delete a blog post, you also have to delete all its posts, and all their comments. This happens one-by-one currently. What we need is the ability to efficiently (and atomically if

看了fish-redux的todoList demo，发现里面连接全局状态的方法是使用visitor

visitor: (String path, Page<Object, dynamic> page) {
      /// 只有特定的范围的 Page 才需要建立和 AppStore 的连接关系
      /// 满足 Page<T> ，T 是 GlobalBaseState 的子类
      if (page.isTypeof<GlobalBaseState>()) {
        /// 建立 AppStore 驱动 PageStore 的单向数据连接
        /// 1. 参数1 AppStore
        /// 2. 参数2 当 AppStore.state 变化时, PageStore.state 该如何变化
     

Copied from: nrwl/nx#1545

Please make sure you have read the submission guidelines before posting an issue

Expected Behavior

Please describe the behavior you are expecting

When running the below command without a --project flag, I expect the error message to reflect the missing fl

I really would appreciate feedback here. It is so hard for me to see it since I've been so close to this for so long and I've developed apps in this manner for 10 years. I'm going to be the worst person to write the documentation since it is all so second nature for me. Yet, I am most likely going to be the person writing the documentation since I understand how everything works so well.

So can

The window operators should indicate if the returned Flux for each window is safe to subscribe to multiple times.

Documentation Issue

I had a data processing pipeline that I introduced batching to, using the window operator. In this pipeline, it will retry a batch if it faces a transient error. When batching was added, and it retried, I saw a failure of `IllegalStateException: UnicastP

Basically, we don't need to have kafka-console-consumer, we have mill instead: https://github.com/ThreeDotsLabs/watermill/tree/master/tools/mill

It would be nice to replace it in all examples.

Chrome:

Firefox:

The idea is to be able to write the following to override the log configuration in dev-mode.

lagomDevSettings ++= Seq(
  "logger.resource" -> "logback-dev.xml"
)