JDK

$ java --version
openjdk 15 2020-09-15
OpenJDK Runtime Environment (build 15+36-1562)
OpenJDK 64-Bit Server VM (build 15+36-1562, mixed mode, sharing)

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

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 该如何变化
     

I thought I open an issue for that as I believe it can save the team a lot of work.

https://github.com/actions/labeler

If this is interesting I would contribute with the workflow file.

Just let me know what you think.

I'd like to use react-solid-state in a React/Typescript project, but the typing are missing. Or do I have to import the types from solid?

Since 3.4.0, most retry and retryWhen operator variants have been removed in favor of retry(Retry) and the RetrySpec/RetryBackoffSpec builders.

However, the reference documentation still mentions these methods in the faq.adoc.

It also references deprecated Retry builder/function from reactor-extra in apdx-reactorExtra.adoc.

The FAQ should be updated to use the new API in

Lagom 1.6.4

The akka-persistence-testkit library contains very useful testkit classes, like EventSourcedBehaviorTestKit. Unfortunately the dependency is not listed in the lagom-maven-dependencies BOM. Thus project has to manage this dependency additionally to the lagom one. Including this dependency into the lagom-maven-dependencies will make its usage more comfortable and will prevent a po

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

Last I checked, Pluto does not pass tests on Julia 1.6 because something changed internally in the method table ordering. Run the tests to see what's up.

If you are comfortable with building Julia from source, and if you have some experience with manipulating method tables in Julia, then this would be a good issue to help out Pluto, without working on javascript!