reactive

The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:

1. Update the docs to reflect the latest Storybo

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.

We use sbt-dynver to set the version for the Play project based on git tags.
E.g. when you run sbt in the Play project folder you will see:

// If you haven't you need to get the Play framework source code
git clone git@github.com:playframework/playframework.git
cd ./playframework

// You are in the master branch now, from which we want to rele

Describe the bug

The documentation https://github.com/quarkusio/quarkus/blob/main/extensions/quartz/runtime/src/main/java/io/quarkus/quartz/runtime/QuartzBuildTimeConfig.java#L46 is referring to db store which has long been deprecated and removed.
We should update the javadoc to refer to jdbc-tx or jdbc-cmt job stores instead.

Expected behavior

There is no mention of db store

Is there a way to export / import(restore) database.

看了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

Documentation Issue

I think the documentation of Schedulers#boundedElastic is confusing regarding the @return statement. It states

 * @return a new {@link Scheduler} that dynamically create workers with an upper bound to
 * the number of backing threads and after that on the number of enqueued tasks,
 * that reuses threads and evict idle ones

It lead me to think that the retur

This comment says that the message ID is optional,
but for SQL transport it is a mandatory attribute,
in turn it causes misunderstanding?

Is it possible to fix it or did I get something wrong?

https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f67388/message/message.go#L20
https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f6

We have a couple of combinations of let and global that are not analyzed correctly, like:

let
	a = 1
	global a = 2
end

defines a global a, but Pluto prioritizes the let block.

@test_broken means that we still need to fix it:

https://github.com/fonsp/Pluto.jl/blob/c1d23122845e7864ef3dfe15a8428366c98f95eb/test/ExpressionExplorer.jl#L368-L379

This is a good firs

In documentation about guard there is no info that if we do not pass 'source' then guard gets data from clock.

Moreover, we can add to Docs more cases like that
https://share.effector.dev/deTs17ML

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"
)