Kotlin 1.9.10 官方文档 中文版
resulting in an error. It will eventually be removed from Kotlin. Kotlin/Native Among other improvements, this release brings further advancements to the Kotlin/Native memory manager that should enhance with Java and objects are never initialized in this case. You can also expect some performance improvements in your Kotlin/Native projects thanks to this change. 在 Kotlin/Native 中能够为 iOS 模拟器测试配置独立模 式 along with updates in JavaScript interop. 尺寸相关的优化 Kotlin 1.9.0 introduces significant size improvements for WebAssembly (Wasm) projects. Comparing two "Hello World" projects, the code footprint for0 码力 | 3753 页 | 29.69 MB | 1 年前3
Celery 3.1 DocumentationUsing the Django Database Experimental Status The Django database transport is in need of improvements in many areas and there are several open bugs. Unfortunately we don’t have the resources or funds development docs, go here. Using MongoDB Experimental Status The MongoDB transport is in need of improvements in many areas and there are several open bugs. Unfortunately we don’t have the resources or funds development docs, go here. Using Amazon SQS Experimental Status The SQS transport is in need of improvements in many areas and there are several open bugs. Unfortunately we don’t have the resources or funds0 码力 | 887 页 | 1.22 MB | 1 年前3
Celery v4.1.0 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1057 页 | 1.35 MB | 1 年前3
Celery v4.0.2 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery 4.0 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery v4.0.1 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1040 页 | 1.37 MB | 1 年前3
Celery v4.2.1 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1121 页 | 1.38 MB | 1 年前3
Celery v4.2.2 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1121 页 | 1.38 MB | 1 年前3
Celery v4.2.0 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1110 页 | 1.36 MB | 1 年前3
Celery v4.4.5 Documentationif the worker doesn’t start. In production you’ll want to run the worker in the background as a daemon. To do this you need to use the tools provided by your platform, or something like supervisord [http://supervisord daemonization tool to start the worker in the background. See Daemonization for help starting the worker as a daemon using popular service managers. This document describes the current stable version of Celery (4 kill -HUP $pid Note Restarting by HUP only works if the worker is running in the background as a daemon (it doesn’t have a controlling terminal). HUP is disabled on macOS because of a limitation on that0 码力 | 1215 页 | 1.44 MB | 1 年前3
共 549 条
- 1
- 2
- 3
- 4
- 5
- 6
- 55













